Rickard, > Giju Thomson wrote: > > > Can a entity bean be made to access more than one table in the > > database using EJB1.1 Spec > > When using BMP there are no restrictions on what an EntityBean uses as > underlying datastore. > > One thing to look out for is 2-phase commit support though, if you are > concerned with transactions using multiple datastores. >
There is nothing that restricts CMP either :) In fact section 9.4.1 of the EJB 1.1 spec states: "Because entity beans are typically coarse-grained objects, the content of the container-managed fields may be stored in multiple rows, possibly spread across multiple database tables. These mapping techniques are beyond the scope of the EJB specification, and do not have to be supported by an EJB compliant container." So, if a vendor does provide this feature (we do) - then it does solve a lot of developer concerns albeit with a loss of portability. But CMP does offer higher performance, cleaner coding and maintainability over their BMP counterparts. Think of this as a QoS feature that vendors should implement. <vendor> The Borland Enterprise Server supports mapping a CMP Entity Bean to multiple tables in a database. In addition, using 2PC and XA, it is possible to map a CMP entity bean to multiple tables in multiple heterogeneous databases. <vendor> -krish =========================================================================== 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".
