Hi!
Neil Thorne wrote:
> Why even use a Bean at all? You don't have to make all of your system fit
> the EJB model.
No, but it makes things easier for deployment. Everything your app needs
fits inside the EAR-file. Also, a singleton implemented as an EJB could
make use of all features that EJB's have such as security, transactions
and easy hookup into resource managers through the java:-namespace.
Those are very good reasons IMHO.
> You can use some of the other great things in J2EE, like the
> JNDI. Why not put your singleton java object in a JNDI namespace?
Does all JNDI implementations support that?
> Okay so
> you won't be able to propogate your transactional context if you need one,
> unless of course you use a persistent JMS to transmit the request to the
> JNDI singleton. If you don't need to propogate a transactional context then
> personally I'd go with the JNDI.
Well, as above, there are other reasons why implementing it as an EJB
would be a good idea.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
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".
