<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - To Annotate or Not?</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Fri, 24 May 2013 20:24:11 -0400</pubDate>


    <item>

        <title>EJB3 XML configuration format</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29754</link>

        

        
            <description><![CDATA[Yes, some folks are looking into how this would work at the J2EE level (the scope at which resources are used) and in fact a proposal is being circulated right now within the J2EE, EJB and other expert groups as well. I believe that it will work just as...]]></description>
        

        <pubDate>Wed, 03 Nov 2004 09:27:59 -0500</pubDate>

        

        <jf:creationDate>Wed, 03 Nov 2004 09:27:59 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 03 Nov 2004 09:27:59 -0500</jf:modificationDate>
        <jf:date>Nov 3, 2004</jf:date>
        <jf:author>Mike Keith</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>EJB3 XML configuration format</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29754</link>

        

        
            <description><![CDATA[Will to-be EJB3 also standardize a xml-based configuration format (for dependency injection / properties) to compliment annotations for the usage scenarios Drew described?  Or will it be up to each vendor to do their own thing?  I missed that.<br><br>If...]]></description>
        

        <pubDate>Wed, 03 Nov 2004 08:36:39 -0500</pubDate>

        

        <jf:creationDate>Wed, 03 Nov 2004 08:36:39 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 03 Nov 2004 08:36:39 -0500</jf:modificationDate>
        <jf:date>Nov 3, 2004</jf:date>
        <jf:author>Keith Donald</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>POJMM</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29754</link>

        

        
            <description><![CDATA[<blockquote>I still think that it is better to keep certain details out of code so that they can be modified as necessary. IMHO this approach leads to much looser coupling, and thus greater code flexibility. You do have to watch, however, that your...]]></description>
        

        <pubDate>Tue, 02 Nov 2004 15:42:36 -0500</pubDate>

        

        <jf:creationDate>Tue, 02 Nov 2004 15:42:36 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 02 Nov 2004 15:42:36 -0500</jf:modificationDate>
        <jf:date>Nov 2, 2004</jf:date>
        <jf:author>Deivson Rayner Teixeira da Costa</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>RE: To Annotate or Not?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29754</link>

        

        
            <description><![CDATA[I see the value of both the developer simplicity of annotations (provided they are minimal with good defaults) and also the need for the ability to use concise XML meta-data. Ideally I would like to see JSRs looking at using annotations follow a common...]]></description>
        

        <pubDate>Tue, 02 Nov 2004 14:14:45 -0500</pubDate>

        

        <jf:creationDate>Tue, 02 Nov 2004 14:14:45 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 02 Nov 2004 14:14:45 -0500</jf:modificationDate>
        <jf:date>Nov 2, 2004</jf:date>
        <jf:author>Doug Clarke</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Based on my Xdoclet experience</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29754</link>

        

        
            <description><![CDATA[Perhaps the experience of using Xdoclet annotations in the code to generate metadata is relevant here.<br><br>It was really convenient in the short term.  There was an immediate boost in developer producticvity.<br><br>However, I dread the posibility of...]]></description>
        

        <pubDate>Tue, 02 Nov 2004 14:02:24 -0500</pubDate>

        

        <jf:creationDate>Tue, 02 Nov 2004 14:02:24 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 02 Nov 2004 14:02:24 -0500</jf:modificationDate>
        <jf:date>Nov 2, 2004</jf:date>
        <jf:author>bad mASH</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>To Annotate or Not?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29754</link>

        

        
            <description><![CDATA[Yup. Sun make it real pain to do the deployment XML so that they can introduce annotation to fix it. The annotation can make code/deployment coupling so strong that Sun can come out with a new way (annotation interceptor in jdk 1.6? :)) for fixing it....]]></description>
        

        <pubDate>Tue, 02 Nov 2004 10:28:28 -0500</pubDate>

        

        <jf:creationDate>Tue, 02 Nov 2004 10:28:28 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 02 Nov 2004 10:28:28 -0500</jf:modificationDate>
        <jf:date>Nov 2, 2004</jf:date>
        <jf:author>Tiong Lee</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Thanks, han theman!!</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29754</link>

        

        
            <description><![CDATA[You are so kind! :)]]></description>
        

        <pubDate>Tue, 02 Nov 2004 08:05:50 -0500</pubDate>

        

        <jf:creationDate>Tue, 02 Nov 2004 08:05:50 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 02 Nov 2004 08:05:50 -0500</jf:modificationDate>
        <jf:date>Nov 2, 2004</jf:date>
        <jf:author>Younghoe Ahn</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>A stupid question</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29754</link>

        

        
            <description><![CDATA[IMHO = In My Humble Opinion<br>IMNSHO = In My Not So Humble Opinion]]></description>
        

        <pubDate>Tue, 02 Nov 2004 06:26:35 -0500</pubDate>

        

        <jf:creationDate>Tue, 02 Nov 2004 06:26:35 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 02 Nov 2004 06:26:35 -0500</jf:modificationDate>
        <jf:date>Nov 2, 2004</jf:date>
        <jf:author>han theman</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>A stupid question</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29754</link>

        

        
            <description><![CDATA[<blockquote>this approach leads to much looser coupling, and thus greater code flexibility. You do have to watch, however, that your config formats are easy to deal with.</blockquote><br>Dear, Drew McAuliffe.<br>I read and understood your good...]]></description>
        

        <pubDate>Tue, 02 Nov 2004 05:34:26 -0500</pubDate>

        

        <jf:creationDate>Tue, 02 Nov 2004 05:34:26 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 02 Nov 2004 05:34:26 -0500</jf:modificationDate>
        <jf:date>Nov 2, 2004</jf:date>
        <jf:author>Younghoe Ahn</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>To Annotate or Not?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29754</link>

        

        
            <description><![CDATA[I understand your point, but unfortunately there are far too many cases where even what you described is too tightly coupled. In some enterprise environments, developers don't have control over things like datasource names (because they're considered...]]></description>
        

        <pubDate>Tue, 02 Nov 2004 01:28:50 -0500</pubDate>

        

        <jf:creationDate>Tue, 02 Nov 2004 01:28:50 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 02 Nov 2004 01:28:50 -0500</jf:modificationDate>
        <jf:date>Nov 2, 2004</jf:date>
        <jf:author>Drew McAuliffe</jf:author>
        <jf:replyCount>8</jf:replyCount>
    </item>


    <item>

        <title>To Annotate or Not?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29754</link>

        

        
            <description><![CDATA[<blockquote>So what is the cost of brevity? Specifying the metadata beside the source instead of in a decoupled XML file has certain repercussions.</blockquote><br>I don't think this is a real issue.  The annotations can act as &quot;keys&quot; within a...]]></description>
        

        <pubDate>Mon, 01 Nov 2004 17:10:53 -0500</pubDate>

        

        <jf:creationDate>Mon, 01 Nov 2004 17:10:53 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 01 Nov 2004 17:10:53 -0500</jf:modificationDate>
        <jf:date>Nov 1, 2004</jf:date>
        <jf:author>hookomjj</jf:author>
        <jf:replyCount>10</jf:replyCount>
    </item>


    <item>

        <title>To Annotate or Not?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=29754</link>

        

        
            <description><![CDATA[Java 2 Standard Edition (J2SE) 5.0 is now a reality, annotations have become popular, and the Java metadata feature it introduced is being touted with much fanfare as being somewhere between a new and better way to develop applications and a full-scale...]]></description>
        

        <pubDate>Mon, 01 Nov 2004 14:49:12 -0500</pubDate>

        

        <jf:creationDate>Mon, 01 Nov 2004 14:49:12 -0500</jf:creationDate>
        <jf:modificationDate>Mon, 01 Nov 2004 14:49:12 -0500</jf:modificationDate>
        <jf:date>Nov 1, 2004</jf:date>
        <jf:author>Doug Clarke</jf:author>
        <jf:replyCount>11</jf:replyCount>
    </item>



</channel>
</rss>

