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?
[ July 06, 2005: Message edited by: Todd Farmer ]
[ July 06, 2005: Message edited by: Todd Farmer ] [ July 08, 2005: Message edited by: Todd Farmer ]
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:
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.
[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 ]