[jbossws-issues] [JBoss JIRA] Updated: (JBWS-1652) ServiceEndpoint requirements for JBossESB

ServiceEndpoint requirements for JBossESB ----------------------------------------- Key: JBWS-1652 URL: http://jira.jboss.com/jira/browse/JBWS-1652 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public(Everyone can see) Components: jbossws-jaxws Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: jbossws-2.1.0 JBossESB implements what it calls a "JBossWSAdapter" (http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/core/listeners/...). This class allows the ESB to expose JBossWS endpoints through the ESB i.e. over all transport protocols supported by the ESB. In order to do this, JBossWSAdapter currently relies on a number of non-public JBossWS classes (tested against jbossws-1.0.3.SP1 only). After talking with Thomas (at JavaOne), we established that JBossWS will have a public API that will fit our requirements. This JIRA is just to track the ESB requirements in this area. So the ESB needs the following: 1. The ability to "lookup" a JBossWS ServiceEndpoint (or its equivalent in the new API). We currently use the ServiceEndpointManagerFactory to do this. 2. The ability to invoke the ServiceEndpoint to process a SOAP payload (ala the "ServiceEndpoint.handleRequest" method in jbossws-1.0.3.SP1). 3. The ability to register/deploy endpoint implementations. Thomas showed me how this can be done, but I forget the exact code now without having the code in front of me :-) 4. The ability to get the endpoint WSDL from the ServiceEndpoint instance (ala the ServiceEndpoint.handleWSDLRequest method in jbossws-1.0.3.SP1).