cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Resolved: (CXF-908) "XMLStreamException: No open start element..." using JaxB
Date Tue, 19 Feb 2008 21:38:46 GMT


Daniel Kulp resolved CXF-908.

       Resolution: Invalid
    Fix Version/s: Invalid

Marking invalid as this is an XFire issue, not CXF.

> "XMLStreamException: No open start element..." using JaxB
> ---------------------------------------------------------
>                 Key: CXF-908
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>         Environment: Application on Jboss-4.2.1.GA, JRockit R27.2.0 jre 1.5.0_10. 
>            Reporter: Grzegorz Oledzki
>             Fix For: Invalid
> When writing a service which implements only one method: 
> public Set<Address> getAddresses(String par);
> we get on the server-side an 
> org.codehaus.xfire.fault.XFireFault: Couldn't write message.
> caused by:
> No open start element, when trying to write end
> Client failes with the message:
> org.codehaus.xfire.fault.XFireFault: Could not unmarshall type : unexpected element (uri:"",
local:"Envelope"). Expected elements are [ comes the list of expected elements]
> at org.codehaus.xfire.jaxb2.JaxbType.readObject( 
> [...]
> After debugging the XFire under Eclipse I discovered that:
> the problem is caused by too many writeEndElement() compared to writeStartElement(),

> the error has to been somewhere in the area constrained by these calls:
> AegisBindingProvider:220 # writeParameter() creates an ElementWriter with constructor
NOT writing the start element,
> CollectionType # writeObject() is called
> ArrayType:279 # writeValue() is called
> Since type is JaxbType this line is called: 
> cwriter = writer;
> Then after writing the object the writer is closed by:
> cwriter.close();
> which refers to:
> ElementWriter:176 # close()
> which writes the end-element (but there has been no start element written before, so
it closes its parent)
> My guess is that the ElementWriter#close() implementation should be changed. So that
the end element is written only if the start element was written before.
> Or... If not there, then maybe the ArrayType#writeValue()?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message