0 Replies Latest reply on Oct 22, 2009 2:13 PM by Michael McKibben

    Custom JAXBContext search path for JAXWS EJB endpoint

    Michael McKibben Newbie

      Hi All,

      I have a JAXWS EJB endpoint implementation using JBossWS 3.2 Native, and I need to customize the JAXBContext package search path used to unmarshall the SOAP payload.

      My wsdl is using document literal to send the payload, and one of the message elements has a child element that is of type "xs:any". I have the JAXB generated Java classes for the actual element being added as a child in the xml, but the object is still being unmarshalled as a DOM Element instead of my JAXB class.

      It seems like this should be possible, but I can't find any way to do this looking through the user docs. I thought by adding an @XmlSeeAlso annotation to my JAXWS EJB SEI implementation should've added that JAXB class to the JAXBContext used for unmarshalling, but that didn't work.

      Anybody have a solution? Or is this a JBoss bug? The JAXWS 2.1 spec (see section 2.2) seems to imply the @XmlSeeAlso should work, but their examples show the annotation on the SEI and not on the SEI implementation.