If you expect transactional behavior of these "static" values, this
solution will not provide
it. Singleton entities bound into JNDI will provide transactional behavior.
Jim
Jim Rhyne, STSM, Component Broker Tool Architect
[EMAIL PROTECTED], 416 448 4383
IBM Canada Ltd. 2G/846/1150/TOR
1150 Eglinton Ave. E., Toronto, Ont. M3C 1H7 CANADA
Jim Frentress <[EMAIL PROTECTED]> on 04/15/99 03:24:34 PM
Please respond to A mailing list for Enterprise JavaBeans development
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: Jim Rhyne/Somers/IBM)
Subject: Re: Shared EJBs and staic variables
you can register whatever you want with jndi. i attach a uuid
generator (and lots of other stuff) to jndi and it is not an ejb. we access
it directly from jndi (eg we use no session bean to get to it)
> 2. Use a non EJB (I feel that using ejb's on the server side does not
mean
> all server side classes have to be EJbs ). The advantages are that you
> wouldn't have to worry about a persistence layer . Now to actually access
> the singleton class you could use a session bean whose sole purpose is to
> access the singleton class. I don't know if you can directly register the
> Non EJB singleton class with JNDI. I think you can and in that case you
> don't need the session bean.
>
>
> Sachin.
>
>
===========================================================================
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".
===========================================================================
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".
