Title pretty much explains the question, but for background, we are attempting to integrate with a poorly-designed SOAP-based web service which does not fully specify the XSD of the object model. So during the wsimport, we use the "-b" option to provide our own XSD to generate the additional portion of the object model that we want to use. However, we don't need to access ALL of the attributes of that additional object model, so our additional XSD only specifies the subset of attributes that we want to access. Attempting to provide and maintain a full XSD for a web service that we don't own is too exhaustive a solution in this case, so that leads to the following problem after deployment to TomEE.
javax.xml.bind.UnmarshalException: unexpected element (uri:"", local:"ism_i_ID"). Expected elements are... So what's the best mechanism to go about configuring the JAXB context for the @WebServiceRef injection to ignore the unexpected elements in the XML body of the SOAP response? Keep in mind that I'm pretty new to TomEE as we are only just beginning to explore the option of moving a pretty big enterprise project over to it from WebLogic, and I'm pretty much the pioneer on this frontier for our team, so please ELI5 it for me. -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/How-to-Configure-SAX-Parser-for-WebServiceRef-Injection-to-Ignore-Unexpected-Elements-tp4679008.html Sent from the TomEE Users mailing list archive at Nabble.com.
