DO NOT REPLY [Bug 34819] - [digester] NodeCreateRule Failing

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

DO NOT REPLY [Bug 34819] - [digester] NodeCreateRule Failing

Bugzilla from bugzilla@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=34819>.
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=34819





------- Additional Comments From [hidden email]  2005-05-10 01:00 -------
Hi Jack.

Interesting. My initial thought is that NodeCreateRule is doing something that
Xerces is happy with but that Aelfred doesn't want to allow.

My guess is that
  getDigester().getXMLReader().setContentHandler(...)
is the issue, ie that Aelfred doesn't like people to modify the content handler
after parsing has started. I've checked the Aelfred javadoc online, but it
doesn't say anything relevant.

Firstly, could you please run your test again with logging enabled?
See the section titled "How do I enable debugging output" in the FAQ:
  http://wiki.apache.org/jakarta-commons/Digester/FAQ

And secondly, could you please write a simple SAX app which attempts to set the
content handler after parsing has started and see what happens?

Have you run the complete digester test suite using kaffe? I should do that
sometime to see what happens..

--
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: [hidden email]
For additional commands, e-mail: [hidden email]