In Axis1 1.4 the command to use is: %>java org.apache.axis.wsdl.WSDl2Java --server-side --skeletonDeploy true <web_service_name>.wsdl This command will generate two sets of Java classes that are mingled together (pity that), the stub, locator and interface classes needed by clients, and the skeleton, impl and interface classes needed by the web service. Their location is determined by the reverse of the namespace structure found in the targetNamespace prefix of the wsdl file. (E.g. if targetNamespace="http://www.company.com/project in your wsdl, then the folder hierarchy would be: com--company--www--project). There are a number of ways to write a client. The easiest is to use the static approach, that is, use the <web-service_name>_ServiceLocator.java class to get a reference to the stub. The stub acts as a local version of the service, supplying methods with the same signature as that appear on the actual web service interface. So you call those methods and they in turn marshal your data and send it across the wire. Those methods will return the same types as you declared in your service interface. The harder but more dynamic approach is to create a Call object and fill in the multitude of fields and then call invoke() on the call object. This is the approach usually taken by the Axis 1.4 samples found in the binary distribution jar. I strongly recommend that you read both approaches in the Axis 1.4 samples. -jeff _____
From: Sudhir Sharma [mailto:[EMAIL PROTECTED] Sent: Thursday, October 18, 2007 10:10 AM To: axis-user@ws.apache.org Subject: java client from wsdl Hi, I am new to web services and axis. I have a webservice in .NET that is into production. I need to make a java client from the wsdl of that web service.can anyone help me how to automaticaly generate a java client from the wsdl.I am using axis 1.4 and Tomcat 5.0 Thanx in advance. Thanks & Best Regards, Sudhir Sharma
