noddoux added a comment - Wed, 10 Nov 2010 - 09:52:59 +0100
I remarked this problem. I think it is a regression on the version 4.0.4 of the BC SOAP. It will be corrected in the version 4.1 of the BC SOAP with the addition of the HTTPS support.
noddoux added a comment - Wed, 10 Nov 2010 - 09:52:59 +0100 I remarked this problem. I think it is a regression on the version 4.0.4 of the BC SOAP. It will be corrected in the version 4.1 of the BC SOAP with the addition of the HTTPS support.
Frédéric Gardes added a comment - Wed, 10 Nov 2010 - 09:00:00 +0100
Under our environement, the bc-soap doesn't have this issue (it seems). The first invocation works, and the first time we read the wsdl (adding '?wsdl' at the end of the url) or vists the bc soap web page (under 8084 port by default), we can consult the wsdl page.
We're under RHEL5, not windows, under esb 3.1.1.
So, curious, and hard to reproduce : keep preciously your dev PC
Frédéric Gardes added a comment - Wed, 10 Nov 2010 - 09:00:00 +0100 Under our environement, the bc-soap doesn't have this issue (it seems). The first invocation works, and the first time we read the wsdl (adding '?wsdl' at the end of the url) or vists the bc soap web page (under 8084 port by default), we can consult the wsdl page.
We're under RHEL5, not windows, under esb 3.1.1.
So, curious, and hard to reproduce : keep preciously your dev PC
Backported in version 4.0.8