Jim Ma [http://community.jboss.org/people/jim.ma] created the discussion
"Re: Handling message parts defined in SOAP header with CXF" To view the discussion, visit: http://community.jboss.org/message/601567#601567 -------------------------------------------------------------- Sorry for the late response. I created implementation class and dispatch this soap request message in CXF: @WebService(targetNamespace = "http://www.jboss.org/bpel/examples/wsdl";, name = "HelloGoodbyePortType") @XmlSeeAlso({org.jboss.bpel.examples.xsd.ObjectFactory.class}) @SOAPBinding(style = SOAPBinding.Style.RPC) public class HelloGoodbyePortTypeImpl implements HelloGoodbyePortType{ @Override public void hello(Holder<Integer> id, Holder<String> message) { System.out.println("id" + id.value); System.out.println("message" + message.value); } @Override public void goodbye(Holder<Integer> id, Holder<String> message) { System.out.println("id" + id.value); System.out.println("message" + message.value); } } This soap message can talk with this implementation. I also looked at the WebServiceProviderGenerator.java and BaseWebServiceEndpoint.java, but I did not figure out what's the generated provider class looks like, and how can I create an provider class to reproduce this issue in CXF ? JBossWS native uses own saaj implementaion. It might does some extra things and behaviors differently from Sun's saaj implementation which CXF used before execture Provider.invoke(). Do you have the server log for this error ? Let see if that helps us find somthing. Thanks Jim -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/601567#601567] Start a new discussion in JBoss Web Services at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2044]
_______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
