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.
The only time I've ever been able to use the "Test web service" feature in NetBeans of the past year is when I create new projects and a Hello World service that echo's a String. All the web services I have created in NetBeans that I actually want to test have always given me the following exception when I click the "Test Web Service" context menu item: Exceptions details : java.lang.RuntimeException: Cannot find the correct port class. javax.servlet.ServletException: java.lang.RuntimeException: Cannot find the correct port class. at com.sun.enterprise.webservice.monitoring.WebServiceTesterServlet.initializePort(WebServiceTesterServlet.java:551) at com.sun.enterprise.webservice.monitoring.WebServiceTesterServlet.doGet(WebServiceTesterServlet.java:166) at com.sun.enterprise.webservice.monitoring.WebServiceTesterServlet.invoke(WebServiceTesterServlet.java:106) at com.sun.enterprise.webservice.JAXWSServlet.doGet(JAXWSServlet.java:176) at javax.servlet.http.HttpServlet.service(HttpServlet.java:705) at javax.servlet.http.HttpServlet.service(HttpServlet.java:818) at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:398) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:277) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:258) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:189) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:611) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:564) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:81) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:193) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:611) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:558) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1067) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:611) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:558) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1067) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:255) at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:618) at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:549) at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:790) at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:326) at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:248) at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:199) at com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTask.doTask(PortUnificationPipeline.java:345) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252) at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:93) Caused by: java.lang.RuntimeException: Cannot find the correct port class. at com.sun.enterprise.webservice.monitoring.WebServiceTesterServlet.initializePort(WebServiceTesterServlet.java:538) ... 32 more When I execute my own client application, the service works fine.
Test web service is a feature in glassfish and there's already filed https://glassfish.dev.java.net/issues/show_bug.cgi?id=361 for improving it. Cannot help more without knowing some other details - like your version of glassfish, how does your service looks like (is the service from wsdl or from java, how does the wsdl of the deployed service looks like...)
The services I'm having trouble with are written from scratch in NetBeans, not from an existing WSDL. Most, if not all methods take complex types as parameters and return complex types. For example, a Reservation object that contains a bunch of fields, a reference to a Hotel object, an array of RoomOptions objects, etc... I would not expect the simple web based tester to let me create Reservation objects and submit them as requests. But I also would not expect to get stack dumps. Right now I'm using Sun Application Platform SDK Update 3 Preview 2 (9.1), NetBeans 5.5.1, JDK 1.5.0_11, Windows XP.
This is a limitation of JAX-WS WS tester web application. This is difficult to fixed without cooperation with JAX-WS team. See the enhancement : https://jax-ws.dev.java.net/issues/show_bug.cgi?id=213 I am changing this to an enghancement