This is partly true for the company I work for as well, There it is not so much that we do not want to run 1.5, but that the appserver we use (wls 8.1) does not support using newer jvm's (it doesn't even start trying without anything deployed in it with 1.5). So that would mean migrating to wls 9, which is approx. a 6-7 month project IF decided to do so. It's (partly) my job to give 'advance warnings' on this so once apps that require 1.5 are comming out, we have a platform.
Rainer, wouln't these kinds of announcements trigger the company you work for to decide to skip 1.4 and go to 1.5?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991594#3991594
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991594
I have a servlet talking to a Sessionbean.
Is it allowed -regarding threadsafeness - to obtain the manager in the servlets init() method and store it in an instance-membervariable of the class.
public class LzServlet extends HttpServlet {
|
| MandantenManager mm =null;
|
| public void init(ServletConfig config)
| {
| try
| { InitialContext ctx = new InitialContext();
| mm = (MandantenManager) ctx.lookup("BBCS/MandantenManagerBean/remote");
| }
| catch (Exception e)
| { e.printStackTrace(); }
| }
Is getting the initialcontext and the lookup an "expensive" operation?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991590#3991590
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991590
Gavin, we are still stuck with this. You also recently confirmed this http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991260#modules/....
So it is like: Hibernate team fixed it in 3.2 CR1, EJB team did so in EJB 3.0 RC7 - FD as well. But these versions are incompatible. Right?
OK, so what has to be fixed in EJB3 then? Is it http://jira.jboss.com/jira/browse/EJBTHREE-795? (Yeah, I know it says JBoss Cluster, but the linked forum topic seems to address a problem not only limited to JBoss Clustering but to Hibernate Query Cache usage.)
So, you see - I'm somewhat lost as to where I have to ask for a fix. Could you either give me a hint on the Jira issue in EJB3 context, are at least an explanation of what exactly goes wrong if a more recent EJB3 release is used?
We are nearing a production roll out, and the idea of a "could not sync"-issue on a productive systems really gives me the creeps. :-/
As usual - thanks for you support.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991589#3991589
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991589
