[
https://jira.jboss.org/jira/browse/JBESB-3021?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-3021:
-------------------------------------
The mapping in HttpClient is the default expected for each protocol, our problem is that
we were overwriting that on each invocation. More a misunderstanding in the original
implementation of the HttpClientFactory etc, than any issue with HttpClient.
The fix you have added is what we should really have been doing in the first place,
creating our own version and using that explicitly.
SOAPProxies on different services shares configuration
------------------------------------------------------
Key: JBESB-3021
URL:
https://jira.jboss.org/jira/browse/JBESB-3021
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Environment: ER4
Reporter: Jiri Pechanec
Assignee: David Ward
Priority: Critical
Fix For: 4.7 CP1
Attachments: soapproxy-breaker.zip, two_proxies.log.gz
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