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 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 PROTECTED]]
> >Sent: Thursday, January 18, 2001 7:08 AM
> >To: Orion-Interest
> >Subject: JSP/Bean not reloading after re-deploy
> >
> >
> >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 JSPs and its bean classes withouth restarting the server. I
> >understand that the server should never be restarted, but I
> >can't seem to
> >get anything working without actually doing just that. I have
> >touched the
> >web.xml file before it is ear'd up to be deployed, but that
> >didn't work.
> >Does anyone have a solution to this problem? I must be missing
> >something
> >very simple.
> >
> >Thanks,
> >Ozzie Gurkan
> >
> >
>
