I do not cache my home objects. I look up a new one every time my JSP page
is invoked. So, I'm not sure that having a home object around is the
problem. I get a new InitialContext, do the lookup, the works. So this
isn't it. I was just curious as to see if this was a "java" problem, or a
"Jboss" problem, since sometimes, I have to restart Tomcat when it uses
standard "classes" and not EJBs in the same manner.
Wes
-----Original Message-----
From: Carlos Valiente [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 16, 2000 10:47 AM
To: jBoss
Subject: Re: [jBoss-User] Auto Deploy
Rickard �berg wrote:
> For each page request, get new InitialContext() (which is cached
> internally anyway, so it is VERY fast to do it!), lookup the home and
> create your session. When fail-over is done this should be changed so
> that you do lookup once, and then home.create on each page request.
So, to sum up:
1) for now, move the EJB initialization back to doGet()/dopost()
2) When fail-over is ready, the lookup call goes back to init() and
home.create() stays in doGet()/doPost()
--
"Es tristi di pidil, piru is mas tristi di pidil un duminiu .es"
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
