Geek Answers Handbook

SoapUI vs. Java Web Service Client

If the SOAP web service works well through the SoapUI (creating the right SOAP responses), when creating the web service client in Java using different APIs / frameworks, there are various problems when invoking this web service, is it safe to consider a stable web service and problems on the part of the consumer?

I am asking a general question here, I have already asked a detailed question, which is probably too long to read. I'm more interested in the concept than my actual implementation, so if you can answer my question without contacting my longer mail, please do it.

UPDATE : I realized that even if WSDL is compatible with WS-I and works correctly through SoapUI, this is still not enough to conclude that the web service is not broken. As @jtahlborn said, SoapUI is very tolerant of disrupted web services, and this can easily fool you into believing that your web service is working fine, which is what happened in my case.

I am creating a SOAP response in ESB and my problem was that I was using a namespace that was defined in WSDL but not in the schema. SoapUI received the answer and showed it to me (with the wrong namespace); this question could have been avoided if I had enabled the answer verification option .

It is also worth mentioning that in the Java web service client that I created to test my web service, the response could not be loaded into the output object (a NullPointerException error occurred when trying to access the output object), it was caused by a namespace problem, and it started working correctly after fixing the namespace.

+6
source share
3 answers

SoapUI is a fantastic product. one of the things that makes it a great product, however, is that it is very tolerant of poorly defined web services. in our product we are dealing with a large number of web services, and a frequent comment on the problem in our product is "it works great in SoapUI". we have learned that SoapUI will tolerate all kinds of broken web services. therefore, in general, working with SoapUI is not proof that your web service is well defined.

+10
source

There are WS-I testing tools to check your web service for compliance Web service support . If your service meets the basic WS-I profile, and SoapUI can name it, the problems are definitely customer dependent.

EDIT: well, or between both ...

SoapUI can check your wsdl for WS-I compliance, see http://www.soapui.org/SOAP-and-WSDL/working-with-wsdls.html .

+2
source

Most likely, the consumer (client) is not working ... If the client is generated using wsdl2java, this is a great chance to get errors in it ... and if you use some special functions that are valid (corresponding to w3c), then do not be surprised .. ... created clients sometimes do this ... even some of the libraries used to create Java classes or libraries for creating web services are full of errors ...

Many things are not supported by well-known and frequently used libraries ... (I do not want to give names, but wsdl4java is not perfect).

If you use security or something else ... higher chances of errors on the server and on the client side :)

maybe if you tell us what the problem is, we can help you ...

0
source

More articles:


All Articles