axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ramkig <ramk...@gmail.com>
Subject Re: Axis2 1.4.1 namespace error in reponse
Date Thu, 22 Sep 2011 20:16:34 GMT

Amila / Axis Group,

I did not get any response on this. Can you please check when you get a
chance.

Here I am trying to explain the problem again. Problem is that axis2 server
on our side ( 1.4 or 1.6) sends response with same name space for all
elements even though they belong to different name space.
Our clients are not able to decode the response. For work around, I updated
the axis generated wsdl  to match with the response axis generating i.e all
elements with single name space. With this WSDL Client is able to
deserialize the response successfully. But obviously we want to fix the
issue on server side. Here I am attaching both wsdls. WebService-URL.wsdl is
the one generated by Axis. WebService-URL-SN.wsdl is the one I updated.
Please look into this issue asap.

Here I am also giving the axis generated response again.

<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/ ">
<soapenv:Body>
<ns:checkCustomerResponse xmlns:ns="http://webservice.custapi.alacriti.com">
 <ns:return type="com.alacriti.custapi.vo.response.CheckCustomerResponse">
 <ns:header type="com.alacriti.yaf.msg.MessageHeader">
 <ns:msgId>13102</ns:msgId>
 <ns:msgName xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:nil="true" />
  <ns:msgType>16</ns:msgType>
  <ns:msgVersion>1.0</ns:msgVersion>
  </ns:header>
 <ns:msgData type="com.alacriti.custapi.vo.APIMessageData">
  <ns:channelType>7</ns:channelType>
  <ns:extIssuedCustId>910618</ns:extIssuedCustId>
  <ns:partnerKey>111113872</ns:partnerKey>
  <ns:productId>2</ns:productId>
  <ns:responseCodes type="com.alacriti.yaf.msg.MessageResponseCode">
  <ns:responseCode>301</ns:responseCode>
  <ns:responseText xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:nil="true" />
  <ns:responseType>1</ns:responseType>
  <ns:responseTypeId>0</ns:responseTypeId>
  </ns:responseCodes>
  <ns:responseType>1</ns:responseType>
   <ns:sessionId  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:nil="true" />
  <ns:timestamp>09/12/2011 16:01:14:713 EDT</ns:timestamp>
 </ns:msgData>
 <ns:customer xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"
xsi:nil="true" />
<ns:customerAccounts xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:nil="true" />
 </ns:return>
 </ns:checkCustomerResponse>
 </soapenv:Body>
 </soapenv:Envelope>


- Rama








Amila Suriarachchi wrote:
> 
> Can you send us your POJO class and services.xml so that we can reproduce
> the error?
> 
> thanks,
> Amila.
> 
> On Sun, Sep 18, 2011 at 12:20 AM, ramkig <ramkibg@gmail.com> wrote:
> 
>>
>> I tried with axis2 1.6.0. Getting same response with invalid name space.
>> Only
>> difference is type attribute is not coming which does not matter. Please
>> advise.
>>
>>
>>
>> Amila Suriarachchi wrote:
>> >
>> > Can you please check with Axis2 1.6.0?
>> >
>> > thanks,
>> > Amila.
>> >
>> > On Sat, Sep 17, 2011 at 4:35 AM, ramkig <ramkibg@gmail.com> wrote:
>> >
>> >>
>> >> Axis2 1.4.1 service sends same name space for all elements even though
>> >> different elements belong to different name space. The type attribute
>> for
>> >> each element has Java package which is correct , but the name space is
>> >> incorrect and most of the clients other than axis ( like .Net or
>> >> NetBeans)
>> >> not able to decode the response and they see all response elements as
>> >> null.
>> >> This is very urgent for me. Any help on this is appreciated.
>> >>
>> >> If you observe in below response the header element and all other
>> >> elements
>> >> are coming with same name space of root element(ns). The header should
>> >> have
>> >> been with namespace "http://response.vo.custapi.alacriti.com/xsd" and
>> >> other
>> >> elements also with different name spaces. Attached the WSDL File.
>> >>
>> >> <?xml version='1.0' encoding='utf-8'?>
>> >> <soapenv:Envelope
>> >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
>> >> ">
>> >>  <soapenv:Body>
>> >>    <ns:checkCustomerResponse
>> >> xmlns:ns="http://webservice.custapi.alacriti.com">
>> >>      <ns:return
>> >> type="com.alacriti.custapi.vo.response.CheckCustomerResponse">
>> >>        <ns:header type="com.alacriti.yaf.msg.MessageHeader">
>> >>          <ns:msgId>13102</ns:msgId>
>> >>          <ns:msgName
>> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> >> xsi:nil="true" />
>> >>          <ns:msgType>16</ns:msgType>
>> >>          <ns:msgVersion>1.0</ns:msgVersion>
>> >>        </ns:header>
>> >>        <ns:msgData type="com.alacriti.custapi.vo.APIMessageData">
>> >>          <ns:channelType>7</ns:channelType>
>> >>          <ns:extIssuedCustId>910618</ns:extIssuedCustId>
>> >>          <ns:partnerKey>111113872</ns:partnerKey>
>> >>          <ns:productId>2</ns:productId>
>> >>          <ns:responseCodes
>> >> type="com.alacriti.yaf.msg.MessageResponseCode">
>> >>            <ns:responseCode>301</ns:responseCode>
>> >>            <ns:responseText
>> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"
>> />
>> >>            <ns:responseType>1</ns:responseType>
>> >>            <ns:responseTypeId>0</ns:responseTypeId>
>> >>          </ns:responseCodes>
>> >>          <ns:responseType>1</ns:responseType>
>> >>          <ns:sessionId
>> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"
>> />
>> >>          <ns:timestamp>09/12/2011 16:01:14:713 EDT</ns:timestamp>
>> >>        </ns:msgData>
>> >>        <ns:customer xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance"
>> >> xsi:nil="true" />
>> >>        <ns:customerAccounts
>> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"
>> />
>> >>      </ns:return>
>> >>    </ns:checkCustomerResponse>
>> >>  </soapenv:Body>
>> >> </soapenv:Envelope>
>> >>
>> >>
>> >>
>> >> http://old.nabble.com/file/p32483689/WebService1.wsdl WebService1.wsdl
>> >> --
>> >> View this message in context:
>> >>
>> http://old.nabble.com/Axis2-1.4.1-namespace-error-in-reponse-tp32483689p32483689.html
>> >> Sent from the Axis - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-user-help@axis.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Amila Suriarachchi
>> > WSO2 Inc.
>> > blog: http://amilachinthaka.blogspot.com/
>> >
>> >
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Axis2-1.4.1-namespace-error-in-reponse-tp32483689p32486265.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-user-help@axis.apache.org
>>
>>
> 
> 
> -- 
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
> 
> 

-- 
View this message in context: http://old.nabble.com/Axis2-1.4.1-namespace-error-in-reponse-tp32483689p32503836.html
Sent from the Axis - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org


Mime
View raw message