Re: AXIS2 1.4: Client problems when changing form plain XML to SOAP-style messages: Disallowed element found in envelope:Envelope..

2008-05-28 Thread Sanka Samaranayake
Hi Robert, If I understand your problem correctly, all you need is to retrieve the MobilePointList element via a SOAP from your back-end service. You can follow Axis2 user guide sample when creating you own service. Just like in sayHello(..) method, all you have to return is MobilePolicyList

Re: AXIS2 1.4: Client problems when changing form plain XML to SOAP-style messages: Disallowed element found in envelope:Envelope..

2008-05-19 Thread Samisa Abeysinghe
Robert Ribnitz wrote: Hello Sanjiva, my basic porblem is the general lack of documentation; in the examples, there is a "SOAP with Attachments" example, but there is no example on how to use a plain SOAP message. What about the echo sample? If you already have the SOAP envelope, all you hav

Re: AXIS2 1.4: Client problems when changing form plain XML to SOAP-style messages: Disallowed element found in envelope:Envelope..

2008-05-19 Thread Robert Ribnitz
Hello Sanjiva, my basic porblem is the general lack of documentation; in the examples, there is a "SOAP with Attachments" example, but there is no example on how to use a plain SOAP message. I do have my list of Points (elements from the DB), which i need to return My interpretation of the d

Re: AXIS2 1.4: Client problems when changing form plain XML to SOAP-style messages: Disallowed element found in envelope:Envelope..

2008-05-18 Thread Sanjiva Weerawarana
The problem is that your service code is returning an entire SOAP envelope. Is that what you wanted to do? Or did you mean to return just a body? (It seems that you're not using outContext at all .. ? However, the bug is fishy .. I don't think the SOAP spec disallows sending an entire SOAP en

AXIS2 1.4: Client problems when changing form plain XML to SOAP-style messages: Disallowed element found in envelope:Envelope..

2008-05-16 Thread Robert Ribnitz
Hello, I have also posted the following to the user list, with no response. As I think this might be an error in Axis2, I am forwarding this to the dev list. I have recently started to use AXIS2 (1.4) (on J2EE 5/with the Sun Java Application Server 9.1, using Java 6); the idea is to be able t