[ 
https://issues.apache.org/jira/browse/AXIS-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515612
 ] 

Christoph Ludwig commented on AXIS-2682:
----------------------------------------

I realized after submitting the issue report that the attribute xmlns="" is 
used to bring the elements back into the global namespace in case an outer 
element changed the default namespace and can be certainly valid. Thus, the 
first part of my report was in fact misleading, sorry.

The real problem is, though, that in my example both the data and the length 
element do not belong to the global  namespace but to 
"http://www.textgrid.de/tests/bytearray/";. (By accident, I submitted the report 
before I was finished, therefore this is mentioned in the first comment only.)

So the subject of this issue should rather read "WSDL2Java spuriously puts 
complex type members in the global namespace". And that *is* a bug, I think... 

> wsdl2Java generates invalid empty string namespaces
> ---------------------------------------------------
>
>                 Key: AXIS-2682
>                 URL: https://issues.apache.org/jira/browse/AXIS-2682
>             Project: Axis
>          Issue Type: Bug
>          Components: WSDL processing
>    Affects Versions: 1.4
>         Environment: Eclipse 3.2 on Mac OS 10.4.10 (Intel)
>            Reporter: Christoph Ludwig
>         Attachments: bytearray.wsdl
>
>
> I generated with WSDL2Java a service skeleton and client stubs for the 
> attached WSDL which I used for interoperability tests. When I investigated 
> errors, I found the following in the generated SOAP request:
>   <?xml version="1.0" encoding="UTF-8"?>
>      <soapenv:Envelope 
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>         <soapenv:Body>
>            <AcceptBase64 xmlns="http://www.textgrid.de/tests/bytearray/";>
>               <data xmlns="">SGVsbG8gV29ybGQh</data>
>               <length xmlns="">12</length>
>            </AcceptBase64>
>         </soapenv:Body>
>      </soapenv:Envelope>
> Note the empty namespaces in the data and length elements. The W3C 
> recommendation "Namespaces in XML 1.0" states explicitly: "The empty string, 
> though it is a legal URI reference, cannot be used as a namespace name" 
> (http://www.w3.org/TR/xml-names/#iri-use). 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to