[
https://issues.apache.org/jira/browse/WODEN-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514926
]
Dan Harvey commented on WODEN-40:
---------------------------------
To make the result of this JIRA clearer in r426030 comment Jeremy said:
"BTW: I decided to use add instead of create methods as add/remove is better
than create/remove or create/destroy IMO "
So we know the convention we are working with.
> Use composition in the element model instead of aggregation
> -----------------------------------------------------------
>
> Key: WODEN-40
> URL: https://issues.apache.org/jira/browse/WODEN-40
> Project: Woden
> Issue Type: Improvement
> Components: Parser
> Reporter: Jeremy Hughes
> Assignee: Jeremy Hughes
>
> Following on from this list discussion:
> http://mail-archives.apache.org/mod_mbox/ws-woden-dev/200606.mbox/[EMAIL
> PROTECTED]
> 1. remove addXxxElement methods. Change semantics of createXxxElement to
> "create and add"
> 2. distribute createXxxElement methods so they appear on the YyyElement
> interface where Yyy is the parent element of Xxx
> 3. XxxElementImpl to implement Cloneable and clone() to carry out a deep clone
> 4. add createXxxElement(XxxElement) methods to deep clone the parameter and
> add the clone to the target object
--
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]
