[
https://issues.apache.org/jira/browse/WODEN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865276#action_12865276
]
Dilshan Edirisuriya commented on WODEN-20:
------------------------------------------
Thanks Arthur for your valuable comments. I have following doubts.
1) Most of the time people don't use qualified names within the body of the
classes. When it refers to classes as there can be multiple classes with the
same name people can get confused. So is this a good approach. What do you
think?
2) At the moment I don't have a clear idea to handle this use case. May be I
can come up with a good solution later.
Any suggestion is welcome.
> Component model API needs modifiers
> -----------------------------------
>
> Key: WODEN-20
> URL: https://issues.apache.org/jira/browse/WODEN-20
> Project: Woden
> Issue Type: New Feature
> Components: Parser
> Reporter: Jeremy Hughes
> Assignee: Sagara Gunathunga
> Attachments: WodenProposal_Dilshan.pdf
>
>
> A Woden 'client' - eg a tool such as java2wsdl - might want to:
> 1 introspect a tree of java classes / interfaces
> 2 create an org.apache.woden.wsdl20.Interface for each - adding to the
> Description object along the way
> 3 serialize to disk.
> Today it is only possible to modify the object form of the WSDL through the
> Element model API. This requires the client app to understand WSDL at the
> file level.
> For step 2 addInterface() is required on Description. Of course
> Interface.addInterfaceOperation() is then required and so on...
> For step 3 a 'strategy' is needed to map from the Component model to the
> Element model's representation of the WSDL in file form. e.g. do all the
> <interface> elements go in the same WSDL file or do all the <interface>
> elements in the same namespace go in one file etc. Also, do the <service>
> elements go in separately included/imported WSDL files as is typically the
> best practice with WSDL 1.1. All these options could be represented using a
> strategy pattern.
--
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]
