The "simple" fix might be to make aegis make all attribute unqualifed by default (to match what most people expect) and then provide the configuration overrides (either via xml config or from the annotations) to change that on a per-attribute basis.
For example, in this case, if he had done:
@XmlAttribute(name = "id", namespace="http://the.namespace";)
then it would have been qualified. If no namespace attribute, then unqualified.
Dan On May 8, 2008, at 9:13 PM, Benson Margulies wrote:
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?
--- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog
