[
https://issues.apache.org/jira/browse/DELTASPIKE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141768#comment-14141768
]
Mark Struberg commented on DELTASPIKE-728:
------------------------------------------
The rational behind this is that web.xml is a really bad place to store
non-static config.
Anything which is installation specific (like the ProjectStage, db settings,
etc) must not be configured in web.xml imo. Simply because you cannot change
those values without repackaging.
There are some servers which allow filtering for such files like beans.xml and
web.xml but then you end up being highly non-portable as all those mechanisms
work different dependent on the vendor - if it works at all.
Please also note that MyFaces also looks up the ProjectStage from System env
and settings, but Mojarra sadly doesn't do that.
> ProjectStage doesn't take care of javax.faces.PROJECT_STAGE context param
> -------------------------------------------------------------------------
>
> Key: DELTASPIKE-728
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-728
> Project: DeltaSpike
> Issue Type: Bug
> Components: Core, JSF-Module
> Affects Versions: 1.0.2
> Reporter: Thomas Andraschko
> Assignee: Mark Struberg
> Priority: Trivial
>
> In all my projects i have a web.xml with ProjectStage Production and i have a
> overwrite web.xml (via jetty-maven-plugin) to overwrite the ProjectStage to
> Development.
> I also overwrite some other params and servlet mappings.
> Therefore setting the ProjectStage again via
> --Dfaces.PROJECT_STAGE=Development
> is just a really annoying overhead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
