To answer part of my own question: The result is
@XmlElement(namespace = "") The result of this, indeed, is to force an explicit prefix for the current schema TNS. > -----Original Message----- > From: Benson Margulies [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 31, 2007 9:27 AM > To: [email protected] > Cc: Daniel Kulp > Subject: RE: XmlSchemaElement qname not set for qualified element + form > not set right > > This thread concerns the construct: > > @XmlElement(namespace = "some_other_namespace") > int intValue; > > Yesterday, Dan Kulp offered the idea (I thought) that this was the way > to get a schema like: > > <xsd:element form='qualified' ref='son:intValue' .../> > > Sadly for me at the moment, I note that the form property of the element > is 'none', and so is the form property of the referenced element. > > I can code the javascript generator to force qualification in this case, > but is this correct? > > One possibility is that jaxb is just not interested in form= on > elements, and only does qualification when it notices a schema > disparity. This leads to interesting questions about what happens when > you construct a WSDL/XSD that uses form='qualified' 'gratuitously', in > terms of what annotations result. >
