John, I did make that allowance in my first mail :)
<self-quote> Since entity beans typically add overhead (yes, even with local interfaces!), I'd recommend the use of a bulk get to transfer data between the local entity bean & the session facade when accessing a majority of the persistent fields. ..... On the other hand, if the client (session facade or whatever) needs only a subset of the persistent fields then probably fine-grained/ejbSelect methods can be used. .... And this bulk-getter can co-exist with fine-grained accessor methods which (as mentioned above) can be used in other use-cases. </self-quote> -krish > Ok, but then your operations aren't isomorphic, namely > > AB getAB(); // bulk accessor called at time t_0 > checks the declarative context (tx, sec, etc.) at t_0 whereas: > > A getA(); // call at t_0 > B getB(); // call at t_1 > > checks the declarative ctx at both t_0 and t_1, there is additional > behaviour required *unless* you can allow a call to pin the > declarative ctx so that the second check isn't performed. This > may actually be useful for large systems where users want to use > EJB to say help front a warehouse. People might want to accept restrictions > associated with some sort of "pinning" for certain > beans in certain cases. =========================================================================== 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".
