Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <538229113.1256132999357.JavaMail.jira@brutus>
Date: Wed, 21 Oct 2009 13:49:59 +0000 (UTC)
From: "James Carman (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (DIGESTER-135) Digester rules defined through
 Java5 Annotatations
In-Reply-To: <87202288.1254984811286.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DIGESTER-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768240#action_12768240 ] 

James Carman commented on DIGESTER-135:
---------------------------------------

I'm not so sure about this approach.  One thing that jumped out at me was the @SetNext annotation.  When you're building up your digester by hand, you have some context of where you are when you set up your rules.  With that @SetNext, how do you know where you are?   How do you know your context?  It would be easy for the classes to get out of synch.  I think we'd be better off creating a rules builder API that reads more like English.

> Digester rules defined through Java5 Annotatations
> --------------------------------------------------
>
>                 Key: DIGESTER-135
>                 URL: https://issues.apache.org/jira/browse/DIGESTER-135
>             Project: Commons Digester
>          Issue Type: Improvement
>    Affects Versions: 2.1
>            Reporter: Simone Tripodi
>            Priority: Minor
>             Fix For: 2.1
>
>         Attachments: DigesterAnnotations.patch
>
>
> Taking inspiration by Google-Guice, JAXB and JPA's annotations, the existing package can be extended adding some facilities to configure the commons-digester using the Java language metadata annotations.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.