I find that the format of my wsdl has some difference with the wsdl which is generated by JBossESB using spring.I wonder if the SoapAction in JBossESB doesn't support the wsdl coming from axis2 ?Or I need to do some configurations?

I'm wondering if it is the problem with the version of soapui-client. In JBossESB the version of soapui-client is v1.7.1, and the Web Service testing tool SoapUI is using the v2.0.2. But I don't have the problem in the tool SoapUI.

I had the same problem today: my wsdl was on port 8081 but when Jboss was sending soap messages, the endpoint port was 80 and the message connection refused follows.

I didn't really understood what I did but I solved my problem.I suppose that it's not a Jboss problem.I did my test with Axis2 and I saw that the port was wrong in the wsdl. By reading again the previous post we can see in the wsdl file