How to edit the WSDL

Question

I noticed a few limitations of an automatically generated web service
under WLS 7.0, and I am wondering if there is a way to manually edit
files to overcome these limitations:
- the parameter names have no meaningful names, such as string0,
string1, etc. This needs to be changed to at least use the names given
to the parameters in the EJB. I remember putting in a CR a while back,
but this has not been implemented yet.
- The documentation field says 'todo'. It would be nice to be able to
add some explanatory text there.
I looked for the WSDL file in the web-services.war file but could not
find it. Any pointers as to whether/how this stuff can be edited?
Thanks,
Joop Kaashoek

Answer 1

Indeed, you can do this. But if you have non-built in data types as paramaters
it gets pretty tricky.
manoj cheenath wrote:
You can change the parameter/operation name in the generated
WSDL file by editing the web-services.xml file in the web-inf dir
(inside the war file). This file is generated by servicegen, but can
replaced before deploying the service.
regards,
-manoj
"Joop Kaashoek" <[email protected]> wrote in message
news:[email protected]...
Hi Mike,
Thanks very much for your help, I have sent a request to '[email protected]'.
Regards,
Joop
Michael Wooten wrote:
Hi Joop,
I see. No, I don't work in "development" or have any knowledge of what
features are
going to be in the product. I work in the "services" (i.e. professionalservices)
division, which is primarily tasked with figuring out (and showingothers) how the
stuff works :-)
Individuals from "development" (i.e. product managers, developers,architects, etc.)
do monitor this newsgroup, so I think you should create another postthat has a subject
like "Need static or JSP-based WSDL added back to .war". The subject forthis current
post, sounded like you wanted to know how to edit the WSDL (which Ithink I answered
to your satisfaction), but it sounds like you really just want acapability that
was in WLS 6.1, back in WLS 7.0 :-)
I'm assuming that you already know that you can extract the "static"WSDL from the
client.jar and put it anywhere in the .war, you like. The context rootwill be the
name of the .war file, without the file extension. For instance, if your.war file
is hello.war, the context root will be hello. If you then put the"static" WSDL (which
you extracted from the client.jar), into the root directory for for thisWeb Application,
the URL to it would be something like:
http://localhost:7001/hello/HelloService.wsdl
Regards,
Mike Wooten
Joop Kaashoek <[email protected]> wrote:
Your explanation makes sense, but the implementation does not make
sense
to me. This should
clearly be on the list of things to fix. Our partners use .NET or other
technologies, we
want to be able to publish a meaningful self-documented WSDL document(with
meaningful
parameter names and documentation) on our server, not as part of aweblogic-specific
Java
client jar.
Can you indicate whether this is being worked on?
Regards,
Joop
Michael Wooten wrote:
Hi Joop,
The assumption here, is that the client will download your client.jar(or whatever
you named it in your <clientgen> Ant task), and use a file:// URL to
access
it (the
"persisted" WSDL file) from within this archive :-)
If you use the Web Services Technology Stack from BEA
(lib\webserviceclient.jar)
on the client-side, editing this file affects the construction of theSOAP message
that is sent to the Web service, which I'm assuming is hosted on an
instance
of WLS
7.0. The names for the input parameters (and return value), will be
set
to those
that you specified in this WSDL, which is one of the things you said
you
wanted to
be able to do.
If you don't use the Web Services Technology Stack from BEA on the
client-side,
there
is still a very high probability that the WSDL processor of the tool
you
use, will
use this WSDL to create the SOAP message sent to your web service,
which
again is
assumed to be hosted on an instance of WLS 7.0.
If you use the "dynamically generated" WSDL (as opposed to the one inthe client.jar),
you will get the "generic" parameter names specified in it. The
"dynamically
generated"
WSDL is accessed by concatenating "?WSDL" to the location attribute,
of
your <service>
element.
Make sense?
Regards,
Mike Wooten
Joop Kaashoek <[email protected]> wrote:
Mike,
How can editing this client file make any difference to the web
service
itself?
Joop
Michael Wooten wrote:
Hi Joop,
The "persisted" WSDL file is in the .jar file, for the client ;-)
The name of this .jar file is set using either of the following:
1. The clientJarName attribute, of the <client> sub-element for
your
<servicegen>
task, or
2. The clientJar attribute, of the <clientgen> task.
The path leading to the .wsdl file, is determined by the value youassign
to the
packageName attribute (in either of the above tasks).
Regards,
Mike Wooten
Joop Kaashoek <[email protected]> wrote:
I noticed a few limitations of an automatically generated web
service
under WLS 7.0, and I am wondering if there is a way to manuallyedit
files to overcome these limitations:
- the parameter names have no meaningful names, such as string0,
string1, etc. This needs to be changed to at least use the namesgiven
to the parameters in the EJB. I remember putting in a CR a whileback,
but this has not been implemented yet.
- The documentation field says 'todo'. It would be nice to beable
to
add some explanatory text there.
I looked for the WSDL file in the web-services.war file but couldnot
find it. Any pointers as to whether/how this stuff can be edited?
Thanks,
Joop Kaashoek