The way I have been thinking about this is as follows:
If there was no refresh method, just have a stateless session bean with methods to
access the data, that loaded the data when the bean is first created.
There will probably not be a refresh requirement in our system (changes to the
'static' data will undoubtedly mean changes elsewhere will require a system shutdown.
However, is there any method to locate 'all' stateless session beans of a certain type
and then be able to call a method on each.
Another idea is to have an entity bean contains the last 'data version'. On each
access call, the stateless session bean could check with the entity bean that it has
the correct version, if not it refreshes. Then, when a data update is applied, all
that is required is to notify the entity bean. Would this work ? Any problems ?
Regards
Ed
On Mon, 17 July 2000, Ashwani Kalra wrote:
>
> Perhapas there are no APi to modify the behaviour of the container. So you
> cannot control to keep the stateles beans in the pool till the lifetime of
> the server process. Ofcourse you can call the ejbRemove method. Also there
> is not directo support for the call back mechanism that you are asking for.
> you have to take care for that. May be in future it may be provided
>
> Regards
> Ashwani Kalra
> E-Comm Group
> NIIT Ltd. India
>
>
> > ----------
> > From: Edward Barrett[SMTP:[EMAIL PROTECTED]]
> > Reply To: A mailing list for Enterprise JavaBeans development
> > Sent: Friday, July 14, 2000 5:39 PM
> > To: [EMAIL PROTECTED]
> > Subject: 'static' data in EJB architecture
> >
> > I have a requirement to have data stored in a database which will be
> > accessed from numerous session beans and servlets (it is the data that
> > controls the flow of the application, but could easily be a list of valid
> > choices, etc.).
> >
> > Ideally, I would like to be able to implement a class that resides in the
> > server for the length of the server instance's runtime, but which also has
> > a way of being 'refreshed'.
> >
> > I thought about stateless session beans which, upon their creation
> > obtained the data and cached locally. Can I configure my server so that
> > there are a minimum number of beans and so they stay resident ? Can the
> > server still passivate the bean and therefore wipe the data ?
> >
> > For the 'refresh' functionality, is there a manner to issue a message to
> > all the stateless session beans to notify them to refresh ?
> >
> > Is there another design for this requirement ?
> >
> > As always, TIA
> >
> > Ed
> >
> > PS How do I find the archive for this mailing list ? Also, to which URL
> > does one go to register for the list ?
> >
> >
> > ------------------------------------------------------------------------
> > Graham Parsons
> > Reflective Solutions Limited, London, UK
> > Tel: 07976 150940 E-mail: [EMAIL PROTECTED]
> > http://www.reflective.co.uk
> > ------------------------------------------------------------------------
> >
> > ==========================================================================
> > =
> > 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".
Visit http://www.oceanfree.net to get your free e-mail account and use our unique
Irish Internet directory
===========================================================================
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".
