Werner, I did not intend to cause offence or be rude, I didn't expect the issue to be fixed over the weekend, I was just simply wondering if you had any initial thoughts on what the problem may be.
Sorry for offence caused, Alex. -----Original Message----- From: Werner Guttmann [mailto:[EMAIL PROTECTED] Sent: 14 July 2008 09:38 To: [email protected] Subject: Re: [castor-user] xmlns="" problem Alex, no, not really. Is your expectation really that you'll see this fixed over the weekend ? II guess you are aware that this is an open source project by definition, and that - as such - sources are available. If you are telling us that you want commercial grade support, please have a look at http://castor.org/professional-services.html Regards Werner PS No, I am not personally upset. But somehow I do consider such questions slightly rude. Alex Herriott wrote: > Hi, > > I have logged a defect for this issue, the number is 2468. > > Just wondering has anyone had a chance to look at it? > > Thanks, > Alex. > > -----Original Message----- > From: Alex Herriott [mailto:[EMAIL PROTECTED] > Sent: 09 July 2008 13:06 > To: [email protected] > Subject: RE: [castor-user] xmlns="" problem > > Hi Werner, > > I just logged a defect for this problem, the number is 2468 > > Thanks, > Alex. > > -----Original Message----- > From: Werner Guttmann [mailto:[EMAIL PROTECTED] > Sent: 08 July 2008 20:37 > To: [email protected] > Subject: Re: [castor-user] xmlns="" problem > > Sorry, but I asked Alex (and as such you as well) to create a Jira > issue. Can you please do so (as well) ? > > Werner > > Paco Sanchez wrote: >> Hi all, >> I have the same problem. If I append xmlns="" to every xml element > then the >> whole object is unmarshaled correctly. If I don't, the unmarshaller > tell me >> that "The field '_peticion' (whose xml name is 'peticion') is a > required >> field of class 'MensajeSalida". I've attached the xsd file. >> >> http://www.nabble.com/file/p18343825/ws.xsd ws.xsd >> >> Thanks in advance, >> >> >> Werner Guttmann wrote: >>> Hi Alex, >>> >>> can you please create a new Jira issue and attach a simple (sic!) XML >>> schema so that I can generate the sources myself, and a test case > that >>> allows me to reproduce the problem you are facing within your client. >>> >>> Thanks >>> Werner >>> >>> Alex Herriott wrote: >>>> Hi, >>>> >>>> >>>> >>>> I am having a problem marshalling a message between castor 0.9.5.4 > and >>>> 1.2.1. >>>> >>>> >>>> >>>> On the server I have castor 0.9.5.4, the message source has been >>>> generated with this version and also this version is being used to >>>> marshal the object so it can be sent to the client >>>> >>>> >>>> >>>> On the client there is castor 1.2.1. Here version 1.2.1 is being > used to >>>> generate the message source for the client and unmarshal the > incoming >>>> message. >>>> >>>> >>>> >>>> The same xsd is being used for source generation >>>> >>>> >>>> >>>> the message that is generated from the server (0.9.5.4) is the > following >>>> >>>> >>>> <Rq xmlns="http://www.aaa.com";>< AbcDet>1</AbcDet></Rq> >>>> >>>> >>>> >>>> When this is unmarshaled on the client (v 1.2.1) the 'AbcDet' is > missing >>>> from the object. >>>> >>>> >>>> >>>> If I add and empty namespace declaration to the AbcDet on the > incoming >>>> message e.g. >>>> >>>> >>>> >>>> <Rq xmlns="http://www.aaa.com";>< AbcDet xmlns="">1</AbcDet></Rq> >>>> >>>> >>>> >>>> Then the whole object is unmarshaled correctly. >>>> >>>> >>>> >>>> I have looked the following suggestion >>>> http://osdir.com/ml/java.castor.devel/2003-03/msg00168.html and > added >>>> elementFormDefault="qualified" >>>> >>>> to the xsd however this did not solve the problem >>>> >>>> >>>> >>>> Any suggestions why is castor 1.2.1 not unmarshaling object > correctly >>>> when there is no empty namespace? >>>> >>>> >>>> >>>> Thanks, >>>> >>>> Alex. >>>> >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >>> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
