> -----Original Message----- > From: A mailing list for Enterprise JavaBeans development > [mailto:[EMAIL PROTECTED]]On Behalf Of Filip Hanik > well, consider a clustered server environment where you will have to keep > transactional locks synchronized across servers in a distributed > transaction. It doesn't matter. If you had stateless session beans spread out across these servers, and they needed to participate in the same transaction, you would get the same results. jim =========================================================================== 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: Entity beans vs DAO(Data Access Objects) James Cook
- Re: Entity beans vs DAO(Data Access Objects) Elatta, Sally
- Re: Entity beans vs DAO(Data Access Objects) James Cook
- Re: Entity beans vs DAO(Data Access Objects) Filip Hanik
- Re: Entity beans vs DAO(Data Access Objects) John Harby
- Re: Entity beans vs DAO(Data Access Objects) Filip Hanik
- Re: Entity beans vs DAO(Data Access Objects) John Harby
- Re: Entity beans vs DAO(Data Access Objects) Ian McCallion
- Re: Entity beans vs DAO(Data Access Objects) James Cook
- Re: Entity beans vs DAO(Data Access Objects) Filip Hanik
- Re: Entity beans vs DAO(Data Access Objects) James Cook
- Re: Entity beans vs DAO(Data Access Objects) Filip Hanik
- Re: Entity beans vs DAO(Data Access Objects) Geert Mergan
- Re: Entity beans vs DAO(Data Access Objects) James Cook
- Is EJB Client Stub remote interface method synchroniz... Pradeep Mysore
- Re: Entity beans vs DAO(Data Access Objects) James Cook
- Re: Entity beans vs DAO(Data Access Objects) Anup Maliyackel
- Re: Entity beans vs DAO(Data Access Objects) James Cook
- Re: Entity beans vs DAO(Data Access Objects) Geert Mergan
- Re: Entity beans vs DAO(Data Access Objects) James Cook
- Re: Entity beans vs DAO(Data Access Objects) John Harby
