[ http://jira.codehaus.org/browse/XFIRE-301?page=all ]
Dan Diephouse closed XFIRE-301:
-------------------------------
Resolution: Fixed
This is fixed now in SVN. Thanks! Note: you will have to enable the xmlbeans
namespace hack for rpc/lit to work:
http://xfire.codehaus.org/XMLBeans+Integration?nocache
> RPC/literal messages containing XMLBeans complex types parsed incorrectly
> -------------------------------------------------------------------------
>
> Key: XFIRE-301
> URL: http://jira.codehaus.org/browse/XFIRE-301
> Project: XFire
> Type: Bug
> Components: XMLBeans, Core
> Versions: 1.1, 1.0
> Environment: XFire 1.0 + dependent JARs from xfire-distribution; JDK
> 1.5.0_06; Sun Application Server PE 8.1; Windows XP Pro SP2 IA-32
> Reporter: Tim Robbins
> Assignee: Dan Diephouse
> Fix For: 1.1
>
>
> RPC/literal messages containing XMLBeans complex types are not parsed
> correctly. when the XMLBeans type is anything other than the last parameter.
> I've tracked this down to the main loop in
> org.codehaus.xfire.service.binding.RPCBinding.readMessage returning
> prematurely because the XMLBeans parser has left the DepthXMLStreamReader in
> the "END_ELEMENT" state, which causes STAXUtils.toNextElement to return
> false, terminating the loop.
> It's unclear whether the XMLBeans parser or RPCBinding.readMessage should be
> skipping over this END_ELEMENT event. Modifying RPCBinding.readMessage to
> skip over the END_ELEMENT event (and kludging around XFIRE-299) fixes the
> problem for me and allows me to successfully use XMLBeans with RPC-style
> services.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
