[
https://issues.apache.org/jira/browse/WODEN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866443#action_12866443
]
Lawrence Mandel commented on WODEN-20:
--------------------------------------
I'll echo the comments that this is a good write up that may simply need a few
tweaks.
1. I agree that using the same interface names for the editable interface will
likely be problematic.
2. >2.)Create a new method called, 'Add(Component subComponent)' to add the
existing sub component to
>the component. This method will be needed for the Serializatio
>3.)Create new methods, 'attach(Component subComponent)' and 'detach(Component
>subComponent)',
Do the attach and add methods perform similar function? I'm not clear on the
difference according to the description.
3. For serialization, how about a strategy that separates the abstract
descriptions from the concrete implementation details. In this scenario schemas
will be written to their own files (I consider this a best practice),
interfaces will be written to one WSDL file that is then included in a WSDL
file containing the bindings and services.
> 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]
