You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by gargankur007 <ga...@gmail.com> on 2015/05/20 16:06:08 UTC
making a web service work without targetnamespace
Hi
I have exposed a soap service using CXF component.
The issue is the Soap Body is like
<soapenv:Body>
<RmhpHop3PaymentEffRequest>
<ClientId>?</ClientId>
<InputParameters>?</InputParameters>
<ReceiverID>?</ReceiverID>
<SecurityKey>?</SecurityKey>
</RmhpHop3PaymentEffRequest>
</soapenv:Body>
Now if my Webservice is like
@WebService(targetNamespace = "")
and it is declared in package
"com.hcentive.wig.wem.soap.provider.rmhp.payment.effectuation.services.effService"
On hitting through soap client it gives follwoing error
<soap:Fault>
<faultcode>soap:Client</faultcode>
<faultstring>Unexpected element RmhpHop3PaymentEffRequest found.
Expected
{http://effService.services.effectuation.payment.rmhp.provider.soap.wem.wig.hcentive.com/}RmhpHop3PaymentEffRequest.</faultstring>
</soap:Fault>
Is there any way I can eliminate the verification of targetnamespace?
--
View this message in context: http://camel.465427.n5.nabble.com/making-a-web-service-work-without-targetnamespace-tp5767325.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: making a web service work without targetnamespace
Posted by gargankur007 <ga...@gmail.com>.
Hi
I am using BareStyle Document WSDL and still it is expecting a namespace
--
View this message in context: http://camel.465427.n5.nabble.com/making-a-web-service-work-without-targetnamespace-tp5767325p5767866.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: making a web service work without targetnamespace
Posted by gargankur007 <ga...@gmail.com>.
My Sample request is
"<?xml version="1.0" encoding="UTF-8"?> <XpgIntegratedPaymentRequest
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"> <ClientId>RMHP</ClientId>
<InputParameters>PHBheW1lbnRzPjxwYXltZW50PjxwYXltZW50RGF0ZT4yMDE0LTA3LTAyPC9wYXltZW50RGF0ZT48c291cmNlUmVmZXJlbmNlSWQ+MjA5ODc2NTY0ODc4NTEyNDU0ODc4Nzk8L3NvdXJjZVJlZmVyZW5jZUlkPjxzb3VyY2VSZWZlcmVuY2VBbGlhcz4xNTQ4Nzk2NTg3PC9zb3VyY2VSZWZlcmVuY2VBbGlhcz48cGF5bWVudE1vZGU+QUNIPC9wYXltZW50TW9kZT48cGF5bWVudFN0YXR1cz5QQVlNRU5UX1JFUVVFU1RfU1VDQ0VTU0ZVTEw8L3BheW1lbnRTdGF0dXM+PHNvdXJjZT48c291cmNlTmFtZT5STUhQPC9zb3VyY2VOYW1lPjwvc291cmNlPjxyZWN1cnJpbmdQYXltZW50Pjxtb2RlPkJNPC9tb2RlPjwvcmVjdXJyaW5nUGF5bWVudD48bWFya2V0VHlwZT5JTkRJVklEVUFMPC9tYXJrZXRUeXBlPjxwb2xpY3k+PHBsYW4+PHNvdXJjZVBsYW5JZD48L3NvdXJjZVBsYW5JZD48L3BsYW4+PHByZW1pdW1BbW91bnQ+ODc5PC9wcmVtaXVtQW1vdW50Pjx0b3RhbEFtb3VudD41MTY8L3RvdGFsQW1vdW50PjxlZmZlY3RpdmVDb3ZlcmFnZURhdGU+PC9lZmZlY3RpdmVDb3ZlcmFnZURhdGU+PC9wb2xpY3k+PGFtb3VudFBhaWQ+NTE2PC9hbW91bnRQYWlkPjx1c2VyPjxzb3VyY2VVc2VySWQ+MTU0ODc5NjU4Nzwvc291cmNlVXNlcklkPjxmaXJzdE5hbWU+TkE8L2ZpcnN0TmFtZT48bGFzdE5hbWU+TkE8L2xhc3ROYW1lPjxhZGRyZXNzPjxzdHJlZXQxPk5BPC9zdHJlZXQxPjxjaXR5Pk5BPC9jaXR5PjxzdGF0ZT5OQTwvc3RhdGU+PHppcGNvZGU+TkE8L3ppcGNvZGU+PGNvdW50cnk+TkE8L2NvdW50cnk+PC9hZGRyZXNzPjxlbWFpbElkPmJpbGxpbmdAcm1ocC5vcmc8L2VtYWlsSWQ+PC91c2VyPjwvcGF5bWVudD48L3BheW1lbnRzPg==</InputParameters>
</XpgIntegratedPaymentRequest> "
But when I am using camel cxf it is expecting a different namespace which is
derived by the targetnamespace attribute of @WebService annotation.
--
View this message in context: http://camel.465427.n5.nabble.com/making-a-web-service-work-without-targetnamespace-tp5767325p5767852.html
Sent from the Camel - Users mailing list archive at Nabble.com.