Well, ok. But how can it be right to have unqualified names from both, which is a current behavior.
<schema xmlns="http://www.w3.org/2001/XMLSchema"; attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://stuff.basistech.com";> <complexType name="ArrayOfName"> <sequence> <element maxOccurs="unbounded" minOccurs="0" name="Name" nillable="true" type="ns1:Name"/> </sequence> </complexType> <complexType name="Name"> <sequence> <element minOccurs="0" name="data" nillable="true" type="string"/> <element minOccurs="0" name="uid" nillable="true" type="string"/> </sequence> </complexType> </schema> > -----Original Message----- > From: Glen Mazza [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 04, 2007 10:38 AM > To: [email protected] > Subject: Re: targetNamespace > > Am Dienstag, den 04.09.2007, 10:09 -0400 schrieb Benson Margulies: > > I'm reasonably clear that the first part of the problem with CXF-959 is > > that NamespaceHelper.getPrefix is ignorant of the targetNamespace > > attribute of the schema. However, I'm not quite sure what to do about > > this. Examples I see all over the web leave types in the targetNamespace > > unqualified, but carefully qualify xsd: types. The WSDL coming out of > > CXF doesn't qualify xsd types, but doesn't pay attention to the > > targetNamespace. What's correct? > > There's apparently no set answer for that: > http://64.233.169.104/search?q=cache:LrQ6yu7uWaUJ:www.xfront.com/Default Na > mespace.pdf+xfront+targetnamespace&hl=en&ct=clnk&cd=1&gl=us > > Glen >
