On Tuesday 30 October 2007, Benson Margulies wrote: > I don't see how the @XmlElement annotation can do the job. At least in > the version of JAXB we have in 2.0.3, @XmlElement can't control the > form, only the namespace.
That's kind of the point. If @XmlElement is not there or if the namespace attribute is unspecified, it uses the namespace information from the package-info which is should be whatever from the default is for the schema. If the element in the schema has a "form" that doesn't match the default, jaxb will output either: 1) @XmlElement(namespace = "") (unqualified) 2) @XmlElement(namespace = "http://blah.blah.blah";) (qualified, namespace will match the schema namespace) Dan > > > -----Original Message----- > > From: Daniel Kulp [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, October 30, 2007 3:10 PM > > To: cxf-user@incubator.apache.org > > Cc: Benson Margulies > > Subject: Re: form attribute on xsd:element versus jaxb > > > > > > Actually, I think if the form doesn't equal the schema form, it > > outputs > > > the @XmlElement annotation with the proper namespace attribute. > > If > > it > > > does agree, it doesn't. > > > > Something like that at least. > > > > Dan > > > > On Monday 29 October 2007, Benson Margulies wrote: > > > So far as I can see, JAXB has no place to annotate an element that > > has > > > > a form= that disagrees with the schema default. > > > > > > Should wsdl2java complain when someone feeds it such a schema? I > > just > > > > tried it with the current 2.0.3 snapshot, and no error emerged. > > > > -- > > J. Daniel Kulp > > Principal Engineer > > IONA > > P: 781-902-8727 C: 508-380-7194 > > [EMAIL PROTECTED] > > http://www.dankulp.com/blog -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
