> ...then each of those methods are going to run in a separate
> transaction, and the bean will probably be loaded separately for each
> method call. Two database hits.
Makes sense, thanks!
--
Eric Jain
___
JBoss-user mailing list
[EMAIL PROTECTED]
Jeff Schnitzer wrote:
> How are you accessing the entity beans? If you access like this:
>
> void clientMethod()
> {
>foo = bean.getFoo();
>bar = bean.getBar();
> }
>
> ...then each of those methods are going to run in a separate
> transaction, and the bean will probably be loaded sepa
How are you accessing the entity beans? If you access like this:
void clientMethod()
{
foo = bean.getFoo();
bar = bean.getBar();
}
...then each of those methods are going to run in a separate
transaction, and the bean will probably be loaded separately for each
method call. Two database
On søn, 2002-04-07 at 16:16, Eric Jain wrote:
> I bundled a scheduled class together with the entity beans it uses so it can
> access them directly. Previously the scheduled class had to access the
> entity beans through a session bean, since the entity beans only have local
> interfaces (CMR...).
