FWIW I worked around this by defining and returning my own "holder" class - it looks just like the ArrayOfWhatever class that JAXB would have generated. Of course, it meant that the signature of my service method had to change.
In other words, I no longer rely on the automatic handling of arrays. Interestingly, my holder class now contains the List<Whatever> and there are no problems writing the XML at all. Tim Tim Morrow 2 wrote: > > I'm using XFire 1.2.5 with JAXB2 and JSR181 annotations, specifying the > org.codehaus.xfire.jaxb2.JaxbServiceFactory in my services.xml. > > When I try to invoke a web service using the dynamic client where the web > service method returns an Array (or List) of a JAXB-annotated object I get > an XStreamException: > > ...snip... > > The problem doesn't occur when the array or list is empty. The WSDL looks > fine too. > > Has anyone encountered such an issue? > > Thanks, > > Tim > > -- View this message in context: http://www.nabble.com/XMLStreamException%3A-No-open-start-element%2C-when-trying-to-write-end-element-with-JAXB2-JSR181-generation-tf3481745.html#a9754261 Sent from the XFire - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
