Yeah, it might be. Will do.
----- Original Message -----
From: "elephantwalker" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Tuesday, April 17, 2001 1:37 AM
Subject: RE: remote deployment, how?
> Bill,
>
> This sounds like a bug. Could you log this in bug-zilla so Magnus et al
can
> get this one fixed? This seems to work for us.
>
> Regards,
>
> The Elephantwalker
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bill Winspur
> Sent: Tuesday, April 17, 2001 12:15 AM
> To: Orion-Interest
> Subject: Re: remote deployment, how?
>
>
> I dont like the underscore prefixing either, particularly in my
development
> environment.
>
> At present, on my development wkstation, I manually replace the ear file
in
> orion/applications while the server is running. This triggers auto-unpack
> and redeploy without underscore renaming. Previously, I used the -deploy
> option of the admin.jar utility which does result in underscore renaming.
>
> Slamming an ear into the running server like this does avoid renaming
> behavior, but I've found that it does not work on all our development
> wkstations, for reasons I have not nailed down. In some cases,
auto-unpack
> fails with a diagnostic like 'zip file format error', when the file is
> flawless. The work-around in that case is to stop the server replace the
> ear file in orion/applications and then startup the server.
>
> I intend to put the work around into our ant deployment script (let it
stop
> and startup orion) but have not done so yet. I've used admin.jar across
the
> network ok, so given a shared file system, this klunky approach should
work
> as a remote deployment technique for enterprise apps that does not result
in
> underscore renaming.
>
> For our initial production application, the *shutdown, replace ear,
startup*
> approach will probably be
> an acceptable protocol that fits into our weekly change-management
process.
> For subsequent, high availability applications we will probably be looking
> at another server for production, unless Orion has a more convenient
> hot-deploy capability by then.
>
>
> ----- Original Message -----
> From: "Koster, K.J." <[EMAIL PROTECTED]>
> To: "Orion-Interest" <[EMAIL PROTECTED]>
> Sent: Friday, April 13, 2001 2:14 PM
> Subject: remote deployment, how?
>
>
> > Dear All,
> >
> > I would like to be able to deploy an .ear remotely (the servers run
> FreeBSD,
> > some of the development workstations use Windows). I found that
admin.jar
> > can do this, and that the new application is indeed uploaded to the
> server.
> > It is not automatically deployed in place of the old one.
> >
> > What I do now (more or less) is this:
> >
> > java -jar admin.jar ormi://bladibla admin passwd \
> > -deploy -file doc.ear -deploymentName doc
> >
> > I see that the new file shows up in $ORION/applications, prefixed with
an
> > underscore. Repeatedly deploying the same file gives me lots of folders
> with
> > ever more underscores (_doc, __doc, ___doc, etc), but changes to .jsp
> files
> > in the .ear are not visible over the web.
> >
> > What I want to do is upload a new version of the application archive in
> > place of the old one, auto-deploying the thing. Question is: how do I do
> > that?
> >
> > Kees Jan
> >
> > ================================================
> > You are only young once,
> > but you can stay immature all your life.
> >
> >
> >
>
>
>
>
