Hi all,
I got a definition like this in the schema I use in my wsdl
complexType name=ProjectMemberType
sequence
element name=UserId nillable=true type=xsd:int /
element name=Username nillable=true type=xsd:string /
element name=Email nillable=true
fourni.
Date: Mon, 10 Aug 2009 15:01:21 +0200
Subject: Not Generating prefixes for sub-sub elements
From: hakon.sageh...@bccs.uib.no
To: axis-user@ws.apache.org
Hi all,
I got a definition like this in the schema I use in my wsdl
complexType name=ProjectMemberType
sequence
Håkon,
Note that even though the Roles element has no prefix, it is still in
the right namespace.
Andreas
2009/8/10 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
Hi all,
I got a definition like this in the schema I use in my wsdl
complexType name=ProjectMemberType
sequence
Hi
Yes I know that it's in the same namespace, but we have in our project best
practices that all our elements should have fully elementFormDefault names,
so is it possible to get this? And if the attribute elementFormDefault set
to elementFormDefault then all elements should have prefixes or?
The actual value of the prefixes is irrelevant.
elementFormDefault=qualified only means that the elements must be
namespace qualified and this is the case here. So you are actually
following the best practices.
Andreas
2009/8/10 Håkon Sagehaug hakon.sageh...@bccs.uib.no:
Hi
Yes I know that
