[jira] Updated: (ISIS-79) Fix "additional business logic" hooks in collection templates

["Mike Burton (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ISIS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Burton updated ISIS-79:
----------------------------

    Attachment: mutreg.diff

I noticed problems in the business logic hook mechanism, that would require changes to the noc* code templates. I then realised this would not be a quick fix, so I developed a  Mutual Registration sample (based on the Customer / Car example in Dan's book) allowing dis/association from either end of the association.

I've attached mutreg.diff here as a patch for review, specifically:
- I've put it in <trunk>/contribs/MutualRegistration -  is this the best place?
- Visibility of underlying accessor methods
- Can you think of any more test cases?
- How can this extend to many:many relationships and their templates?
- Impact on other artefacts (documentation, examples,...)

Mike

> Fix "additional business logic" hooks in collection templates
> -------------------------------------------------------------
>
>                 Key: ISIS-79
>                 URL: https://issues.apache.org/jira/browse/ISIS-79
>             Project: Isis
>          Issue Type: Improvement
>          Components: Domain: Entities
>    Affects Versions: 0.1.0-incubating
>         Environment: Eclipse code templates
>            Reporter: Mike Burton
>         Attachments: mutreg.diff
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> The code generated by Eclipse templates such as noc does not ensure consistent execution of the "additional business logic" hook methods.
> See email with patch for contribs/MutualRegistration sample
> May also impact existing examples, and ducumentation

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.