comparing JAX-RPC web service created with deploytool and with plain wsdeploy (Sun J2EE 1.4 RI)

From: Merten Schumann <>
Date: Fri, 16 Jul 2004 15:22:49 +0200


playing with Sun J2EE RI 1.4, I followed the whitepapers

> -----Original Message-----
> From: Doug Kohlert
> Sent: Monday, July 12, 2004 7:26 PM
> To:
> Subject: Re: Attention JAXRPC RI Users: FeedBack needed
> Merten,
> On the JAXRPC page at:
> there is a section on documentation. I believe the whitepaper on
> Understanding your JAX-RPC SI Environment has documentation on the ant

> tasks.

to create a JAXRPC web service by hand, not by using deploytool. I want
to understand what's going on behind the scenes.

The interesting thing is, when I create the HelloService sample
according to the white papers, I do end up with a lot more classes in
the .war file (...RequestStruct.class, ...Tie.class). In the .war
created by deploytool, I have this sun-web.xml and webservices.xml
stuff, which is not mentioned in whitepapers (since it's not portable, I

Makes the mapping file (created in wscompile step) the difference? It's
in the deploytool generated .war. In the white papers it's not used in
the wsdeploy step ...

Is the .war file generated by wsdeploy (AAA) portable? When I do open it
in deploytool, its different from the deploytool generated (BBB) one. In
example, on tab "General", AAA is shown there as a servlet with Servlet
Class "com.sun.xml.rpc.server.http.JAXRPCServlet", for BBB is shown
under "Service Endpoint Implementation" "helloservice.HelloImpl". And
for BBB there is an "Endpoint" tab, which not exists for AAA. I guess
this all is just due to missing "sun-web.xml" and "webservices.xml"
files in AAA and AAA is portable.

Thank you!

To unsubscribe, e-mail:
For additional commands, e-mail: