Eric Williams wrote: > And the EJB specification writers had to enable vendors to offer > advanced > products based on the specification (eg, EJB implemented *in* a > database, or a > multi-VM shared-memory approach, etc.)... some of which are incompatible > with > threads or file I/O. Something here bothered me and I just got it: if java.lang.Thread is part of the core Java language (as implemented by every VM, including Oracle's "advanced product" in-database VM), then how could you have an "advanced product" that is incompatible with it? Cheers, Laird =========================================================================== 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".
- Re: Amended list of resource managers (... francis pouatcha
- Re: Amended list of resource managers (... Assaf Arkin
- Re: Amended list of resource managers (... Hed Bar-Nissan
- Re: Amended list of resource managers (... Frank Sauer
- Re: Amended list of resource managers (... Assaf Arkin
- Re: Amended list of resource managers (... Sriram Srinivasan
- Re: Amended list of resource managers (... Assaf Arkin
- Re: Threads question Assaf Arkin
- Re: Threads question Eric Williams
- Re: Threads question Laird Nelson
- Re: Threads question Laird Nelson
- Re: Threads question Assaf Arkin
- Re: Threads question Tim Endres
- Re: Threads question Assaf Arkin
- Re: Threads question Sriram Srinivasan
- Re: Threads question Assaf Arkin
- Re: Threads question francis pouatcha
- Re: Threads question Sriram Srinivasan
- Re: Threads question Laird Nelson
- Re: Threads question Assaf Arkin
- Re: Threads question Laird Nelson
