[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3475?page=c...
]
Felix Gnass commented on HHH-3475:
----------------------------------
BTW: Even a custom EntityNotFoundDelegate doesn't help as this leads to a
NullPointerException somewhere in Hibernate. So this renders any-mappings pretty much
useless in most situations.
Support not-found="ignore" for <any> mappings
---------------------------------------------
Key: HHH-3475
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3475
Project: Hibernate Core
Issue Type: Improvement
Components: core
Affects Versions: 3.3.0.SP1
Reporter: Felix Gnass
Priority: Minor
It would be useful if the <any> element would support the
not-found="ignore|exception" setting. Due to the nature of any-mappings it's
impossible to use on-delete cascades at the database layer, so it's very likely that
ObjectNotFoundExceptions occur.
Currently the only work-around to gracefully handle such situations seems to be the
implementation of a custom EntityNotFoundDelegate that doesn't throw an exception.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira