You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by "Dilshan Edirisuriya (JIRA)" <ji...@apache.org> on 2010/05/06 22:30:49 UTC
[jira] Updated: (WODEN-20) Component model API needs modifiers
[ https://issues.apache.org/jira/browse/WODEN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dilshan Edirisuriya updated WODEN-20:
-------------------------------------
Attachment: WodenProposal_Dilshan.pdf
Proposed design for this issue
> 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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org