I don't understand your problem. I would guess your service implementation bean gets a "IndEmployeeRosterType data" object for the upload operation, from which you can call data.getThis() and data.getThat() to get each of the underlying objects in that complex type. AFAICT no manual unmarshalling needed.
Glen huntc wrote: > > Hi there, > > <p>I have a doc/lit/bare service defined and my service is invoked with > the bare payload - the payload appears to be a W3C Element class (actually > a Xerces ElementNSImpl). This is reasonable I suppose; after all I did > declare the parameter to be bare so I guess CXF leaves it to me to > unmarshall it. > > <p>My first question is then - should CXF leave it to me to unmarshall the > parameter? > > <p>If the answer to the above is "yes" then can someone please provide me > with a pointer as to how to go about that (I'm wondering here if I can use > the same jaxb context as CXF is using - the context should know how to > unmarshall the data as my WSDL provides a complete definition). > > <p>Here's my interface: > > <pre> > @WebService(targetNamespace = > "http://schemas.blueglue.com.au/hrwebservices";) > @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE) > public interface IndicativeDataService { > void upload( > @WebParam(name = "IndicativeData", targetNamespace = > "http://ns.hr-xml.org/2007-04-15";) IndEmployeeRosterType data); > } > </pre> > -- View this message in context: http://www.nabble.com/doc-lit-bare-service---how-to-unmarshall-the-elementnsimpl-tp19798742p19830221.html Sent from the cxf-user mailing list archive at Nabble.com.
