View Ticket
Not logged in
Bounty program for improvements to Tcl and certain Tcl packages.
Tcl 2019 Conference, Houston/TX, US, Nov 4-8
Send your abstracts to [email protected]
or submit via the online form by Sep 9.
Ticket UUID: 6fbee3208ebdd73ea2f50a8ed1d0c03545ce3261
Title: xs:element type and xmlns
Status: New Type: Feature_Request
Severity: Important Priority: Immediate
Subsystem: Utilities Resolution: Open
Assigned to: unassigned
Last Modified: 2018-11-05 13:44:56
Version Found In: trunk
Description & Comments:
In order to deal with a WSDL and XSDs which had an unusual layout of xmlns attributes as outlined in this example
... <xs:element name="A_O_S" type="x1:ArrayOfSomething" xmlns:x1="" /> ...

i.e. the xmlns stuff not in the <xs:schema> node I had to add some handling in WS::Utils::getQualifiedType to get that WSDL parsed proper. I'm not sure if this the right way, however, it solved my problem. Please review and comment.

oehhar added on 2018-10-11 18:45:54 UTC:
Sorry, Christian, did not see your message.

May take a bit of time, on travel (ending on US ETCL conf).

Take care, Harald

oehhar added on 2018-11-05 08:55:54 UTC:
Thank you, Christian.

Code added in branch [ticket-6fbee320-local-ns-prefix].

I think the modification is ok. It is hard to check without a test web service.

I will do some additional tests and merge.

Thank you, Harald

oehhar added on 2018-11-05 13:44:56 UTC:
I ask to review the branch.

I have added an error condition, that a locally not found namespace should stop directly and not use a global prefix.


<global xmlns:x1="URI1">
    <x1:el xmlns:x1="URI2">

In this case, "URI1" should not be linked to node local namespace prefix x1, as it means something else.

It my thinking ok ? And the implementation ?

Thank you, Harald