In my opinion, it would be worth mentioning that the web.xml does not
need anything special related to jaxrpc.
The source of my confusion was that in the old xrpcc times, we had to
put a jaxrpc servlet reference into the web.xml, with a servlet init
parameter referencing the properties file.
I guess all this is now left to wsdeploy.
John
-----Original Message-----
From: Alessio Cervellin [mailto:alessio.cervellin_at_sun-cs-italy.com]
Sent: Friday, January 07, 2005 1:35 PM
To: users_at_jax-rpc.dev.java.net
Subject: Re: jwsdp tutorial
Furton, John wrote:
> I was trying to figure out the proper content of the web.xml file for
> wsdeploy but:
>
> - The whitepaper (Understanding your JAX-RPC SI Environment)
> does not show an example
because the web.xml issue is not something related to jax-rpc, it's just
a standard web-app descriptor... for the war of a webservice, usually it
doesn't need any special paramater in the web.xml, i.e. a web.xml like
this one could be good:
<?xml version="1.0" encoding="UTF-8"?>
<web-app>
<display-name>My webapp</display-name>
<description>my JAX-RPC based webapp</description>
</web-app>
> - The jwsdp 1.5 and 1.4 tutorials don't even talk about
> wscompile and wsdeploy anymore.
maybe 'cause these tools are well explained in the whitepaper you
previously mentioned ;)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net