On Thu, Oct 1, 2009 at 1:51 PM, sri ram <[email protected]>wrote:
> Thanks to Paul and Andreas. > > The same request when modified to this format ,works fine > <SOAP-ENV:Envelope xmlns:ns="http://www.kiran.com"; xmlns:SOAP-ENV=" > http://schemas.xmlsoap.org/soap/envelope/";> > <SOAP-ENV:Body> > <executeSQLQuery xmlns="http://www.kiran.com";> > <sql xmlns="">select * from typedevice</sql> > </executeSQLQuery> > </SOAP-ENV:Body> > </SOAP-ENV:Envelope> > > I have elementFormDefault="unqualified" attributeFormDefault="unqualified" > in the schema .I will change these values and check if it works for me. > > One question :When is it recommended to have a > elementFormDefault="qualified" attributeFormDefault="qualified" ? > normally we use elementFormDefault="qualified" and attributeFormDefault="unqualified" thanks, Amila. > > Thanks, > Sriram > > > --- On *Thu, 1/10/09, Andreas Veithen <[email protected]>* wrote: > > > From: Andreas Veithen <[email protected]> > Subject: Re: > To: [email protected] > Date: Thursday, 1 October, 2009, 1:25 PM > > > The two requests are NOT the same. In the first request, the <sql> > element has a namespace, while in the second one it does not. It is > normal that Axis2 rejects one of them. Which of the two request is the > correct one depends on the WSDL/Schema, more specifically on the > setting for elementFormDefault. > > Andreas > > On Thu, Oct 1, 2009 at 08:29, Paul Fremantle > <[email protected]<http://mc/[email protected]>> > wrote: > > > > Sriram > > > > You don't need to have the ns prefix. As long as the XML is properly > formed, you can use either style. > > > > Paul > > > > On Thu, Oct 1, 2009 at 7:12 AM, sri ram > > <[email protected]<http://mc/[email protected]>> > wrote: > >> > >> Hi, > >> > >> As I see in Axis 2 doesn't support a format of SOAP messages which > doesn't have namespace prefix.As shown below the request doesn't work > ,however when substituted bya namespace prefix it does work well. > >> > >> <SOAP-ENV:Envelope encodingStyle=" > http://schemas.xmlsoap.org/soap/encoding/"; xmlns:SOAP-ENV=" > http://schemas.xmlsoap.org/soap/envelope/";> > >> > >> <SOAP-ENV:Body> > >> > >> <executeSQLQuery xmlns= > http://www.kiran.com/AXL/API/7.1> > >> > >> <sql>select * from > typeproduct</sql> > >> > >> </executeSQLQuery> > >> > >> </SOAP-ENV:Body> > >> > >> </SOAP-ENV:Envelope> > >> > >> (axis 2) expects the request message to have namespace prefix in the > request . > >> > >> > >> > >> <SOAP-ENV:Envelope encodingStyle=" > http://schemas.xmlsoap.org/soap/encoding/"; xmlns:SOAP-ENV=" > http://schemas.xmlsoap.org/soap/envelope/";> > >> > >> <SOAP-ENV:Body> > >> > >> <ns:executeSQLQuery xmlns:ns =" > http://www.kiran.com/AXL/API/8.0";> > >> > >> <sql>select * from > typeproduct</sql> > >> > >> </ns:executeSQLQuery> > >> > >> </SOAP-ENV:Body> > >> > >> </SOAP-ENV:Envelope> > >> > >> Is there a way to make the axis 2 framework to allow and process the > other format of request ie withoute the namespace prefix. > >> > >> > >> > >> Is this (namespace prefix ) a standard followed by all the SOAPEngines > and Parsers. > >> > >> Can some one throw some light on it. > >> > >> Please reply back soon. > >> > >> If this kind of question is already addressed can you guys please give > link to the corresponding mail. > >> > >> Thanks , > >> > >> Sriram > >> > >> ________________________________ > >> Connect more, do more and share more with Yahoo! India Mail. Learn more. > > > > > > -- > > Paul Fremantle > > Co-Founder and CTO, WSO2 > > Apache Synapse PMC Chair > > OASIS WS-RX TC Co-chair > > > > blog: http://pzf.fremantle.org > > [email protected] <http://mc/[email protected]> > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > ------------------------------ > Try the new Yahoo! India Homepage. Click > here<http://in.rd.yahoo.com/tagline_metro_1/*http://in.yahoo.com/trynew> > . > -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
