lates/ hierarchy.
Voila! No more paths, except for relative, Java ones.
Tim
-Original Message-
From: Farrow, Marc [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 05, 2006 8:05 PM
To: Tomcat Users List
Subject: RE: System.setProperty/System.getProperty
Thanks. This is what I needed t
ubject: RE: System.setProperty/System.getProperty
P.S. For reference, here is an excellent how-to:
http://www.javaworld.com/javaworld/javaqa/2003-08/01-qa-0808-property.html
-Original Message-
From: Tim Lucia [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 05, 2006 7:42 PM
To: 'To
To: Tomcat Users List
Subject: RE: System.setProperty/System.getProperty
The differences are between testing environment and
production/semi-production environment between windows and other platforms.
We store templates, etc in a certain folder and have to read them. However
the "path"
Subject: RE: System.setProperty/System.getProperty
The differences are between testing environment and
production/semi-production environment between windows and other platforms.
We store templates, etc in a certain folder and have to read them. However
the "path" is different between
ednesday, April 05, 2006 7:03 PM
To: [EMAIL PROTECTED] Apache. Org (E-mail)
Subject: System.setProperty/System.getProperty
Is there an easy way within Tomcat to set System properties so that all
webapps have access to them at startup? Basically, I would like to add my
own properties to the System ob
EMAIL PROTECTED] Apache. Org (E-mail)
Subject: System.setProperty/System.getProperty
Is there an easy way within Tomcat to set System properties so that all
webapps have access to them at startup? Basically, I would like to add my
own properties to the System object at startup as opposed to
Is there an easy way within Tomcat to set System properties so that all
webapps have access to them at startup? Basically, I would like to add my
own properties to the System object at startup as opposed to using
environment entries. Maybe I am over thinking things. Or better yet, what
is the be
