DO NOT REPLY [Bug 35095] New: - Allow SetNextRule to fire on begin

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35095>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35095

           Summary: Allow SetNextRule to fire on begin
           Product: Commons
           Version: 1.6 Final
          Platform: All
        OS/Version: other
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Digester
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: skitching@apache.org


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.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org