I see
this specified in 16.4.
Do you
know why this restriction is imposed ?
Is it
because there is a generated BeanImpl class and that raises the issue of
duplicating all the static methods over there and gets complicated by the fact
that in Java the instances can directly access static/class variables of their
class and thus some methods would be accessing the copy on the bean class and
others could be accessing the static methods/variables on the generated Impl
class ?
Is this
restriction going to be removed in the next EJB spec ?
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]]On Behalf Of Tom Valesky
Sent: Wednesday, April 14, 1999 4:11 PM
To: [EMAIL PROTECTED]
Subject: Re: Static variables in EJBs?Only if they're final. Otherwise, it's prohibited.===========================================================================
Tom Valesky -- [EMAIL PROTECTED]
http://www.patriot.net/users/tvalesky-----Original Message-----
From: Damon Williams <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, April 14, 1999 3:12 PM
Subject: Static variables in EJBs?Can you define static variables in an EJB?
