JAX-WS @Resrouce injection still not working

[Mike London]

If you want the underlying information of who's calling your web service (say, the remote IP), the only way I know how to do it is to enable "Resource injection".

However, no matter what I do, it will not work.

Here's the setup code:

// Enable dependency injection on web service context.
@Resource
WebServiceContext wsContext;

at the top of a JAX-WS web service.

----------------------------------

Then, later in the web service code, inside a @WebMethod:

public String getLatest()
{

/* NullPointerException happens here ---> */ MessageContext context = wsContext.getMessageContext();

.
.
.

}

???

When I run the client web service, I always get a NullPointerException as shown at the line above.

Web.xml seems to have the correct information in it so I'm totally stumped.

Has anyone gotten this working?

Thanks in advance.

Mike

[Ivan Krizsan]

Hi again!
Have you tried to deploy your web service to GlassFish (I recall you said you used Tomcat last time we discussed this issue)?
This way, you can hopefully determine if your web service really has problems or if the problem is the Tomcat environment.
Best wishes!

[Mike London]

Hey,

I downloaded GF3, but MyEclipse doesn't yet support it (until 8.5 which is due almost anytime). I've actually been trying to switch to Intellij IDEA for development (their tech support is incredible!), but, unfortunately, their 9.0.1 product has a bug with web services too! This bug will (hopefully) be fixed in 9.0.2...due out maybe Mar, 2010.

Therefore, I remain in "stuck-ville" for the moment.

I appreciate all your replies!

Thanks.

Mike

[Ivan Krizsan]

Hi!
You could build a WAR and deploy it manually to the GlassFish server.
Deploying is done by copying the WAR to the following directory in the GlassFish v3 installation directory: glassfish/domains/domain1/autodeploy
The name "domain1" may be different depending on your configuration.
Best wishes!

[Mike London]

Could I use the same client program if I just changed the port to 8001 (the one I used for GF)?

Mike

[Ivan Krizsan]

Hi!

Mike London wrote:Could I use the same client program if I just changed the port to 8001 (the one I used for GF)?

The same web service client program?
Yes, providing there are no changes in the WSDL (except for the endpoint address), there should be no problems.
Best wishes!

[Mike London]

Cool, thanks Ivan!

I'll post back with updates.

[Mike London]

Glassfish gives this main error (part of an error stack) when I try to deploy to autodeploy folder:

Caused by: java.lang.IllegalArgumentException: Servlet [MyWSPortImpl] and Servlet [MyWSDelegate] have the same url pattern: [/MyWSService]

???

[Ivan Krizsan]

Can you post the complete code?
I must admit that I have never seen that kind of error before.

[Mike London]

Hi Ivan,

I'll try to post an example that reproduces the same problem shortly.

Thanks very much for your continuing replies!



Mike

[Mike London]

Hello,

I've now created a very simple JAX-WS Web Service with this code:

 
   package servletws;

   import javax.annotation.Resource;
   import javax.jws.WebService;
   import javax.xml.ws.WebServiceContext;

   @WebService
   public class HelloServlet {
       @Resource WebServiceContext wsContext;

       public String hello(String msg) {
           return "Servlet WS: " + wsContext.getUserPrincipal()   // *** NullPointerException happens here! ***
           + ": " + msg;
       }
   }

The web service deploys and I can get to its WSDL in the browser.

************
HOWEVER....
************

As with my production web service, as soon as the client web service hits the line above where the wsContext.get UserPrincial() is, I get a NullPointerException....as with my previous postings.

My really-simple Web Service Client is this:

    

package servletws;

public class WebServiceClient
{

    /**
     * @param args
     */
    public static void main(String[] args)
    {
        HelloServletService service = new HelloServletService();
        HelloServletDelegate delegate = service.getHelloServletPort();
        
        delegate.hello("hello there Test!");
      
    }
}

=========

The WSDL is this:

    

<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3-hudson-390-. -->
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://servletws/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="HelloServletService" targetNamespace="http://servletws/">
  <types>
    <xsd:schema>
      <xsd:import namespace="http://servletws/" schemaLocation="HelloServletService_schema1.xsd"/>
    </xsd:schema>
  </types>
  <message name="hello">
    <part element="tns:hello" name="parameters"/>
  </message>
  <message name="helloResponse">
    <part element="tns:helloResponse" name="parameters"/>
  </message>
  <portType name="HelloServletDelegate">
    <operation name="hello">
      <input message="tns:hello"/>
      <output message="tns:helloResponse"/>
    </operation>
  </portType>
  <binding name="HelloServletPortBinding" type="tns:HelloServletDelegate">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="hello">
      <soap:operation soapAction=""/>
      <input>
        <soap:body use="literal"/>
      </input>
      <output>
        <soap:body use="literal"/>
      </output>
    </operation>
  </binding>
  <service name="HelloServletService">
    <port binding="tns:HelloServletPortBinding" name="HelloServletPort">
      <soap:address location="http://localhost:8000/ResWebServiceTest/HelloServletPort"/>
    </port>
  </service>
</definitions>

===============

The web.xml is this:

    

<?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">
  <servlet>
  	<description>JAX-WS endpoint - HelloServletService</description>
  	<display-name>HelloServletService</display-name>
  	<servlet-name>HelloServletService</servlet-name>
  	<servlet-class>
  		com.sun.xml.ws.transport.http.servlet.WSServlet
  	</servlet-class>
  	<load-on-startup>1</load-on-startup>
  </servlet>
  <servlet-mapping>
  	<servlet-name>HelloServletService</servlet-name>
  	<url-pattern>/HelloServletPort</url-pattern>
  </servlet-mapping>
  <welcome-file-list>
    <welcome-file>index.jsp</welcome-file>
  </welcome-file-list>
  <listener>
  	<listener-class>
  		com.sun.xml.ws.transport.http.servlet.WSServletContextListener
  	</listener-class>
  </listener></web-app>

============

And the log error dump is:

   
Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: java.lang.NullPointerException
	at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188)
	at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:116)
	at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
	at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
	at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
	at $Proxy34.hello(Unknown Source)
	at servletws.WebServiceClient.main(WebServiceClient.java:14)
Caused by: java.lang.NullPointerException
	at servletws.HelloServlet.hello(HelloServlet.java:15)
	at servletws.HelloServletDelegate.hello(HelloServletDelegate.java:15)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:246)
	at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
	at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
	at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
	at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
	at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
	at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
	at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
	at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
	at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
	at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
	at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
	at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServletDelegate.java:129)
	at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:160)
	at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:75)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
	at java.lang.Thread.run(Thread.java:619)

 

I now have two projects (the service and the client) I can post if there's someway to post binary files.

Look forward to any possible reasons why I keep getting NullPointerExceptions.

Thanks very much.

-- Mike

[Mike London]

I've now reproduced this behavior (bug?) on two Tomcat installations?

Can anyone see what the problem might be?

Thanks.

Mike

[Ivan Krizsan]

Hi!
Try adding a file named "sun-jaxws.xml" next to the web.xml deployment descriptor with the following contents:

<?xml version="1.0" encoding="UTF-8"?>
<endpoints version="2.0" xmlns="http://java.sun.com/xml/ns/jax-ws/ri/runtime">
  <endpoint implementation="servletws.HelloServlet" name="HelloServlet" url-pattern="/HelloServletPort"/>
</endpoints>

Best wishes!

[Mike London]

Hi Ivan,

Here's the sun-jaxws.xml file that MyEclipse already created in the web-inf directory:

    

<?xml version = "1.0"?>
<endpoints version="2.0"
	xmlns="http://java.sun.com/xml/ns/jax-ws/ri/runtime">
	<endpoint name="HelloServletPort"
		implementation="servletws.HelloServletDelegate"
		url-pattern="/HelloServletPort">
	</endpoint></endpoints>

I'm using the MyEclipse IDE (now version 8) and it's (supposedly) generating everything.

My best guess at this point is that MyEclipse is not putting in a required library or something like that (yet I can run the web service if I remove the attempt to access the context).

I can send you a WAR file if you want to see if a generated client you create successfully runs against this service.

Let me know.

Thanks.

Mike

[Ivan Krizsan]

Hi!
NetBeans also generate the Sun webservice deployment descriptor behind the scenes, while the standard version of Eclipse do not.
I would really like to take a look at that WAR, so please send it to me. Note that you do not accept private messages, so I cannot contact you using private messages.
Best regards!

[Mike London]

The solution to this @Resource NullPointerProblem, for me anyway, was to create a setter and getter method to apply the @Resource WebServiceContext wsContext variable.

Something like:

@Resource WebServiceContext wsContext

.
.
.

private void setWsContext(WebServiceContext wsContext)
{
// do stuff with the context here....
}

// I also created a public getter, but I'm not sure this is needed.

-----------

Clearly the @Resource was being injected by the Tomcat 6.0.26 container so I'm not sure why code like that in "Java Web Services, Up and Running" simply did not work.

This was all quite confusing.

Also, MyEclipse 8.5 (and earlier versions) doesn't seem to like to re-create an existing web service when you add new methods or change the service's interface. I had nothing but problems using it. The only way around this was to create a brand new project each time I modified the project and copy everything into it. MyEclipse refused (for me) to re-create/update the delegate class for an existing service.

Hope this update is useful.

- M