Right. Mostly, My interface is well defined. We have a B2B Transaction
server that has one method in its interface:
String processXML( String xmlDoc )
It takes an XML document and returns an XML document. I only change the
underlying behavior, but the effects don't happen unless I stop and restart
Jboss. Its like it has a memory of it, even though it has been undeployed
and redeployed automatically, which is way cool.
Wes
-----Original Message-----
From: Rickard �berg [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 16, 2000 2:22 PM
To: jBoss
Subject: Re: [jBoss-User] Auto Deploy
Hi!
Wes Mckean wrote:
>
> 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.
BTW, are you changing interface or implementation? Impl. should be cool,
but interface will be troublesome unless you reload the interface class
in Tomcat somehow (redeploy?)
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
