"thomas.diesler(a)jboss.com" wrote : | | import org.jboss.ws.core.jaxws.JAXBContextCache; | | | | This already is the problem. You cannot rely on proprietary API . | +1 and that's why I'm here looking for the correct solution :-) What I've outlined is what I had to do to get the "native" JBossWS stack (which uses JAXB, right?) to work with a set of Java bindings that are not JAXB annotated. Kohsuke Kawaguchi has confirmed that this is the correct solution from a JAXB perspective, so I guess what we need to do here is figure out how this all fits into your view of the world ala the JBossWS SPI etc "thomas.diesler(a)jboss.com" wrote : However I need to understand your use case better in order to give you a qualified answer. OK. It's basically as I outlined in the JAXB forum post... anonymous wrote : "... we need to be able to bind an XML message (using this JAXB based code) into an existing Java interface (not annotated for JAXB). We don't own the interface, so changing it is not an option." So JAXB requires the java bindings it's trying to unmarshal the SOAP message into to have JAXB annotations. In the JBossESB usecase, this is very often going to be impossible because the interface is probably owned by something outside the ESB (i.e. we can't modify them to add the annotations). An ESB example of this that we continually use is where the ESB is being used to expose a Webservice interface for a legacy EJB based Service. The EJB remote interface is already defined and is what we want to base our ESB "hosted" (interpret loosely) JSR181 endpoint - the EJB wrapper Webservice. Our current solution to all this from a JBossESB + JBossWS 2.0.x perspective is as outlined in that JAXB forum post. "thomas.diesler(a)jboss.com" wrote : Not every supported stack is necessarily using JAXB. So setting JAXB properties might not be the right solution anyway. How the SPI exposes this is up to you for sure. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057738#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...