[
https://issues.apache.org/jira/browse/DELTASPIKE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-1096:
-----------------------------------------
Description:
the project-stage configured for ds should be used for jsf as well.
in case of a *custom* test-stage the jsf-project-stage should be Development
and in case of a custom project-stage which isn't a test-stage or in case of
project-stage Production the jsf default handling should be used.
e.g.:
ds-ps dev + no jsf-ps (default/prod.) - the result for jsf is dev
ds-ps custom-test-stage + no jsf-ps (default/prod.) - the result for jsf is dev
ds-ps default or prod. (= no config) + no jsf-ps (default/prod.) the result for
jsf is prod
ds-ps default or prod. (= no config) + jsf-ps e.g. dev - the result for jsf is
dev
ds-ps e.g. UnitTest + jsf-ps e.g. dev - the result for jsf is UnitTest (= issue
in the config which can be fixed by users - to avoid a runtime-overhead we use
the value from ds since ds also checks the jndi config for jsf and values like
UnitTest shouldn't be configured via web.xml)
was:
the project-stage configured for ds should be used for jsf as well.
in case of a *custom* test-stage the jsf-project-stage should be Development
and in case of a custom project-stage which isn't a test-stage or in case of
project-stage Production the jsf default handling should be used.
> project-stage bridge for jsf
> ----------------------------
>
> Key: DELTASPIKE-1096
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1096
> Project: DeltaSpike
> Issue Type: New Feature
> Components: JSF-Module, JSF22-Module
> Affects Versions: 1.5.4
> Reporter: Gerhard Petracek
> Assignee: Gerhard Petracek
> Fix For: 1.6.0
>
>
> the project-stage configured for ds should be used for jsf as well.
> in case of a *custom* test-stage the jsf-project-stage should be Development
> and in case of a custom project-stage which isn't a test-stage or in case of
> project-stage Production the jsf default handling should be used.
> e.g.:
> ds-ps dev + no jsf-ps (default/prod.) - the result for jsf is dev
> ds-ps custom-test-stage + no jsf-ps (default/prod.) - the result for jsf is
> dev
> ds-ps default or prod. (= no config) + no jsf-ps (default/prod.) the result
> for jsf is prod
> ds-ps default or prod. (= no config) + jsf-ps e.g. dev - the result for jsf
> is dev
> ds-ps e.g. UnitTest + jsf-ps e.g. dev - the result for jsf is UnitTest (=
> issue in the config which can be fixed by users - to avoid a runtime-overhead
> we use the value from ds since ds also checks the jndi config for jsf and
> values like UnitTest shouldn't be configured via web.xml)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
