[
https://issues.apache.org/jira/browse/MYFACES-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881629#action_12881629
]
Martin Marinschek commented on MYFACES-2730:
--------------------------------------------
Hi guys,
if there is backwards compatibility issues - e.g. an existing version of
Orchestra which runs on MyFaces 1.2 does not run on MyFaces 2.0 due to throwing
an exception, or any libraries which don't deploy but would be deploying if we
don't throw exceptions, I change my position. I also think that resolving EL
expressions should also be possible on startup (just not in request and session
scoped beans).
However, I thought the FacesContext was not available on startup so far, so why
do existing libraries rely on this behaviour?
If this is necessary - I am in favor to log an error instead.
best regards,
Martin
> FacesContext not available on application startup
> -------------------------------------------------
>
> Key: MYFACES-2730
> URL: https://issues.apache.org/jira/browse/MYFACES-2730
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-127, JSR-252, JSR-314
> Affects Versions: 1.1.8, 1.2.9, 2.0.0
> Reporter: Nick Belaevski
> Assignee: Leonardo Uribe
> Fix For: 2.0.2-SNAPSHOT
>
> Attachments: MYFACES-2730-1.patch, MYFACES-2730-2.patch,
> MYFACES-2730-3.patch, MYFACES-2730-revert.patch
>
>
> If custom ResourceHandler calls FacesContext.getCurrentInstance() in
> constructor to read init parameters, null value is returned. This affects
> latest MyFaces 2.0.0-SNAPSHOT. Mojarra 2.0 provides InitFacesContext in this
> case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
