Re: Document literal style - Send XML as string
"Something" is generated according to the operation name defined in your WSDL. With this I'm assuming that you are using the WSDL2Java tool or eclipse plug in. I still don't understand completely your problem. Is the SOAPUI able to send a successful message to the WS? What are you receiving back? I'll do a test later but what is curious to me is the fact that in your SOAP message the XML string parameter is not been escaped as < What code are you using to call your stub? -Pablo Melchi http://pablo-melchi.blogspot.com http://www.linkedin.com/pub/8/747/354 Mohan Radhakrishnan wrote: Hi, The WSDL is copied at the end of this mail. According to soap UI and the stub bindings what I am sending seems to be right. What I am sending is http://test.com";>
Re: Document literal style - Send XML as string
If I'm assuming the right thing. Your requirement is about sending a XML as an String through a Web Service. So what you are doing is something like this: Some XML with scaped characters The CDATA tag is helping to scape your XML so the parsers don't mix it with your SOAP evelope. The namespace should be already working fine since your stub was created based on the WSDL but if you still want to change it you can take a look to this: http://wso2.org/library/2060 Now my question would be... are you receiving any error? -Pablo Melchi pablo-melchi.blogspot.com Mohan Radhakrishnan wrote: What is the difference ? My WSDL requires me to pass a string parameter. I generated XMLBeans bindings and Axis2 stubs. There is a setter method generated and I set the XML that I want to pass. What is the rule in this case ? Should I set it as a child or let it pass the CDATA ? My second questions is about the targetnamespaceprefix that is automatically generated ? I think it is. Can I set my own prefix ? Thanks, Mohan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Document literal style - Send XML as string
I think that the problem is that your are sending a string inside a soap message and the soap message is created in the doc/lit style. Probably you want to use a binding framework to create that xml or check how to include it as a child of your payload -Pablo Melchi pablo-melchi.blogspot.com On Jun 1, 2008, at 9:30 AM, Mohan Radhakrishnan <[EMAIL PROTECTED] > wrote: Hi, I am using the doc/lit style to send a xs:string type. Now if I post an entire XML then it gets wrapped in CDATA. I am using Axis 2 XMLBeans bindings. I have these questions. 1. Does this style of sending XML as string require CDATA ? 2. A new namespace is added like this in the SOAP message when invoking the operation ? I am not specifying this 'newnamespace' anywhere. What is the rule for generating this 'newnamespace' ? I will post the WSDL and actual SOAP message if this info. is not sufficient. Thanks, Mohan -- View this message in context: http://www.nabble.com/Document-literal-style---Send-XML-as-string-tp17586208p17586208.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deserialization problems
Hi everybody. I have included some more details of the problem First... this is a rpc/encoded service so I'm using Axis (1) The problem is that I have this SOAP message (I've attached both messages): The only difference in the messages is the position of the element "" When axis tries to get the first element and start the deserialization it gets the first element in the first position (NS2:Par1) and solve all the references fine. But when it reach the end it finds the element "" and it cannot deserialize it (and it should not because it would create an infinite loop). I think that the obvious solution would be to fix the (get first element from axis) Now if the element "" is at the begging (like in the good.xml) axis can deserialize the whole message with no problem So I have a couple of questions: First: Is this XML well formed in both cases? I mean the position of the elements really matters? Second: What would be better try to implement support in axis2 for rpc/encoded or fix axis(1) to support this message? Thank you! -Pablo Melchi http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";> http://schemas.xmlsoap.org/soap/envelope/";> http://namespace1"; xmlns:NS2="http://namespace2";> 0 A Some text 1 B Some text 2 http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";> http://schemas.xmlsoap.org/soap/envelope/";> http://namespace1"; xmlns:NS2="http://namespace2";> 0 A Some text 1 B Some text 2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis]Deserialization problem
Hi everybody. I have a problem with a deserialization for axis (axis1) The problem is with a SOAP Message rpc/encoded, I have already gone through the code and it looks like there is a problem between the position of the tags in the message and the way that Axis is looking for the first element within the message. I know that Axis2 is not supporting rpc/encoded but by using ADB, I have been able to send a message to the application (I haven't just figured out how I'll handle the biding in the response yet) My question is... is worthy fix axis and submit the patch or is better to build something for axis2 to handle that?
