the spec allows for cascade-delete. but there is not concept of cascasde-restrict. Meaning Do not delete this object if other objects depend on it.
Currently the default is to set the referencing objects to null, and then delete the object.
in the ejbRemove() do I have to code this?
if findbyFK().count > 0 then
throw excpetion.
somthing like the above? what I really would like is a cascade-restrict concept.
Anyone have an suggestions on a better solution?
