public static final class

CascadeStyle.MultipleCascadeStyle

extends CascadeStyle
java.lang.Object
   ↳ org.hibernate.engine.CascadeStyle
     ↳ org.hibernate.engine.CascadeStyle.MultipleCascadeStyle

Summary

[Expand]
Inherited Fields
From class org.hibernate.engine.CascadeStyle
Public Constructors
CascadeStyle.MultipleCascadeStyle(CascadeStyle[] styles)
Public Methods
boolean doCascade(CascadingAction action)
For this style, should the given action be cascaded?
boolean hasOrphanDelete()
Do we need to delete orphaned collection elements?
boolean reallyDoCascade(CascadingAction action)
Probably more aptly named something like doCascadeToCollectionElements(); it is however used from both the collection and to-one logic branches...
String toString()
[Expand]
Inherited Methods
From class org.hibernate.engine.CascadeStyle
From class java.lang.Object

Public Constructors

public CascadeStyle.MultipleCascadeStyle (CascadeStyle[] styles)

Public Methods

public boolean doCascade (CascadingAction action)

For this style, should the given action be cascaded?

Parameters
action The action to be checked for cascade-ability.
Returns
  • True if the action should be cascaded under this style; false otherwise.

public boolean hasOrphanDelete ()

Do we need to delete orphaned collection elements?

Returns
  • True if this style need to account for orphan delete operations; false othwerwise.

public boolean reallyDoCascade (CascadingAction action)

Probably more aptly named something like doCascadeToCollectionElements(); it is however used from both the collection and to-one logic branches...

For this style, should the given action really be cascaded? The default implementation is simply to return doCascade(CascadingAction); for certain styles (currently only delete-orphan), however, we need to be able to control this seperately.

Parameters
action The action to be checked for cascade-ability.
Returns
  • True if the action should be really cascaded under this style; false otherwise.

public String toString ()