Why context listeners not configured in web.xml in some way of WS implementation?

[Kumar Raja]

Hello All,

My question is in reference to Ivan's notes (Chapter 9). I'm comparing the setup between generating service and client artifacts from WSDL and the implementing XML Based, Document style WS.

Under section 9.3 "Create WSDL and Generate Service Implementation from XMLSchema", there is no explicit inclusion of WSServletContextListeners and Servlet mapping is not included in web.xml. Also, there is no reference to the usage of sun-jaxws.xml in this case.

But under section 9.4, "XML-Based, Document Style JAX-WS Web Service", there is a reference to the usage of Listeners, Servlet Mappings and the usage of sun-jaxws.xml.

Why there is a difference here? In what way having or not having the listeners configured in web.xml, will have impact on the Web Service.

Please advice.

Thanks

[Dan Drillich]

Kumar,

It's interesting to see that in section 9.3 we see a shell web.xml -

<?xml version="1.0" encoding="UTF-8"?> <web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"> <session-config> <session-timeout>30</session-timeout> </session-config> <welcome-file-list> <welcome-file>index.jsp</welcome-file> </welcome-file-list> </web-app>

Whereas in section 9.4, we see a full fledged web.xml -

<?xml version="1.0" encoding="UTF-8"?> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation=" http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5"> <display-name>JAX-WSXMLCalculator</display-name> <listener> <listener-class> com.sun.xml.ws.transport.http.servlet.WSServletContextListener </listener-class> </listener> <!-- The URL pattern of the service is specified here too. See next step! --> <servlet> <display-name>XMLCalculator</display-name> <servlet-name>XMLCalculator</servlet-name> <servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>XMLCalculator</servlet-name> <url-pattern>/xmlcalc/*</url-pattern> </servlet-mapping> </web-app>


Not sure if JAX-WS RI web services deployment made simplified sheds light on it.

Regards,
Dan

[Ivan Krizsan]

Hi!
@Kumar: I will consider the question answered by Dan.
I do not hesitate to attempt additional clarification, upon request.
Best wishes!

[Kumar Raja]

Thank you Dan and Ivan.

[Ivan Krizsan]

Hi!

Dan Drillich wrote:
It's interesting to see that in section 9.3 we see a shell web.xml -
...
Whereas in section 9.4, we see a full fledged web.xml -

A very good observation!
Section 9.4 has a more complete web.xml deployment descriptor due to the fact that the Metro deployment descriptor, sun-jaxws.xml, is also used in the example.
At that time, I were not able to make the example work without the web.xml deployment descriptor configured as seen in the study notes. This may have changed with GlassFish v3 - I haven't tried.
Best wishes!