You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Simone Tripodi (JIRA)" <ji...@apache.org> on 2011/07/06 13:55:16 UTC
[jira] [Closed] (DIGESTER-72) [digester] Allow SetNextRule to fire
on begin
[ https://issues.apache.org/jira/browse/DIGESTER-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simone Tripodi closed DIGESTER-72.
----------------------------------
included in Apache Commons Digester 3.0 release
> [digester] Allow SetNextRule to fire on begin
> ---------------------------------------------
>
> Key: DIGESTER-72
> URL: https://issues.apache.org/jira/browse/DIGESTER-72
> Project: Commons Digester
> Issue Type: Improvement
> Affects Versions: 1.6
> Environment: Operating System: other
> Platform: All
> Reporter: Simon Kitching
> Assignee: Simone Tripodi
> Priority: Minor
> Fix For: 3.0
>
>
> Currently, SetNextRule always invokes the target method from its end method.
> But there is no reason why it can't invoke the target from begin. This would be
> useful in cases where it is desirable to build the parent/child relationship
> before processing nested xml. In particular, using BeanPropertySetterRule
> against nested xml elements can cause the setter methods to be called on a bean
> before its parent/child relationship is set up and sometimes this is bad.
> It should be possible to add options to the constructor of SetNextRule to
> indicate if fire-at-end (existing) or fire-at-begin (new) behaviour is desired.
> Of course the xmlrules module would need to be updated too.
> And this feature probably could be applied to a few other rules.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira