This week's giveaway is in the Testing forum. We're giving away four copies of TDD for a Shopping Website LiveProject and have Steven Solomon on-line! See this thread for details.
Mmm, I used to use Apache CXF as JAX-WS framework for exposing web services. For client, I think that using wsimport to generate client-side artifacts should be enough.
I have red alot that says you can not access SOAP ws throw web browser request.
but surprisingly one of our projects can be accessed throw browser using http get request and returns a result as xml.
No, an URL entered into the browser (like for REST) is not sufficient, because the SOAP request is transported in the HTTP body - and only POST requests have a body, not GET requests. And GET is what the browser address bar sends.
If you want to do use SOAP from within a browser, you need to use JavaScript. That's one of the reasons REST is so popular in web apps.
but that what i am facing.
cxf-beans.xml file contains jax-ws's but no one is jax-rs.
and the source does not contain any annotation for jax-rs & no java script exist just beans.
after all of that is it accessible throw browser using http get requst
I'm sure you'll find JavaScript SOAP libraries if you search for them. They're probably not for the faint of heart, though. And again, GET is not an option for interacting with a SOAP WS. If GET is so important to you, why don't you rewrite the WS to have a REST interface as well?
I searched for "envelop" and found that cxf-2.5.0 has cxf-utils.js Java script file that contain alot of functions.
maybe these functions that do the work for get requets, but how it is used with the project.
it is just added into the lib folder.
Thanks for you all we solved the problem by using the cxf version 2.5 jar file, then we could call the soap web service from the url like it was Restful webservice.
thanks for your help.