project_key: SOA I'm attempting to proxy a Teiid SOAP service hosted in the same SOA install. When deploying the ESB project I get the following error when the ESB tries to load the WSDL. I've debugged it partially are it appears that the host never gets into the HTTP Method even though the correct URL is supplied. This should be reproducible w/o my SOAP service. Caused by: org.jboss.soa.esb.ConfigurationException: java.lang.IllegalArgumentException: host parameter is null at org.jboss.soa.esb.actions.soap.proxy.SOAPProxy.<init>(SOAPProxy.java:193) ... 66 more Caused by: java.lang.IllegalArgumentException: host parameter is null at org.apache.commons.httpclient.HttpConnection.<init>(HttpConnection.java:205) at org.apache.commons.httpclient.HttpConnection.<init>(HttpConnection.java:154) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionWithReference.<init>(MultiThreadedHttpConnectionManager.java:1105) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$ConnectionPool.createConnection(MultiThreadedHttpConnectionManager.java:741) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.doGetConnection(MultiThreadedHttpConnectionManager.java:469) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.getConnectionWithTimeout(MultiThreadedHttpConnectionManager.java:394) at org.jboss.soa.esb.http.ESBMultiThreadedHttpConnectionManager.getConnectionWithTimeout(ESBMultiThreadedHttpConnectionManager.java:74) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:152) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324) at org.jboss.soa.esb.actions.soap.RemoteWsdlLoader.load(RemoteWsdlLoader.java:90) at org.jboss.soa.esb.actions.soap.AbstractWsdlContractPublisher.getWsdl(AbstractWsdlContractPublisher.java:199) at org.jboss.soa.esb.actions.soap.proxy.SOAPProxyWsdlLoader$Puller.pull(SOAPProxyWsdlLoader.java:521) at org.jboss.soa.esb.actions.soap.proxy.SOAPProxyWsdlLoader.load(SOAPProxyWsdlLoader.java:157) at org.jboss.soa.esb.actions.soap.proxy.SOAPProxy.<init>(SOAPProxy.java:188) ... 66 more 12:01:57,726 INFO [EsbDeployment] Destroying 'ProductProxy.esb'
Here's the project.
Attachment: Added: SOA-2519-jira.zip
You removed HttpProtocol from the list of configurators. configurators=AuthBASIC, HttpProtocol Is this not mentioned in the documentation?
Here is the doc I've been referring to, and if I'm reading it correctly, that's an optional property. http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html/ESB_Programmers_Guide/chap-SOA_ESB_Programmers_Guide-Out-of-the-box_Actions.html#sect-SOAP-SOAPPROXY Is my understanding incorrect? For the service I have configured, I need to send Basic credentials, and it looks like I was using the clientCredentialRequired property incorrectly. I've change that value to be false, but it doesn't seem to matter.
The exception you are seeing is caused by the fact you have not configured the HttpProtocol. While this property is optional, defaulting to HttpProtocol, you must include that configurator (or an alternative) if you specify it. The documentation does include both but is not as clear as it should be.
I just spoke to Ken Johnson following the defect review and we discussed what the doc might say. One issue that it's struggled with in this case is how to set up the HTTP config for different scenarios. All of our examples seem to point to a SSL Socket implementation sample. I think we should document the SSL config, as well as a plain HTTP config and a plain HTTP config with BASIC Auth.
The documentation that appears to be missing is the descriptions of each configurator and what they do, including whether they are required or optional. If we have this in place then the configuration should be clearer.
Candidate for SOA 5.1.0. Needs clearer documentation.
Blocker for SOA 5.1.0
Writer: Added: dlesage
Link: Added: This issue depends JBESB-3575
Updated in ESB 4.9CP branch
Section has been merged from upstream into product document.
Release Notes Docs Status: Added: Not Required