Correct. My objective is to manually handle the XML processing of the web service. I would like to use the WSDL to generate the Java source.
Using wscompile to generate artifacts with the nodatabinding feature, I receive the above exception upon a client attempting to consume the web service. I also tried implementation via wstools. I suspect wstools does not support generation of artifacts from WSDL -> Java for message style endpoints. I do not see an element or attribute in the wstools ant task to support mesage style endpoints; nor is there an element or attribute for the wsdl-java element in the wstools configuration file to flag processing for message style endpoints. When I generate using WSDL-> Java, wstools creates POJO representations of the schema, as well as the generated service didn't deal with SOAPElement arguments or method returns. Any advice? For wscompile, I suspect I am missing something in the jaxrpc mapping file, and / or missing something in the ws4ee-deployment.xml, and that is what is causing the stack trace from the JBossWS (org.jboss.ws.soap.SOAPContentElement) source code. I am unsure what I am neglecting for the wstools utility. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3950864#3950864 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3950864 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
