MessagePartInfo with apparently incorrect element name

[Benson Margulies <bi...@basistech.com>]

JAXB+JAXWS ... I have a MessagePartInfo with isElement true, xmlSchema
null, and the element QName has no namespaceURI. The name comes from an
@WebParam which has a plain, unqualified name in it. So I suppose I'm
dealing with a name in the service TNS, but is this how we want these to
come through?

Re: MessagePartInfo with apparently incorrect element name

[Daniel Kulp <dk...@apache.org>]

Benson

On Wednesday 07 November 2007, Benson Margulies wrote:
> JAXB+JAXWS ... I have a MessagePartInfo with isElement true, xmlSchema
> null, and the element QName has no namespaceURI. The name comes from
> an @WebParam which has a plain, unqualified name in it. So I suppose
> I'm dealing with a name in the service TNS, but is this how we want
> these to come through?

I'm definitely concerned about the xmlSchema being null.   That really 
looks bad.  :-(    That's my #1 concern with the above.

I think currently, the QName will not have a namespaceURI if the schema 
is unqualified (which is the default for JAXWS).     That is paritially 
historical.   Originally, the MessagePartInfo didn't have 
a "ConcreteName" field so the element name was overloaded to be the 
concrete name.   We added the ConcreteName stuff to hold the "what it 
really looks like" version so, in theory, the part names could be 
updated to have the proper namespaces.


-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog