There are a bunch of doc/lit specific bugs that have been fixed in both the
straight 1.2 alpha release and the latest Axis CVS. Originally we were
using the straight 1.2 alpha release - then we started playing with WSS4J
and have been using the build from Axis CVS that they are using ever since.
As to your template WSDL suggestion... not sure what the best solution is
there. The way the Axis code works right now the "right" way to do it is to
let Axis generate the WSDL for you once you've published your doc/lit
service - Axis will then fill in the appropriate endpoint URL. It is only
because we don't trust Axis right now to emit correct WSDL that we end up in
<wsdlFile> hell, having to host our included schemas and changing our WSDL
endpoints per deployment.
One can also argue that if you've gone through the trouble of putting a lot
of comments into your WSDL then you would want to make use of <wsdlFile> as
well.
The bigger problem though is that WSDL requires service endpoints to be in
the WSDL AT ALL. I'm not sure if this is being addressed by either WSDL 1.2
or WSDL 2.0.
-Jon
-----Original Message-----
From: Nelson Minar [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 3:33 PM
To: Anderson Jonathan
Cc: [EMAIL PROTECTED]
Subject: RE: Doc/Literal support in axis
I was looking again at your excellent cookbook for doing doc/literal
in Axis and had a couple of followup practical questions:
You specify using Axis 1.2 alpha. Is there any hope with Axis 1.1? And
do you mean the alpha release or the latest Axis CVS?
You mention that if you use <wsdlFile>,
>Endpoint location URLs need to be modified per deployment, since you
>don't want your production WSDL to reference localhost:8080.
I find the hardcoded URLs are a really frustrating part of working
with WSDL. It would be easy to add a simple templating system into
Axis to smooth this over, just load a template WSDL and rewrite it at
runtime to have the right URL. Is this a good idea?
