> -Original Message-
> From: Craig McClanahan [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 20, 2004 4:39 PM
> To: Struts Users Mailing List
> Subject: Re: OT: Best practice for access to file from
> multiple web apps
>
>
> On Tue, 20 Jul 2004 15:35:51 -0
> -Original Message-
> From: Craig McClanahan [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 20, 2004 4:39 PM
> To: Struts Users Mailing List
> Subject: Re: OT: Best practice for access to file from
> multiple web apps
>
>
> On Tue, 20 Jul 2004 15:35:51 -0
On Tue, 20 Jul 2004 15:35:51 -0700, Jim Barrows <[EMAIL PROTECTED]> wrote:
> We have PDF's that can be created by one webapp, but must also be served by other
> webapps.
Forgive me for coming in late, but it's not obvious to me how big a
problem the "other webapps" part of this really is. Lets
ED]
> > Sent: Tuesday, July 20, 2004 3:44 PM
> > To: Struts Users Mailing List
> > Subject: Re: OT: Best practice for access to file from
> > multiple web apps
> >
> >
> > Jim,
> >
> > do you use ANT or Maven to build/deploy your projects? if so
> -Original Message-
> From: Andrew Close [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 20, 2004 3:44 PM
> To: Struts Users Mailing List
> Subject: Re: OT: Best practice for access to file from
> multiple web apps
>
>
> Jim,
>
> do you use ANT or Ma
Jim,
do you use ANT or Maven to build/deploy your projects? if so you can
have them set up a config file for you based on the environment you're
building to.
andy
On Tue, 20 Jul 2004 15:35:51 -0700, Jim Barrows <[EMAIL PROTECTED]> wrote:
> We have PDF's that can be created by one webapp, but mu
We have PDF's that can be created by one webapp, but must also be served by other
webapps. Obviously, fun is ensuing in trying to figure out the best to avoid hard
coding paths, even in a configuration file. Dev, Test and Production are of course
different enought that each environment require
7 matches
Mail list logo
