I tried it with nightly build , I still get the same problem . Please let me
kniow if I need to run the wsdl2java again (did not do that )
Also to give u some more context
for axis 1 (though i was not involved) there was some code added to update
the namespace mapping in the SOAP envelope SOAPEnvelope responseEnvelope
= msgContext.getResponseMessage().getSOAPEnvelope();
// Update Name Space Mappings
NSStack nss = new NSStack();
nss.add("http://ei.com/schemas/entities/v3_1";<http://ei.com/schemas/entities/v3_1>,
"ent");
nss.add("http://ei.com/schemas/envelope/v3_0";<http://ei.com/schemas/envelope/v3_0>,
"tns");
....
responseEnvelope.setNSMappings(nss.cloneFrame());
As per my understanding this causes the axis 1 to send desired response . Is
there something which can be done with Axis 2.
Also if you note below in Axis2 response its using default namespaces we
would want the response to be same as axis1 , is there something similar in
axis 2 specificaly with regards to org.apache.axiom.soap.SOAPEnvelope?
Thanks
Gaurav
On 1/10/08, Gaurav Lall <[EMAIL PROTECTED]> wrote:
>
> Hi Amila
>
> Thanks will try with nightly build and let you know. Just want to check
> with you not sure how the nightly works should i be taking the build
> which is out there with modified date 10-Jan-2008 11:50 (
> http://people.apache.org/dist/axis2/nightly/) or do i need to wait for the
> build to happen
>
> Thanks
> Gaurav
>
>
> Amila Suriarachchi wrote:
>
> can you please try with a nighly build. Now axis2 directly use the
> xmlbeans serialization.
>
> thanks,
> Amila.
>
> On Jan 9, 2008 1:16 PM, Gaurav Lall < [EMAIL PROTECTED]> wrote:
>
> > Hi all ,
> >
> > We are doing migration to axis2 from axis1, we are using xmlnbeans as
> > data binding. mechanism.I am using axis 2 version 1.3
> >
> > We are observing difference in the responses
> >
> > 1. there is no xsi:type coming out for the response
> > 2. Also the namespaces are coming for each element in axis 2
> > response ? I would idealy like to use the prefixes to reduce the size of
> > the
> > payload
> > 3. Is there a configuration parameter which controls the emission
> > of xsi:type
> >
> > Any direction or pointers would be of great help ?
> >
> > -------------------AXIS 1
> > <off:productCategory>
> > <off:controlType>multiSelect</off:controlType>
> > <off:categoryType xsi:type="*xs:string*">
> > alaCarteResidential.alaCarteResidential</off:categoryType >
> > <off:categoryName>ODUSelection.ODUSelection</off:categoryName>
> > <ent:description xsi:type="*xs:string*">ODU Selection</
> > ent:description>
> > ------------Axis2
> > <productCategory xmlns=
> > "http://ei.com/schemas/wsdl/orderServices/v3_0/offer";<http://ei.com/schemas/wsdl/orderServices/v3_0/offer>
> > >
> > <controlType xmlns=
> > "http://ei.com/schemas/wsdl/orderServices/v3_0/offer";<http://ei.com/schemas/wsdl/orderServices/v3_0/offer>>multiSelect</controlType>
> >
> > <categoryType xmlns=
> > "http://ei.com/schemas/wsdl/orderServices/v3_0/offer";<http://ei.com/schemas/wsdl/orderServices/v3_0/offer>
> > >alaCarteResidential.alaCarteResidential</categoryType>
> > <categoryName xmlns=
> > "http://ei.com/schemas/wsdl/orderServices/v3_0/offer";<http://ei.com/schemas/wsdl/orderServices/v3_0/offer>
> > >ODUSelection.ODUSelection<l</categoryName>
> > <description
> > xmlns="http://ei.com/schemas/entities/v3_1";<http://ei.com/schemas/entities/v3_1>>A
> > La Carte Programming</description>
> >
> > Thanks for the help
> > Gaurav
> >
> >
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>
>
>
