Note that the second request is not valid with respect to the schema defined in your WSDL, because meterref is in the urn:Alcatel_Lucent_OSP_BPEL namespace, but the schema uses elementFormDefault="unqualified".
Andreas On Wed, Feb 25, 2009 at 11:13, GKGT80 <[email protected]> wrote: > > Hello keith, > > Axis is generating SOAP Request in this form :- > > **************** > <soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> > <soapenv:Body> > <urn:portalreadmeter2 xmlns:urn="urn:Alcatel_Lucent_OSP_BPEL"> > <meterref>100010</meterref> > </urn:portalreadmeter2> > </soapenv:Body> > </soapenv:Envelope> > **************** > > But I need in this form (because some issue in our SOAP server):- > ************************ > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> > <soapenv:Body> > <portalreadmeter2 xmlns="urn:Alcatel_Lucent_OSP_BPEL"> > <meterref>100010</meterref> > </portalreadmeter2> > </soapenv:Body> > </soapenv:Envelope> > ***************************** > > Please find the attached WSDL file. > http://www.nabble.com/file/p22199926/portalreadmeter2.wsdl > portalreadmeter2.wsdl > KR, > Gaurav Kumar > > > > > Keithgchapman wrote: >> >> Hi Gaurav, >> >> Your Response is not valid XML, That is the reason for this error. >> >> xmlns:urn:="urn:Alcatel_Lucent_OSP_BPEL"> >> >> should have been >> >> xmlns:urn="urn:Alcatel_Lucent_OSP_BPEL"> >> >> This looks to be a bug in the server (OSP 2.4 BPEL engine) >> >> Thanks, >> Keith. >> >> On Mon, Feb 23, 2009 at 10:11 PM, GKGT80 <[email protected]> wrote: >> >>> >>> Hello keith , >>> >>> I am also facing problem in SOAP response. >>> >>> SOAP Response I am getting (TCP Monitor trace):- >>> ***************************************** >>> HTTP/1.1 200 OK >>> Server: OSP 2.4 BPEL engine >>> Content-Type: text/xml; charset=ISO-8859-1 >>> Content-Length: 1965 >>> Connection: close >>> >>> <?xml version="1.0" encoding="UTF-8"?> >>> <SOAP-ENV:Envelope >>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; >>> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"; >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >>> xmlns:urn:="urn:Alcatel_Lucent_OSP_BPEL"> >>> <SOAP-ENV:Body> >>> ... >>> </SOAP-ENV:Body> >>> </SOAP-ENV:Envelope> >>> >>> ***************************************** >>> >>> In our SOAP response Envelope 1 semantics error in namespace >>> declaration:- >>> xmlns:urn:="urn:Alcatel_Lucent_OSP_BPEL" >>> Because of this my SOAP client give exception while receiving the SOAP >>> response : >>> ********************* >>> org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxUnexpectedCharException: >>> Unexpected character ':' (code 58) expected '=' >>> at [row,col {unknown-source}]: [1,284] >>> ******************** >>> >>> Is any work around of this problem ? like getting the raw response etc. >>> >>> KR, >>> Gaurav Kumar >>> >>> >>> >>> Keithgchapman wrote: >>> > >>> > You could have elementFormDefault="unqualified" in the schema of the >>> WSDL. >>> > This instructs the user not to care about the namespaces. >>> > >>> > Thanks, >>> > Keith. >>> > >>> > On Fri, Feb 20, 2009 at 7:39 PM, durbans <[email protected]> wrote: >>> > >>> >> >>> >> I am new to Axis2; i am using ADB. >>> >> I'd like to skip namespace prefixes in XML response. For example if >>> the >>> >> client receive >>> >> >>> >> <name xsi:type="xsd:string">John</name> >>> >> >>> >> or receive >>> >> >>> >> <s:name xsi:type="xsd:string">John</s:name> >>> >> >>> >> it must work in both case. At the moment only the second case work, >>> >> because >>> >> in xsd file the namespace is defined. >>> >> >>> >> Are there any way to skip ALWAYS the namespaces ? >>> >> -- >>> >> View this message in context: >>> >> >>> http://www.nabble.com/Axis2%3A-how-to-skip-namespace-prefixes---tp22120392p22120392.html >>> >> Sent from the Axis - User mailing list archive at Nabble.com. >>> >> >>> >> >>> > >>> > >>> > -- >>> > Keith Chapman >>> > Senior Software Engineer >>> > WSO2 Inc. >>> > Oxygenating the Web Service Platform. >>> > http://wso2.org/ >>> > >>> > blog: http://www.keith-chapman.org >>> > >>> > >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Axis2%3A-how-to-skip-namespace-prefixes---tp22120392p22165119.html >>> Sent from the Axis - User mailing list archive at Nabble.com. >>> >>> >> >> >> -- >> Keith Chapman >> Senior Software Engineer >> WSO2 Inc. >> Oxygenating the Web Service Platform. >> http://wso2.org/ >> >> blog: http://www.keith-chapman.org >> >> > > -- > View this message in context: > http://www.nabble.com/Axis2%3A-how-to-skip-namespace-prefixes---tp22120392p22199926.html > Sent from the Axis - User mailing list archive at Nabble.com. > >
