Hi Marcel,

You're right, I had already tried that and it didn't work. On the other
hand, I tried to pack my .war inside a .ear and everything worked. Of
course that adds another directory and another file to be created but
it's something I can cope with ;). Touching the application.xml file
works fine but I was hoping that auto-detection of new .war files would
be as easy as .ear files, that way a simple ftp with the new war file is
enough but that's not a problem.

Another question, when I perform a hot deployment, all the sessions are
lost. Is there any way I can keep the sessions alive? I mean is there
any setting to persist the sessions across deployments?

Thank you for your help,
Dan
-------------------------------------------
Daniel Lopez Janariz ([EMAIL PROTECTED])
Web Services
Computer Center
Balearic Islands University
-------------------------------------------


Marcel Schutte wrote:
> 
> I'm having the same problem as Daniel. It's not a matter of touching or
> recreating the .war. Daniel wrote that he tried that already.
> 
> For me, the automatic redeployment of .ear files works fine. Whenever I
> overwrite the .ear file, orion starts redeploying right away. However, when
> I make my .war part of the global-application by editing the following line
> in <orion>/config/application.xml:
> 
>         <web-module id="defaultWebApp" path="../default-web-app" />
> 
> orion doesn't redeploy my web application when I overwrite the .war.
> Instead, I have to restart the server for it to pick up the changes.
> 
> ....<several minutes later>....
> 
> Just occurred to me that perhaps touching the file
> <orion>/config/application.xml would trigger redeployment. And indeed it
> does, problem solved.
> 
> Marcel
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Mike
> > Cannon-Brookes
> > Sent: Thursday, March 29, 2001 4:02 PM
> > To: Orion-Interest
> > Subject: RE: Hot deployment
> >
> >
> > Touch the .war file or recreate it - Orion will detect that
> > and redeploy it.
> > If not, check your date settings etc. Sometimes one machine (if you're
> > deploying across a network) may have a different clock to another.
> >
> > -mike
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of
> > Daniel Lopez
> > > Sent: Thursday, March 29, 2001 8:22 PM
> > > To: Orion-Interest
> > > Subject: Hot deployment
> > >
> > >
> > > Hi,
> > >
> > > I've been using Orion for a while and so far, so good. Now
> > I'm trying to
> > > improve the way we develop/deply applications and I started
> > to digg in
> > > the .war file world. I've created the war file containing
> > just the web
> > > application and it's been auto-unpacked and auto-deployed
> > succesfully,
> > > great! Now I wanted to check what are the steps that I need
> > to follow in
> > > order to deploy a new version of an application. Re-creating the war
> > > file and substituting it seems not to affect Orion and it's not
> > > detecting a new version. I even tried to remove the
> > deployed application
> > > directory to see if it would re-unpack it from the new war
> > file but it
> > > didn't work either. So, what am I missing? Do I need to
> > create the full
> > > .ear file blah, blah so hot-deployment works? As I don't
> > use EJB, I was
> > > thinking about just using a plain .war file with just the web
> > > application. Is that the problem?
> > > Thank you very much in advance,
> > > regards
> > > Dan

Reply via email to