The w3c Element is what JAXB unmarshals to if there isn't a real java class that it knows about that is bound to the element name. This USUALLY occurs if the parameter is an interface or some other class that JAXB cannot handle. The other time is if you have a subclass, but the interface uses the superclass.
As you found, the XmlSeeAlso annotation allows adding extra classes to the JAXB context to make sure it knows everything that is needed. Dan On Sunday 05 October 2008, huntc wrote: > Hi Glen, > > Thank you for your message. > > The problem was that, before specifying the see-also annotation, the > data passed to my service came through as a null object. > > On closer inspection within the debugger the object being passed to me > was actually an ElementNSImpl type i.e. something that had not been > unmarshalled. > > Kind regards, > Christopher -- J. Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog
