Hal Hildebrand wrote:
>
> Your bean should implement the Synchronization interface. This way it
> will be notified regarding the status of the commit.
>
yes, it works fine with sessions, but i�m talking about entities...
I will have to implement a server-dependent "file system resource"
anyway, because of the new restrictions os the 1.1 spec ( no java.io
permission ) :/
Isn�t this kind of restriction too hard for a specification that aims
compatibility with legacy data?? I am starting to wonder if i really
worths it implementing my business objects as ejb....
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".
- BMP(non-database) & transaction behaviour Juliano Junio Viana
- Re: BMP(non-database) & transaction behaviour Larry Allen
- Re: BMP(non-database) & transaction behav... Rickard �berg
- Re: BMP(non-database) & transaction b... Larry Allen
- Re: BMP(non-database) & transaction b... Karl-Fredrik Blixt
- Re: BMP(non-database) & transacti... Rickard �berg
- Re: BMP(non-database) & tran... Karl-Fredrik Blixt
- Re: BMP(non-database) & transaction behaviour Hal Hildebrand
- Re: BMP(non-database) & transaction behav... Juliano Junio Viana
- Re: BMP(non-database) & transaction behaviour Chip Wilson
- Re: BMP(non-database) & transaction behaviour Chris Raber
- Re: BMP(non-database) & transaction behav... James Cook
- Re: BMP(non-database) & transaction behaviour Chris Raber
- Re: BMP(non-database) & transaction behaviour Chip Wilson
- Re: BMP(non-database) & transaction behav... Hal Hildebrand
- Re: BMP(non-database) & transaction behaviour Chip Wilson
