You said it in the last sentence. I gave that a shot yesterday and vouila!
I got it working. I don't like using the "admin.jar" way anymore. It seems
to create new directories for each deployment...ughh!
Thanks,
Ozzie Gurkan
--- Jeff Schnitzer <[EMAIL PROTECTED]> wrote:
> Just a thought, but hav
- Original Message -
From: "Jeff Schnitzer" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Friday, January 19, 2001 7:44 AM
Subject: RE: JSP/Bean not reloading after re-deploy
> Just a thought, but have you checked the syst
Just a thought, but have you checked the system clocks on the various
machines involved? Maybe the timestamps are fouled.
"reloading" of JSPs works fine for me; my deployment process just copies
the new .ear over the old one.
Jeff
>-Original Message-
>From: Ozzie Gurkan [mailto:[EMAIL
Actually, I am not getting any errors. I am deploying an 'ear' file using
admin.jar commands and everything works fine. However, it seems like the
server still wants to hang on to its memory copy of the JSPs and not
recompile the deployed ones. When I restart the server, everything is fine.
Ozzie
I am using ant also to do the ear and deploy using the admin.jar commands.
I get the appropriate messages from the console but my JSPs are still not
picked up by the server. I hit reload and nothing...until I restart the
server.
Ozzie
--- Thomas Pridham <[EMAIL PROTECTED]> wrote:
> Not sure if t
What is the error? I get a LinkageError when I update my WAR file without
restarting the server.
-Dan
Ozzie Gurkan wrote:
> I have searched through all of orion-interest list and still have not found
> a solution that works for me. I am talking about the "reload" problem with
> changing of JSP
Not sure if this helps...we are using ant do builds with and each time we
build / deploy, Orion deploys the new files without failure. It appears to
me that Orion is triggering a re-deploy based on the timestamp of the ear
file changing. However, I don't think this on-the-fly deployment is a goo
