Axis wsdl2java overwriting class files

[Todd Farmer]

Hi,

I'm just beginning to work through web services, and I'm having a difficult time. I created a test business object (com.greenbuildingpages.services.DistanceCalculator) and ran java2wsdl against it:

java org.apache.axis.wsdl.Java2WSDL -o wp.wsdl -l"http://localhost:8080/axis/services/distance" -n "urn:Example" -p"com.greenbuildingpages.services" "urn:Example" com.greenbuildingpages.services.DistanceCalculator

This created the wdsl file:

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="urn:Example" 
xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="urn:Example" 
xmlns:intf="urn:Example" 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" 
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" 
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<!--WSDL created by Apache Axis version: 1.2.1
Built on Jun 14, 2005 (09:15:57 EDT)-->
   <wsdl:message name="getDistanceResponse">
      <wsdl:part name="getDistanceReturn" type="soapenc:int"/>
   </wsdl:message>
   <wsdl:message name="getDistanceRequest">
   </wsdl:message>
   <wsdl:portType name="DistanceCalculator">
      <wsdl:operation name="getDistance">
         <wsdl:input message="impl:getDistanceRequest" name="getDistanceRequest"/>
         <wsdl:output message="impl:getDistanceResponse" name="getDistanceResponse"/>
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name="distanceSoapBinding" type="impl:DistanceCalculator">
      <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
      <wsdl:operation name="getDistance">
         <wsdlsoap:operation soapAction=""/>
         <wsdl:input name="getDistanceRequest">
            <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:Example" use="encoded"/>
         </wsdl:input>
         <wsdl:output name="getDistanceResponse">
            <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:Example" use="encoded"/>
         </wsdl:output>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name="DistanceCalculatorService">
      <wsdl:port binding="impl:distanceSoapBinding" name="distance">
         <wsdlsoap:address location="http://localhost:8080/axis/services/distance"/>
      </wsdl:port>
   </wsdl:service>
</wsdl:definitions>
 

I then ran wsdl2java against this generated wsdl document:

java org.apache.axis.wsdl.WSDL2Java -o ./main/src/java -d Session -s -S true -Nurn:Example com.greenbuildingpages.services wp.wsdl

When this completed, I had the additional artifacts that I was expecting (DistanceCalculatorService,java, DistanceCalculatorServiceLocator.java, etc.). But my original DistanceCalculator.java file had been modified (into an interface).

I'm sure I likely have the command line arguments mixed up. Can somebody help me or point me towards their favorite Axis tutorial that might help me through this?

Thanks!

Todd Farmer

[ July 06, 2005: Message edited by: Todd Farmer ]

[ July 06, 2005: Message edited by: Todd Farmer ]
[ July 08, 2005: Message edited by: Todd Farmer ]

[Tim West]

I'm no expert, but sounds like you're doing it right - what you want to do is specify a different output directory for the generated files. I'm not sure of the command line option (-o, probably, which you already use), but the wsdl2java Ant task can be used like this:

    <axis-wsdl2java
        output="${client.build.dir}"
        testcase="false"
        verbose="true"
        url="${booking.wsdl}">
    </axis-wsdl2java>

In general, with Web services (regardless of the Java toolkit used) I find it necessary to:

Keep the client and server bindings in separate directories (or in separate JARs).

Never put the two directories/JARs on the same classpath, when compiling or running the client or server application. Only put the server JAR/dir on the server classpath, etc. This prevents the inevitable namespace clashes (if the same packages are used).

Have neither on the classpath when regenerating the binding files themselves (e.g., when running wsdl2java). On some platforms (e.g., Weblogic) having one on the classpath produces *baffling* errors.

I also find it simplifies things if you generate the client bindings into a different package than the server ones. E.g., org.jacksonwest.travel.client.binding for the client, and org.jacksonwest.travel.server.binding for ther server.

-Tim

[edit: it might be nice to edit your post and shorten that massive line that makes this thread so hard to read...]
[ July 06, 2005: Message edited by: Tim West ]

[Todd Farmer]

Thanks for the help and for the suggestions!