To help you we need a bit more information. There is on the otherhand also another option for you to set your URL name:
The way this works is, your URL will become 'http:/n000129:8080/yourJarName/EchoService?WSDL'. Did you by the way check the name of your jar which is deployed? Could it be that its 'csv-sa.jar'?
The problem is with how it is creating the URL from the deployment name. The esb is deployed as an exploded jar with name csv-sample.esb. It appears JBoss is truncating the directory name. I have attached the entire deployment.
csv-sample.esb.zip 7.9 K
I have tested the following ajustment:
<http-gateway name="HTTP-PROXY-GATEWAY" urlPattern="/mib-ellipse/EchoService/*"
which results into
- Endpoint: http://127.0.0.1:8080/cvs-sample/http/mib-ellipse/EchoService
- Contract: http://127.0.0.1:8080/cvs-sample/http/mib-ellipse/EchoService?wsdl
when you lookup your service from the http://127.0.0.1:8080/contract/ page.
I am using JBossEsb 4.9 btw.
I tried you suggestion with no success. I am using JBossESB 4.10 running on JBoss 5.1.0 with the CXF webservice stack. It is still truncating the deployment name in both the contract, the generated servlet for the http gateway and in the WSDL that is returned.
<http-gateway name="HTTP-PROXY-GATEWAY" urlPattern="/mib-ellipse/EchoService/*"/>
Found the problem. HttpGatewayDeploymentFactory is truncating the name because it is trying to remove .war from the end of the deployment. Since the esb is not deployed as a war, it causes the problem.
Found that it was previously reported as