> >
> >2.0 container supports cascade delete, it looks applicable in your case.
>
> I know. But we can't use this feature, cause we have to write some history
> entries in other tables.

Can't you have method in session bean

public void delete( Integer key ) throws AppException,RemoveException {
    updateHistory( key );
    getBean( key ).remove();
}

it will happen in the same transaction and you do delete after update of
history tables.

Igor

====================================================================
Community Web Site (Core J2EE Patterns Catalog - Online Version):
http://java.sun.com/blueprints/corej2eepatterns
Getting Started (Beta Version):
http://developer.java.sun.com/developer/technicalArticles/J2EE/patterns/
Get the book:
http://www.amazon.com/exec/obidos/ASIN/0130648841/corej2eepatte-20
List Archive:
http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing:
email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)