I was wondering if we can write our own code for a web service client, which can call to any web service (same as we do in SOAP-ui).
I was told to develop a soap-ui type tool which can be embedded in any of our java based project which need a webservice client call. So that we do not have to write separate client code for every wsdl link (or every webservice), or we can say a generic java web service client??
Does any body have any idea on this or can guide me to some examples/path?
Seems like a huge task. What's the big deal about writing client code for a WS call? All the common SOAP stacks have tools that generate client-side code for you. Any alterations you have to make should be negligible.
Ping & DNS - updated with new look and Ping home screen widget
Ulf Dittmer is correct, TCPmon won't be able to originate request, I want something which can originate xml request and get back the xml response from the WS.
Actually we want to have a module, which can be integrated into other applications (without code modification, just specifying the wsdl link/security credentials) in order to call external web services, we just have to provide the required soap request xml and receive the xml response. Same as we do in soapui.
I am also thinking of to start with soapui... but before that I would like to discuss your valuable response, from you guys, with my team to reconsider their decision of moving ahead on this task...
Author and all-around good cowpoke
Joined: Mar 22, 2000
If you have examples of what the SOAP requests look like and:
1. No security/authentication/etc tricks are involved.
2. Generating a request simply requires inserting some values into the fixed SOAP request format so you can create a "template".
Plugging values into a template and sending the resulting XML request to the SOAP service is really really simple with the standard Java library tools.
IF on the other hand, you need to create WS-* security then you are stuck with using one of the toolkits to generate your client code.