This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 165249 - Webservice tester not working properly
Summary: Webservice tester not working properly
Status: RESOLVED WONTFIX
Alias: None
Product: webservices
Classification: Unclassified
Component: JAX-WS (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-15 10:13 UTC by msreekanth
Modified: 2009-05-15 13:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description msreekanth 2009-05-15 10:13:17 UTC
Hi ,

I am trying to open the hello-jaxws2.2 sample from the latest build of glassfishv3 build 47b sdk.When I open the project
and run it, it works fine.While I want to test the webservice listed under the webservices using test web service, I see
the below error in browser:

Exceptions details : null
java.lang.NullPointerException at
org.glassfish.webservices.monitoring.WebServiceTesterServlet.doGet(WebServiceTesterServlet.java:145) at
org.glassfish.webservices.monitoring.WebServiceTesterServlet.invoke(WebServiceTesterServlet.java:100) at
org.glassfish.webservices.EjbWebServiceServlet.service(EjbWebServiceServlet.java:110) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at
com.sun.grizzly.http.servlet.FilterChainImpl.doFilter(FilterChainImpl.java:188) at
com.sun.grizzly.http.servlet.FilterChainImpl.invokeFilterChain(FilterChainImpl.java:137) at
com.sun.grizzly.http.servlet.ServletAdapter.service(ServletAdapter.java:322) at
com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:165) at
com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100) at
com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:208) at
com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:746) at
com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:655) at
com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:905) at
com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:161) at
com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:136) at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103) at
com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89) at
com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76) at
com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53) at
com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57) at
com.sun.grizzly.ContextTask.run(ContextTask.java:69) at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619)
Comment 1 Milan Kuchtiak 2009-05-15 13:41:28 UTC
It's a GlassFish V3 bug.
Please, report the issue to GlassFish team ( https://glassfish.dev.java.net/ )

Since the GlassFish V3 is under development it may happen that some features are not ready yet.