myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <...@myfaces.apache.org>
Subject [jira] Commented: (EXTCDI-18) Provide ProjectStage determination mechanisms also for non-JSF environments like unit tests
Date Thu, 01 Apr 2010 10:50:27 GMT

    [ https://issues.apache.org/jira/browse/EXTCDI-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852324#action_12852324
] 

Mark Struberg commented on EXTCDI-18:
-------------------------------------

I've now committed a basic backend version.

I'll later work on:

* a JSF-1.2 version which additionally checks the web.xml to mimic JSF-2 behaviour

* a JSF-2 version which first asks the Application.getProjectStage() and converts those javax.faces
ProjectStages into our CODI ProjectStages if something other than ProjectStage.Production
has been found.

> Provide ProjectStage determination mechanisms also for non-JSF environments like unit
tests
> -------------------------------------------------------------------------------------------
>
>                 Key: EXTCDI-18
>                 URL: https://issues.apache.org/jira/browse/EXTCDI-18
>             Project: MyFaces CODI
>          Issue Type: New Feature
>            Reporter: Mark Struberg
>
> We need a centralised but extendible mechanism to properly detect ProjectStages and provide
both, programmatic detection and @Produces for it.
> The programmatic detection is necessary for writing plugins which need to know the actual
ProjectStage at a point in time where the CDI startup process has not yet finished.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message