View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820785#3820785
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820785
Thanks Juha,
Your advice is very helpfull.
Cari
---
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820694#3820694
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820694
If the singleton returns immutable values it should be ok. Mutable values don't work
in a cluster setu
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820631#3820631
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820631
Hi Juha,
Thank you very much.
I wandered whether there is a harm to call a singleton class from the
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820620#3820620
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820620
Yes the objects will be available to all clients (they're pooled). So if you use
instance fields they
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820607#3820607
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820607
Hi Adrian and Marc,
Thank you.
The field I want to put in the stateless session bean is not session
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820601#3820601
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820601
having a field in stateless only makes sense if all the sessions need that field. If
the field is ses
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820597#3820597
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820597
The session objects are pooled (and lazily constructed).
This means your ejbCreate() won't be invoke
