Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Static variables restriction in session beans

It's impossible to use static variables on a session bean code. Is this restriction arbitrary or fundamented? And why?

Best regards

like image 821
thathashd Avatar asked Feb 04 '12 14:02

thathashd


People also ask

Can ejb be static?

Nonfinal static class fields are disallowed in EJBs because such fields make an enterprise bean difficult or impossible to distribute. Static class fields are shared among all instances of a particular class, but only within a single Java Virtual Machine (JVM ).

Can you have a private static variable?

Just like an instance variables can be private or public, static variables can also be private or public.

Are static variables thread safe?

Static variables are not thread safe. Instance variables do not require thread synchronization unless shared among threads. But, static variables are always shared by all the threads in the process. Hence, access to static variable is not thread safe.


2 Answers

As stated in the FAQ on EJB restrictions, one of the restrictions for using EJBs is:

enterprise beans should not read or write nonfinal static fields

Further expanded in the discussion on static fields:

Nonfinal static class fields are disallowed in EJBs because such fields make an enterprise bean difficult or impossible to distribute. Static class fields are shared among all instances of a particular class, but only within a single Java Virtual Machine (JVM). Updating a static class field implies an intent to share the field's value among all instances of the class. But if a class is running in several JVMs simultaneously, only those instances running in the same JVM as the updating instance will have access to the new value. In other words, a nonfinal static class field will behave differently if running in a single JVM, than it will running in multiple JVMs. The EJB container reserves the option of distributing enterprise beans across multiple JVMs (running on the same server, or on any of a cluster of servers). Nonfinal static class fields are disallowed because enterprise bean instances will behave differently depending on whether or not they are distributed.

It is acceptable practice to use static class fields if those fields are marked as final. Since final fields cannot be updated, instances of the enterprise bean can be distributed by the container without concern for those fields' values becoming unsynchronized.

like image 105
Óscar López Avatar answered Oct 20 '22 19:10

Óscar López


It is fundamental. As per this sun documenation,

Nonfinal static class fields are disallowed in EJBs because such fields make an enterprise bean difficult or impossible to distribute. Static class fields are shared among all instances of a particular class, but only within a single Java Virtual Machine (JVM). *

like image 28
kosa Avatar answered Oct 20 '22 18:10

kosa