Mark,
Very good questions. The short answer is JAX-WS is designed to run on
either a JAX-WS enabled servlet container
such as Tomcat as well as a Java EE 5 app server. The JAX-WS samples
are configured to run with the JAX-WS
standalone servlet that can be run on a non JAva EE 5 servlet
container. The Glassfish examples are for running
JAX-WS endpoints on a Java EE 5 container. So, to be compatible with
Java EE 5 you should use the Glassfish
examples. However, as you have probably discovered, by methods work on
Glassfish as it is a JAX-WS enabled
servlet container.
Thanks for your interest in JAX-WS.
Mark Hansen wrote:
> I'm writing a number of sample web services - testing out different
> aspects of JAX-WS 2.0. I am trying to deploy everything on the
> nighltly build of Glassfish. I rebuild Glassfish regularly.
>
> I am confused by the different packaging in the samples distributed
> with JAX-WS 2.0 vs. the devtests in Glassfish. The JAX-WS samples
> have a sun-jaxws.xml deployment descriptor. Also, in the JAX-WS
> samples, the web.xml is used to deploy a listener
> (WSServletContextListener), and the servlet deployed is WSServlet.
> Also, the version attribute of the <web-app> element is "2.4".
>
> In the Glassfish devtest/webservices/annotations examples, there is no
> sun-jaxws.xml. Instead, there is a sun-web.xml file. Furthermore,
> the web.xml has no listener, and the servlet class is the actual
> JAX-WS endpoint implementation, rather than WSServlet. The version
> number of the <web-app> element is "2.5".
>
> Can someone explain what is going on with these different versions?
> Also, which packaging approach should I use for my samples
> applications to be deployed on Glassfish? Which approach is closer to
> the Java EE 5 standard?
>
> Thanks for any help with this.
>
> -- Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: users-help_at_jax-ws.dev.java.net
>
--
- Doug