Ticket UUID: | 6fbee3208ebdd73ea2f50a8ed1d0c03545ce3261 | ||
Title: | xs:element type and xmlns | ||
Status: | Closed | Type: | Feature_Request |
Severity: | Important | Priority: | Immediate |
Subsystem: | Utilities | Resolution: | Fixed |
Assigned to: | unassigned | ||
Last Modified: | 2020-11-05 16:50:09 | ||
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="http://foo.org/bar" /> ... 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: 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: 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 have added an error condition, that a locally not found namespace should stop directly and not use a global prefix. Example: <global xmlns:x1="URI1"> <x1:el xmlns:x1="URI2"> </global> 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 oehhar added on 2020-11-05 16:49:51 UTC: |
Attachments:
- Utilities.patch [download] added by chw on 2018-09-21 06:26:33. [details]