Spot on. Thank you. I had a rogue reference to jaxb-api 2.0 being used, amongst the rest of the 2.1 usage. I wish I had thought to belly up and admit I was stumped a long time ago.
dkulp wrote: > > On Thu February 19 2009 11:54:11 pm baartz wrote: >> After a fair amount of trial and error, I have some measure of confidence >> that this is a classpath issue, but no idea how. My dependent dlls are >> located in WEB-INF/lib. If I revert all of the elements that should be >> marshalled to public members, then I get the behavior I was anticipating. >> However, when left private with getters, I am unable to get the dependent >> objects to be marshalled. If I bring the class I'm trying to marshal >> into >> the war, then all acts as expected. >> >> baartz wrote: >> > I'm having some difficulty figuring out how to configure my service to >> > yield a wsdl that recognizes the jaxb annotations on my transfer >> objects >> > unless their classes are included in the war. >> > >> > Any ideas? > > Any chance you can create a small example and post to a JIRA. > > I have no idea what would cause that either. :-( Is the jaxb-api jar > in > the same place as the objects? (and only in that location) I suppose if > the > jaxb-api jar is in the war, the cxf runtime looks for annotations of that > class, but if the objects are outside (and a version of jaxb also > outside), > the annotations on those objects are of the "different" class (same > classname, > but different classloader, thus different). > > -- > Daniel Kulp > [email protected] > http://www.dankulp.com/blog > > -- View this message in context: http://www.nabble.com/Jaxb-annotations-outside-of-war-tp22105605p22129105.html Sent from the cxf-user mailing list archive at Nabble.com.
