[Russ]

I have a web service up and running on JBoss 4.0.5….

I’ve taken the WSDL and used it to generate the Web Service client within MyEclipse. The classes are generated with no problem. I’ve also added the XFire Http Client Library too. In the main method for the client, I call the required method for my web service. However, the response from the service is null. When I go looking at the server logs I see:

[10:19:18,890] [DEBUG] [SOAPMessageDispatcher] [getDispatchDestination: {http://<URI for operation>}<method name>]
[10:19:18,890] [DEBUG] [SOAPBindingProvider] [unbindRequestMessage: {http://<URI for operation>}<method name>]
[10:19:18,890] [DEBUG] [EndpointInvocation] [setRequestParamValue: [name=userId,value=org.jboss.ws.soap.SOAPContentElement]]
[10:19:18,890] [DEBUG] [EndpointInvocation] [setRequestParamValue: [name=taskId,value=org.jboss.ws.soap.SOAPContentElement]]
[10:19:18,890] [DEBUG] [ServiceEndpointInvokerJSE] [invokeServiceEndpoint: <method name>]
[10:19:18,890] [DEBUG] [EndpointInvocation] [getRequestPayload]
[10:19:18,890] [DEBUG] [EndpointInvocation] [getRequestParamValue: userId]
[10:19:18,890] [DEBUG] [SOAPContentElement] [getObjectValue [xmlType={http://www.w3.org/2001/XMLSchema}string,javaType=class java.lang.String]]
[10:19:18,890] [DEBUG] [SimpleDeserializer] [deserialize: [xmlName=userId,xmlType={http://www.w3.org/2001/XMLSchema}string]]
[10:19:18,890] [DEBUG] [ServiceEndpoint] [END handleRequest: jboss.ws:context=<MyWebService Project>,endpoint=WebServiceBean]
[10:19:18,890] [DEBUG] [MessageContextAssociation] [popMessageContext: org.jboss.ws.soap.SOAPMessageContextImpl@1bf8785]

The web service never gets pass this point……it just dies there!

I have also tried other resources in MYECLIPSE. I have tried to use the Web Service Explorer:

This is the response displayed in the window from running the service.

The SOAP response failed schema validation. Please switch to the source view for the SOAP response in XML format.

This is the response XML

XML document must have a top level element. 
Error processing resource 'http://localhost:57734/wsexplorer/wsdl/soap_envelope...

I have tried also creating an AXIS client, but it fails too…..

Can someone shed some light on this client issue. Any suggestions or recommendations at this point would be warmly welcome…….I’ve lost all my hair from this problem already, so it’s time the scream for CPR!!!!

Russ

[tomeksz]

Try to use tcpmon ( https://tcpmon.dev.java.net/ ) and see how your message looks like.

[erjablow]

I’m having the same problem with Tomcat 5.5. What do I point TCPMON at?

[Riyad Kalla]

If the problem is occuring on Tomcat and JBoss, as well as XFire and AXIS… my guess would be that the web service is wrong in some way… using TCPMON is probably a great suggestion to see what is being passed back and forth and why it’s failing.

[Russ]

Thanks everyone…………..Great Suggestion!!!!!!! I couldn’t get The tcp monitor in MyEclipse to work, but the referenced link definately helped.

Now I am totally confused! The only thing I did was change the port number to 8181 on the client side and had tcpmon redirect it back to port 8080 on JBoss. Everything looks good (Status code of 200) but NO XML document……mmmmm. I should be getting back and XML document……….

My request…. looks good:

POST /<projectName>/WebServiceBean HTTP/1.1
SOAPAction: ""
Content-Type: text/xml; charset=UTF-8
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; XFire Client +http://xfire.codehaus.org)
Host: rray-wxp:8181
Expect: 100-continue
Content-Length: 348

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soap:Body><getTaskDetails xmlns="http://workflow.company.com/"><userId xmlns="">blah blah</userId><taskId xmlns="">198412345</taskId></getTaskDetails></soap:Body></soap:Envelope>

My response now from Tomcat is:

HTTP/1.1 100 Continue

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)/Tomcat-5.5
Set-Cookie: JSESSIONID=E2CA4765EB7E4BF68A0A390E9DB57E64; Path=/
Transfer-Encoding: chunked
Date: Tue, 13 Mar 2007 18:46:26 GMT

0

When I take the WSDL document and validated it through XMLSpy, everything is good………no errors.

What I can see is the server thinks it has fulfilled the request, but the server never really move the request over to the application server so it could hit the database………..

Any suggestions?

Thank for you help……..I’ve made alot progess with one post…….

[Russ]

Well after upgrading to MyEclipse5.5M1 I picked up X-Fire 1.2.4. This provided me with the MyEclipse ability to validate the WSDL with the BP-I. This added feature identified several issues in the WSDL that was being overlooked by a JBoss generated WSDL………

As always you guys never seem to amaze me on how forward thinking you really are……….definately a welcomed addition to the web service part of your tool.

You might want to look at this one area. The validation overlooked this in the WSDL, but X-Fire caught it when I tried to view the WSDL in my browser: within messages the “part” element’s name MUST be unique! JBOSS was creating the same name “result” in the WSDL.

[Riyad Kalla]

As always you guys never seem to amaze me on how forward thinking you really are……….definately a welcomed addition to the web service part of your tool.

Thank you Russ, I’m going to pass that comment along to the WS team, I’m sure it will give them a great pick-me-up today.

You might want to look at this one area. The validation overlooked this in the WSDL, but X-Fire caught it when I tried to view the WSDL in my browser: within messages the “part” element’s name MUST be unique! JBOSS was creating the same name “result” in the WSDL.

I will make a note for us to look into it, thanks for the heads up Russ.

[Author]

Posts