[ http://jira.jboss.com/jira/browse/JBXB-2?page=history ]
Alex Loubyansky resolved JBXB-2:
--------------------------------
Resolution: Done
This should be fixed now. XNI includes also emptyElement callback (which was
misused) in addition to start/endElement.
SAX-based parser should be avoided as it does not provide contextual
information about the element being parsed other than uri, local name, qname.
Which was the reason to implement parser based on XNI.
Please, check that your code runs w/o issues now. Are there tests I could run
to make sure I don't break anything next time?
> Xni parser has problems with short form tags
> --------------------------------------------
>
> Key: JBXB-2
> URL: http://jira.jboss.com/jira/browse/JBXB-2
> Project: JBoss XML Binding (JBossXB)
> Type: Bug
> Environment: jboss-head
> Reporter: Adrian Brock
> Assignee: Alex Loubyansky
>
>
> The new Xni parser does not emit endElement() notifications for tags of the
> form <mytag/> rather than <mytag></mytag> where it does.
> This means the stack of accepted elements gets out of step with the end
> element notifications.
> I've switched back to the Sax parser in the Unmarshaller as the default in
> jboss-head
> to avoid this problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
