[ http://jira.andromda.org/browse/HIB-90?page=comments#action_11400 ]
     
Klaus Schultz commented on HIB-90:
----------------------------------

As I understand the special transitive persistence feature of hibernate, it has 
to be controlled by the developer with conscientious placement of 
"cascade"-properties. I think it would be quite helpfull for the developer, if 
he had a graphical view of, what are the central entities and how far reaches  
the transitive persistence of each. For this view, the UML aggregation and 
composition could be used. Unidirectional associations help also, since they 
can only cascade in one direction.

I propose the following adjusting screws at different levels for controlling 
the transitive hibernate persistence:
- a global property for the whole model (already in place, 
"hibernateDefaultCascade")
- a property as what cascade a UML aggregation should be interpreted (defaults 
to the globel property)
- a property as what cascade a UML composition should be interpreted 
(defaulting to "all-delete-orphan"). Actually, composition is always 
interpreted  as "all-delete-orphan", but perhaps some project would prefer 
another delete variant?
- a taggedvalue for the association end as last resort and fine control

I would implement this, if the responsible committer agrees with that concept. 
During reworking association ends, I would eliminate the need to mark one end 
of an One-to-One association as aggregation (issue SPRING-15).


> Cannot set cascade on individual associations
> ---------------------------------------------
>
>          Key: HIB-90
>          URL: http://jira.andromda.org/browse/HIB-90
>      Project: Hibernate Cartridge
>         Type: New Feature
>     Versions: 3.0 RC2
>     Reporter: Kiran Keshav
>     Assignee: Chad Brandon

>
> Currently, you can globally set the 'cascade' value which is used for all 
> associations.  
> You should be able to leave 'cascade=delete' (the default setting) but 
> override this by setting the cascade value on individual associations (via a 
> tagged value).  Andromda should then use the default setting for all 
> associations except those that have specified a tagged value.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.andromda.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Andromda-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-devel

Reply via email to