Kartheek, hopefully someone else can answer your questions positively,
but keep in mind that SOAP *is* fully XML, it's just that your web
service provider would need to trim out the outer SOAP envelope to just
get the SOAP body contents (the "payload" in JAX-WS terminology) which
will contain the XML you care about. (Your provider may need to parse
the XML anyway if you're using XML over HTTP, so it's not much a bigger
deal to use SOAP instead.) There's libraries like SAAJ that make that
parsing easy.
You'll probably want to use the Provider interface if you go this route
(we have a sample in the CXF distribution:
http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/jaxws_dispatch_provider/)
to more easily get at the inner XML message; also look at links #2 and
#11 here for an introduction to SOAP:
http://www.jroller.com/gmazza/entry/blog_article_index. Alternatively,
if you can create a baby WSDL taking a string input, that string will be
your XML and you're as good to go with link #2 as if you're using XML
over HTTP.
Glen
On 06/26/2012 08:32 AM, kdesin wrote:
Thanks for giving all the inputs and I was to able to get the response from
the remote service.
However I am yet to harness features supported in CXF.
My actual requirement is to talk with a service that takes only XML over
HTTPS.
a) Does CXF supports a front end programming model to create a client
service that communicates using XML over https. No fancy SOAP / ReST.
b) How do I use data binding, protocol binding and conduit to control in
above scenario as the apache docs speak mostly about WSDL/REST type services
for these features.
(Adding the certificate to the cacerts keystore solved the certificate
problem)
Saludos
Kartheek
-----
Saludos
Kartheek
--
View this message in context:
http://cxf.547215.n5.nabble.com/XML-HTTP-without-SOAP-in-CXF-tp5710174p5710311.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Glen Mazza
Talend Community Coders
coders.talend.com
blog: www.jroller.com/gmazza
