Hey ant: I forgot to ask. What technology *is* being used to generate the beans (I presume from .NET WSDL)? I would posit that said technology is broken if it doesn't create the right mappings from XML <-> Java....
--Glen > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 17, 2003 4:41 PM > To: [EMAIL PROTECTED] > Subject: DO NOT REPLY [Bug 16485] - BeanDeserializer error when XML > element starts with a capital letter > > > DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG > RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT > <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16485>. > ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND > INSERTED IN THE BUG DATABASE. > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16485 > > BeanDeserializer error when XML element starts with a capital letter > > > > > > ------- Additional Comments From [EMAIL PROTECTED] > 2003-02-17 21:40 ------- > Hi Glen, thanks for looking at this, I don't think you've > misunderstood the > problem. > > Yes its for non AXIS generated beans - just a class with > getters and setters for > the fields. With the current BeanDeserializer its imposible > to use a bean like > that when the schema uses names which start with a capital letter. > > I don't know if theres a spec defining exactly how the > BeanDeserializer should > work, but to me this looks like a bug. The BeanDeserializer > changes the case of > the 1st character of the name using the normal XML<->Java > name mapping rules and > gets it wrong, almost looks like MS did this on purpose just > to be troublesome > for Java. This patch just sets the case of the 1st character > back again. > > I can't imagine there's that much WSDL that will break with > this "lenient" > approach whereas most beans from .Net WSDL are broken as it > is now if AXIS isn't > used to generate the bean. Doesn't seem very user friendly. >
