DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8296>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8296

WSDL2Java forces use of namespace prefix in type attribute value





------- Additional Comments From [EMAIL PROTECTED]  2002-04-24 15:05 -------
Thanks for your comments.  I was messing around with the included file and had 
sent up the wrong one.  I am still curious about the xmlns= thing.  For 
example, if I have an instance that looks like this:

<?xml version="1.0" ?>
 <doc>
  <a>bugs?</a>
 </doc>

Then presumably I could right a schema that looks like this:

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
 <xsd:element name="doc">
  <xsd:complexType>
   <xsd:sequence>
    <xsd:element name="a" type="xsd:string"/>
   </xsd:sequence>
  </xsd:complexType>
 </xsd:element>
</xsd:schema>

With no xmlns= ... It seems to me that you would have this problem whenever you 
converted a DTD to a Schema.  Is that not a consideration? 

Then my WSDL would refer to it like this: 

<wsdl:message name="currentInput">
  <wsdl:part name="composite" element="doc" />
</wsdl:message>


In the Schema Structures document (3.15.2) there is a paragraph that states:

"Since the empty string is not a legal namespace name, supplying an empty
string for targetNamespace is incoherent, and is not the same as not
specifying it at all. The appropriate form of schema document corresponding
to a .schema. whose components have no {target namespace} is one which has
no targetNamespace attribute specified at all."

Just trying to get some clarity on all this, so thanks for your help.

Reply via email to