|
From: Bill B. <bb...@re...> - 2008-09-25 17:53:14
|
Hmmm... You'll have to create a testcase that I can use to recreate the problem. I had to make the changes specified so that @XmlSeeAlso would work (i.e. for unmarshalling class hierarchies). Todd Yocum wrote: > When updating from beta-6 to beta-8, my jaxb unmarshalling no longer works where it once did. > > I now get the following unmarshal exception > > javax.xml.bind.UnmarshalException: unexpected element (uri:"http://www.example.org/DataCollectionPackage", local:"DataCollectionPackage"). Expected elements are (none) > > Looking at the Subversion changes for AbstractJAXBProvider.java, I see the following comment > > rev 343: fix JAXB baseclase bugs and eating of errors > > And the code changed from > > JAXBElement<T> e = unmarshaller.unmarshal(new StreamSource(entityStream), type); > return e.getValue(); > > to > > return (T) unmarshaller.unmarshal(new StreamSource(entityStream)); > > So was there a problem with my JAXB class and it just wasn't being handled in beta-6, or did something else change in > beta-8 that I should be aware of, perhaps? I noticed the supporting libs were all the same, except that the size changed > for jaxb-api-2.1.jar from beta-6 to beta-8 > > Any insights greatly appreciated. > > Thanks > > Todd > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Resteasy-developers mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-developers -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com |