Hi, all
I have two questions:
1. For an EJB container, is it easier to manage 100 pooled instances of the
same stateless session bean class or 100 pooled instances of 10 different
SLSBs(10 instances for each SLSB)?
2. Can I specify 10 different EJBs in the xml deployment descriptor with
different <ejb-name>'s but with the same remote, home interfaces, and the
EJB class? For example, I want to use ejb1, ejb2, ejb3, ... ejb10 as the
<ejb-name>'s to specify 10 EJBs in the descriptor. But they all use the
same remote interface, home interface, and the EJB class.
The reason is that we currently have an application that contain dozens of
EJB classes that differ only by their class names. Based on arguments
passed in, they do different things. The people who developed them claim it
is to provide granularity to control security, transaction, etc. for each
bean. If a generic EJB was used, it wouldn't be able to take advantage of
the features an EJB container offers to control security, transaction at a
bean, or even a method, level. Therefore, if the anser to my second
question above is yes, it would solve the granularity issue.
Thanks a lot.
===========================================================================
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".
