>
>
> Hi,
> How coarse do we make our session bean? I have three business
> methods which
> are similar in nature, require the same entity beans for
> their execution.
> Option one:
> Put three remote methods in my session bean, one for each business
> requirement and keep one session facade. This makes for
> heavier components
Also increases code reuse.
> but reduces the number of different beans that the container
> has to manage
> Option two:
> Make three separate session beans which connect to the same
> entity beans.
> Lighter session beans but greater in number
This is not really an issue. The number of _instances_ in memory only
depends on the number of inflight calls (assuming stateless SBs, otherwise
the semantics change). The number of calls does not depend on your
partitioning.
>
> Which one is better?
>
If they are related, put them together. If they are unrelated, separate
them. Performance is not a factor here.
- Avi
--
This signature intentionally left blank.
===========================================================================
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".
