Javier,
Does the fact that static objects work for you mean it is approved by the
spec, or maybe the ejb vendors haven't fully followed the spec, or you were
just lucky?
When you say "singleton lookup tables of read-only data" do you mean a
static Hashtable can or can't be used to get/put data?
-Ron
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Javier Borrajo
> Sent: Tuesday, October 26, 1999 4:05 PM
> To: [EMAIL PROTECTED]
> Subject: Re: EJB Restrictions-- threads, io
>
>
> >I looked in the list, but these restrictions seemed to apply to the EJB
> Bean
> >itself. I understand the container-managed instance pooling imposes this
> >restriction somehow, although I dont understand exactly why.
> >
> >In particular, I'm wondering if static data can be moved into a utility
> >class which is created by the EJB bean code, and therefore get around the
> >static restriction.
>
> We do just that. It works with several EJB servers we have evaluated.
> We use singleton lookup tables of read only data implemented with static
> instances.
>
> Life's too hard without singletons ;-)
>
> BTW, we asked the same question in this list around March, I think.
>
> Regards
>
> Javier Borrajo
> www.tid.es
>
> ==================================================================
> =========
> 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".
