Hi Daniel, Yes my WSDL/schema defines the B type as an extension of A. I think the problem is due to the JAXBContext instance at invoking the "op" operation. It should contain just A class and not the B class. That justifies why my message is unmarshalled as an A instance. Therefore, my global jaxb context does not work as it should be. It seems that in cxf 2.7.10 version, a JAXBElement instance is computed by default on classes without JAXB annotations. Because, when I remove the globalContext spring configuration in my cxf-beans.xml file at the server side, I get exactly the same results. Maybe there is another way to force JAXB to use a global context which defines all the classes in my package? Which must do the same as adding @XmlSeeAlso annotation
Kind regards, Diana -- View this message in context: http://cxf.547215.n5.nabble.com/How-to-configure-CXF-for-a-single-JAXBContext-and-for-an-automatic-JAXBElement-conversion-tp5740782p5740813.html Sent from the cxf-user mailing list archive at Nabble.com.
