SOAPProcessor picks up wrong WSDL when two WS Endpoints with the same name are deployed via different deployments ----------------------------------------------------------------------------------------------------------------- Key: JBESB-3420 URL: https://jira.jboss.org/browse/JBESB-3420 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Magesh Kumar B Fix For: 4.9 CP1 JBossWS creates deployments with the format jboss.ws:context=foo,endpoint=fooservice If two deployments are deployed like this jboss.ws:context=foo1,endpoint=fooservice jboss.ws:context=foo2,endpoint=fooservice Then the following <property name="jbossws-endpoint" value="fooservice"/> will find any one of the deployment above that may not be what we intended. The property should be changed to use the deployment name rather than just the endpoint's shortname to avoid picking up the wrong WSDL <property name="jbossws-endpoint" value="jboss.ws:context=foo1,endpoint=fooservice"/> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira