[
https://issues.apache.org/jira/browse/DELTASPIKE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13829093#comment-13829093
]
Jason Porter commented on DELTASPIKE-445:
-----------------------------------------
I also prefer option number 2. There are only so many places you can look.
We're also setting them via the deltaspike configuration right? That's
extensible, so you can create your own extensions for reading / resolving
configurations and therefore make it expandable for where to find / set the
ProjectStage.
> read ProjectStage also from a few other places
> ----------------------------------------------
>
> Key: DELTASPIKE-445
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-445
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.5
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 0.6
>
>
> We currently only read the ProjectStage setting from
> "org.apache.deltaspike.ProjectStage".
> We should also try to read the info from the other ususal suspects:
> - javax.faces.PROJECT_STAGE
> - faces.PROJECT_STAGE
> We have 2 options to do so:
> 1.) introduce a SPI and make it expandable. But I honestly doubt this is
> worth the hassle.
> 2.) Just add the other locations and iterate through them directly in the
> ProjectStageProducer.
> I honestly prefer 2. Not as perfectly as clean, but way easier and usually
> this i snothing a user will change anyway.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
