Yes. I don't really have a timescale to switch to CXF but it would be useful for the future for our application to do so. That would be good feature to have.
Richard Grantham Development ------------------------------- [EMAIL PROTECTED] Limehouse Software Ltd DDI: (020) 7566 3336 Main: (020) 7566 3320 Fax: (020) 7566 3321 Limehouse Software Ltd 4th Floor 1 London Bridge London SE1 9BG Manchester Office: 3rd Floor, The Triangle, Exchange Square, Manchester M4 3TR Tel: (0161) 240 2440, Fax: (0161) 240 2441, ISDN: 08700 119 400 Check out Limehouse Software's innovative solutions www.limehousesoftware.co.uk - Transforming the way you publish and consult on information The information contained in this e-mail or in any attachments is confidential and is intended solely for the named addressee only. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Limehouse Software Ltd immediately by returning this e-mail to sender or calling 020 7566 3320 and do not read, use or disseminate the information. Opinions expressed in this e-mail are those of the sender and not necessarily the company. Although an active anti-virus policy is operated, the company accepts no liability for any damage caused by any virus transmitted by this e-mail, including any attachments.-----Original Message----- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: 09 May 2008 02:13 To: [email protected] Subject: Re: Namespaces on attributes I read the code. As the code exists in CXF, Aegis has no feature for creating unqualified attributes. However, the WSDL should correctly describe their qualified status, so conformant clients should work. The annotation you are using is based on JAXB. In JAXB, you would use, I think, a package-level annotation to set the qualification default. Aegis lacks a concept of package-level options. I could add a databinding option to make attributes unqualified, it wouldn't be too tough. I would, however, add it to 2.1.x, not 2.0.x. Can you move to that stream?
