[esb-issues] [JBoss JIRA] Updated: (JBESB-3186) HttpClient on different services shares configuration

[ https://jira.jboss.org/jira/browse/JBESB-3186?page=com.atlassian.jira.plu... ] Kevin Conner updated JBESB-3186: -------------------------------- Description: The HttpClient configuration can be shared between a number of services, this was originally discovered as part of the SOA 5 work when testing out SOAPProxy. The issue is not specific to SOAPProxy and exists in previous streams, including SOA 4.3. The changes made to fix the issue in SOA 5, excluding those directly related to SOAPProxy, need to be ported across. was: If a jboss-esb.xml file contains definition of two services and each uses SOAPProxy, then the configuration is shared between them. Check the attached example 1) Remove Proxy-breaker service from the config file, deploy and do ant runtest. The execution is performed correctly and target service is invoked. 2) Enable Proxy-breaker service but disable <http-client-property name="protocol-socket-factory"... in it, deploy and do ant run test. Although you are invoking the first service the invocation will fail due to strict SSL setting. 3) Enable Proxy-breaker service and enable <http-client-property name="protocol-socket-factory"... in it, deploy and do ant run test. The execution is performed correctly and target service is invoked. It proves that SOAPProxy settings on Proxy-breaker service DIRECTLY infulennces SOAPProxy settings of Proxy service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira