Okay, got this. I'm still trying to understand where some resource
pooling might be adventageous. Until tomcat can do interface reloading
(as Rickard mentioned elsewhere), hot deploy isn't useful for those using
tomcat. But is there opportunity to do some level of resource pooling?
Interested if there is any documents on this yet... (not an issue yet)
just seems that you would want to be able to at least cache the connection
(socket) to the ejb server from tomcat. If someone knows right away the
answer it would be appreciated, otherwise I will try to look into this in
my jboss/tomcat experiments ;)
Kenneth Topp
On Wed, 16 Aug 2000, Rickard [iso-8859-1] �berg wrote:
> Hey
>
> Carlos Valiente wrote:
> > 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()
>
> Yup.
>
> /R
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
