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.
Used the javax.xml.ws.Provider<SOAPMessage> interface in MESSAGE mode to implement a Web Service. When I include service this in a service assembly (of a composite application), the casa editor of Netbeans shows the service as a "Consumer" of the wsdl port but it is actually a "Provider".
balsmn, Can you attach your projects? We need to take a look at the jbi.xml generated by the EJB project. Thanks, -- Tientien Li
Created attachment 66157 [details] Sample Provider, Composite Assembly - Netbeans projects
I have attachted the Netbeans projects including the Webservice and its corresponding composite application containing it. The WSDL was first designed and the java artifcats implementing using provider was generated from the wsdl. -- balsmn
Girish, Can you take a look at this problem? The jbi.xml generated for the servlet-based web service, HelloProvider, SU has only a consume endpoint: <consumes endpoint-name="javaee_SimpleProviderPort" interface-name="ns0:SimpleProviderPortType" service-name="ns0:SimpleProviderService"/> However, the java code, SimpleProvider.java, implements the javax.xml.ws.Provider interface: @WebServiceProvider(serviceName = "SimpleProviderService", portName = "SimpleProviderPort", targetNamespace = "http://j2ee.netbeans.org/wsdl/SimpleProvider", wsdlLocation = "WEB-INF/wsdl/SimpleProvider/SimpleProvider.wsdl") public class SimpleProvider implements javax.xml.ws.Provider<javax.xml.soap.SOAPMessage> { Thanks,
Composite application project does not yet auto generates the endpoints for Web services using JAX-WS provider interface. (i.e using annotation @WebServiceProvider). We need to fix/enhance this.
Changing the issue type to enhancement.