[esb-issues] [JBoss JIRA] Commented: (JBESB-3412) webservice_proxy_* WSDL retrieval not associated with correct classloader

webservice_proxy_* WSDL retrieval not associated with correct classloader ------------------------------------------------------------------------- Key: JBESB-3412 URL: https://jira.jboss.org/browse/JBESB-3412 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Components: Examples, Web Services Environment: JDK 1.5 + AS 4.2.3 and JDK 1.6 + AS 5.1.0 Reporter: David Ward Assignee: Kevin Conner Priority: Blocker Fix For: 4.9 Attachments: webservice_proxy_routed.log webservice_proxy_basic, webservice_proxy_security and webservice_proxy_versioning all have problem with their WSDL contracts being empty from the http//localhost:8080/contract/ web application. Light debugging showed that the reason for this is that ContractProviderLifecycleResource, while having it's map being propertly populated with the appropriate lifecycle resource (deployment) ID + ContractProvider instance at deployment, is returning null when the HttpGatewayServlet attempts to get at it's appropriate ContractProvider. The reason is that during the thread of execution behind the HttpGatewayServlet, when calling ContractProviderLifecycleResource.buildKey(svc_cat, svc_name), LifecycleResourceManager.getSingleton().getIdentity() is returning DEFAULT-ID (or whatever it's called) instead of the actual deployment ID. This *USED* to work, so I don't know what changed environment-wise. webservice_proxy_routed doesn't provide a contract (no HTTP endpoints), so it's N/A to that quickstart.