Ok, thanks everyone for the help. I will look into all suggestions.
Thanks,
Rich
On Mon, Sep 29, 2008 at 11:15 AM, Mikolaj Rydzewski <[EMAIL PROTECTED]> wrote:
> Richard Sayre wrote:
>>
>> I specify a JNDI resources (connection pool) and an Authentication
>> Realm. Each application authenticat
Richard Sayre wrote:
I specify a JNDI resources (connection pool) and an Authentication
Realm. Each application authenticates from a different database, and
has a seprate connetion pool there is a seprate database for each
app.
Define all environment specific details in server.xml (while dec
I specify a JNDI resources (connection pool) and an Authentication
Realm. Each application authenticates from a different database, and
has a seprate connetion pool there is a seprate database for each
app.
On Mon, Sep 29, 2008 at 10:43 AM, Mikolaj Rydzewski <[EMAIL PROTECTED]> wrote:
> Richard
Richard Sayre wrote:
I use ant. I am using Netbeans IDE for everything. Basically I
always have to change the context.xml and web.xml for every
environment that I set up. Everything else remains the same.
What kind of information do you pass through context.xml and web.xml?
JNDI resources?
I use ant. I am using Netbeans IDE for everything. Basically I
always have to change the context.xml and web.xml for every
environment that I set up. Everything else remains the same.
On Mon, Sep 29, 2008 at 9:46 AM, Mikolaj Rydzewski <[EMAIL PROTECTED]> wrote:
> Richard Sayre wrote:
>>
>> Are
Richard Sayre wrote:
Are there any tools that would help with building different .war files
for each context?
Do you build wars by hand or use Ant, Maven, etc?
--
Mikolaj Rydzewski <[EMAIL PROTECTED]>
-
To start a new topi
ANT should easily be able to do this. Then you should be able either use
either of
1) properties
2) target
To build one or more apps a time. If your shared code are versioned
well, maven might be a good fit too. (Since it has more dependency
handling methodology in place)
-Tim
Richard Sayre
What I mean is building a different WAR files, which has all the same
code, but different deployment descriptors.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional com
Are there any tools that would help with building different .war files
for each context?
On Mon, Sep 29, 2008 at 8:58 AM, Tim Funk <[EMAIL PROTECTED]> wrote:
> 1) Disk is cheap.
> 2) Build scripts can easily push the common code out to all your apps in a
> reproducable manner.
> 3) Seperate code m
Richard Sayre wrote:
> Is it possible to have several contexts pointing to the same code
> base? If I am hosing an application and other clients would like to
> use it, is it possible to set them up a seprate context that points to
> one set of JSP/Java Classes?
Yes. How, depends on your Tomcat ve
1) Disk is cheap.
2) Build scripts can easily push the common code out to all your apps in
a reproducable manner.
3) Seperate code makes regression upgrades easier to do since there is
always that one app which cant be upgraded
While you may be "sharing code" - all the code will be living in
Is it possible to have several contexts pointing to the same code
base? If I am hosing an application and other clients would like to
use it, is it possible to set them up a seprate context that points to
one set of JSP/Java Classes?
Are there disadvantages in doing this?
Thank you,
Rich
-
12 matches
Mail list logo
