We are migrating to JBoss an existent web services module, originally developed to Weblogic. We have the beans that implement the business logic and the wsdl file that was generated for Weblogic using a Servicegen task. The existent beans have been adapted to an EJB-based JBoss web service, that is, with an endpoint class and generating the wsdl and xml files with wstools within an Ant task. The wsdl generated by the JBoss tools is quite different to the one that was generated by the Weblogic Servicegen tool.
On the other hand, there is a previosuly developed client that worked fine with the webservices in Weblogic, but doesn't work now with the new web services in Jboss. We have developed a new client using wsdl2java included in the Eclipse Webtools plugin based on Axis runtime and it communicates with the server, although there are problems regarding null values (Axis SOAP requests are not comlpetely understood by the server regarding these values).
Our biggest problem is that the existent client should not be changed, and we are not able to get it working with the new web services in JBoss (probably because the wsdls are quite different)
Is there anyway to migrate the web services to JBoss without changing the current wsdl?
Any ideas to solve this issue?
Thanks in advance.
I would follow a top-down development strategy using wsconsume (see the jaxws guide at http://labs.jboss.com/jbossws/docs/jaxws_userguide-2.0/index.html#d0e741)
This should allow you to keep your previous wsdl contract, at least if it's compliant with standards.