Maybe this has to do with the Bean naming convention ...
Slighty off-topic: What I find even more frustrating is that if you use code-first approach with Aegis binding, all your elements will be lowercase. I'm quite sure xml naming conventions require elements start with an uppercase and attributes start with lowercase. Wouldn't it be a good idea to make this default behavior? Dylan Honorez R & D Consultant 4C Technologies / kZen +32 (0)485 / 69.28.12 [EMAIL PROTECTED] From: Christopher Moesel [mailto:[EMAIL PROTECTED] Sent: maandag 26 maart 2007 21:51 To: [email protected] Subject: [xfire-user] Element Names Starting With Consecutive Capital Letters Cause NullPointerException I don't know if anyone else has seen this one yet, but... I have an XFire 1.2.5 WSDL-first service. I was getting NullPointerExceptions when sending requests. After some investigation, it turns out that leading consecutive capital letters cause problems. For example, the following request type (as defined in the WSDL) will break XFIRE: <xsd:complexType name="OrderPizzaType"> <xsd:sequence> <xsd:element name="PHoneNumber" type="xsd:string" /> <xsd:element name="Toppings" type="tns:ToppingsListType" /> </xsd:sequence> </xsd:complexType> Change the "PH" to "Ph" and everything is fine again. I've filed a bug with a working (err... not working) example: http://jira.codehaus.org/browse/XFIRE-928 -Chris
