Your bean should implement the Synchronization interface. This way it
will be notified regarding the status of the commit.
Juliano Junio Viana wrote:
>
> Hi,
>
> I am pretty new to ejb, but i think this issue was not adressed on this
> list before ( if it is a issue at all :) )
> I have some BMP entity ejb4s that do *not* store information on
> JDBC-aware databases.
> One such creature is a ejb that represents a virtual domain. The virtual
> domain4s configuration is stored in a configuration file used by the
> web server, and the ejb parses the file on ejbLoad() and changes the
> file on ejbStore().
> I have found a problem with this approach: the entity beans are never
> notified of a tranaction rollback. So, if i have method calls on several
> beans in the same transaction, when i commit the transaction my bean
> will receive a ejbStore() call, but if the transaction is rolled back it
> will never know ( and therefore never be able to roll back the change).
> In the spec4s sequence diagrams, the rollback notification goes to the
> database(as a resource registered with the transaction coordinator ),
> but in this case there is no " database" .
> Any sugestions on how can i make my ejb transaction aware in this case?
>
> Regards,
>
> Juliano.
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
--
Hal
___
Casual match in a very dry field
http://www.hellblazer.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
