Date of First Response: 2010-06-16 20:55:58 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/682333 Workaround: Workaround Exists Workaround Description: One workaround is to remove additional interfaces from the WSDL, if possible. project_key: SOA The reason for this is that only the last interface contains the wsdl context loaded using our httpclient, forcing prior interfaces to reload using the UrlWsdlLoader. This does not have knowledge of the authentication as we place it on the httpclient and it instantiates its own httpclient.
Link: Added: This issue incorporates JBESB-3276
JBESB-3276 has been closed.
JBESB-3276 has been closed in trunk, which will make its way into SOA 5.1. This issue needs to be split to represent both 'affects' versions independently.
Link: Added: This issue related SOA-2211
Release Notes Docs Status: Added: Documented as Resolved Issue Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-3276 The soapui client failed to load multiple interfaces if authentication was required. This was because only the last interface contained the WSDL context that was loaded using the httpclient, and it is this httpclient that contained the authentication information. By doing so, it forced prior interfaces to reload using the UrlWsdlLoader. The UrlWsdlLoader did not know about the authentication as it instantiates its own httpclient. To fix this problem, a JBoss AOP aspect was created. This intercepts calls to soapUI's WsdlContext$Loader.getWsdlLoader() method so that the EsbWsdlLoader is always returned. As a result, the soapui client can now load multiple interfaces, even if authentication is required
Writer: Added: dlesage
ESB code was in 5.1