[
https://issues.apache.org/jira/browse/FC-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514385#comment-14514385
]
Shawn McKinney commented on FC-96:
----------------------------------
One option is to use tomcat context.xml to contain the params (per Stefan on
dev list):
In the context.xml you can then add arbitrary name/value pairs which can
be read by ServletContext.getInitParameter():
<Context>
<Parameter name="..." value="..." />
</Context>
and Kiran has recommended using env variables:
use FORTRESS_HOME or FORTRESS_CONF env variable and read the config from that
location. If this variable is not set then the default config can be extracted
and used.
so here is the overall strategy:
1. read first from env variable
2. if that isn’t set, read from servlet context.xml
3. finally read from the fortress.properties if other two not set.
> Externalize fortress web.war config
> -----------------------------------
>
> Key: FC-96
> URL: https://issues.apache.org/jira/browse/FC-96
> Project: FORTRESS
> Issue Type: Improvement
> Affects Versions: 1.0.0-RC40
> Reporter: Shawn McKinney
> Fix For: 1.0.0-RC41
>
>
> Currently the fortress-web.war contains a configuration artifact,
> fortress.properties, which contains the coordinates for directory or rest
> server. These props need to be settable without breaking apart the war and
> editing the file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
