Hi Ajith and Davanum, I seeeeee.. ..and it seems that rolling XmlSchema forward to 1.03 doesn't help; neither can I roll back to XmlSchema-SNAPSHOT.jar as the axis2 code that invokes it seems to have changed to accommodate changes in 1.02.
So it seems possible that there is a change to XmlSchema that might explain the sudden rash of data binding problems. I think I have to roll back to 0.95 as my difficulties with 1.0 do not seem to have a solution that I can code myself. (Glad I have an excuse to stop :-) , my head hurts ) I'll add to jira 710 regarding the 'gen361' prefix (as it's all related) when the system is back up. Thanks for looking at the problem. Regards, Ken -----Original Message----- From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] Sent: 14 May 2006 01:53 To: [email protected]; [EMAIL PROTECTED] Subject: Re: [Axis2 1.0] MessageContext question Hmm... I see a possible bug of the XMLSchema library here. The schemas are kept as XMLschema objects inside the AxisService and what happens in the XMLBeans databinding is that the schema object is serialized and fed into the XMLBeans schema compiler. XMLSchema serilialization may have a problem and the mentioned namespace prefix may be generated by XMLSchema Ajith On 5/13/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Ken, > > Could u please log a JIRA bug and then upload your WSDL? > > thanks, > dims > > On 5/12/06, Ken Campbell <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Sorry to bang on about this but I tried removing the targetNamespace > > entirely from my wsdl and then re-ran WSDL2Java to see if the namespace > > declarations in the soap:body of the message could be removed. > > > > So now I am asking why WSDL2Java throws: > > Invalid QName value: Can't resolve prefix 'gen361' ? > > I don't have a 'gen361' prefix in my schema. > > > > Regards, > > Ken
