I'm looking for the best place to put application init stuff. I'm thinking
of something like the home directory of the file system to which the
application will write to. What's the best way of apssing such information
in. In the past I have used servlet api init params, but with all the
effort
]
To: user@struts.apache.org
Sent: Friday, November 09, 2007 12:41 PM
Subject: S2 best location of application init params
I'm looking for the best place to put application init stuff. I'm
thinking
of something like the home directory of the file system to which the
application will write
best location of application init params
I'm looking for the best place to put application init stuff. I'm
thinking
of something like the home directory of the file system to which the
application will write to. What's the best way of apssing such
information
in. In the past I have
-value
/init-param
M--
- Original Message -
From: tom` frost [EMAIL PROTECTED]
To: user@struts.apache.org
Sent: Friday, November 09, 2007 12:41 PM
Subject: S2 best location of application init params
I'm looking for the best place to put application init stuff
If you're using Spring (and if you're not, now might be the time to consider
it), I'd say make that a property of your application object that needs to
configuration. That is, using your example, say you've got a class,
TransactionLogger that needs the home directory of the file system to which
PROTECTED]
To: user@struts.apache.org
Sent: Friday, November 09, 2007 12:41 PM
Subject: S2 best location of application init
params
I'm looking for the best place to put
application init stuff. I'm
thinking
of something like the home directory of the
file system to which
6 matches
Mail list logo
