[
https://issues.apache.org/jira/browse/WODEN-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Kaputin updated WODEN-140:
-------------------------------
Attachment: woden140_option2.patch
woden140_option1.patch
Dan,
per our discussion could you look into implementing support for namespace
declarations across the WSDL Element model, rather than just fixing the support
that's currently only in DescriptionElement.
I have attached two patch files containing different options for the API:
1) woden140_option1.patch had namespace methods defined on WSDLElement and it
returns an array of NamespaceDeclarations
2) woden140_option2.patch uses a collection/iterator approach
To maintain consistency with the existing API I think I prefer option 1, but
please review both, do some prototyping if you like and I'll discuss them with
you before we decide.
> DescriptionElement.getNamespaces() should have a type-safe return type
> ----------------------------------------------------------------------
>
> Key: WODEN-140
> URL: https://issues.apache.org/jira/browse/WODEN-140
> Project: Woden
> Issue Type: Improvement
> Components: Parser
> Reporter: John Kaputin
> Assignee: Dan Harvey
> Fix For: M8
>
> Attachments: Woden-140.patch.txt, woden140_option1.patch,
> woden140_option2.patch
>
>
> The DescriptionElement.getNamespaces() method currently returns a Map
> containing pairs of prefix String and namespace URI. In keeping with woden
> design goals and the rest of the API, this method should use a type-safe
> return type. Map, List, etc represent their content as java.lang.Object which
> requires casting.
--
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]
