myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <>
Subject [jira] Reopened: (MYFACES-2730) FacesContext not available on application startup
Date Tue, 22 Jun 2010 02:20:01 GMT


Leonardo Uribe reopened MYFACES-2730:

I have to revert this patch because it is causing another problems (see MYFACES-2766). MyFacesServlet
was not updated too, so it is necessary to work more on this issue. 

It is a very bad idea delete classes on myfaces core, or in any project in general, even if
they are not used. One example is myfaces 1.2.x portlet stuff. Those classes does not work,
because that was replaced by portlet bridge project, but to prevent break the code and lose
the svn history of those classes, we just removed when 2.0.x branch was created.

When _SystemEventServletRequest and _SystemEventServletResponse classes were deleted, we lost
all svn history about them (we have to look at 2.0.0 branch to see that).

In issues that requires some change/replace on already stable functionality, it is better
to create patches and do not commit at all, so other people can take a look at the proposed
solution and comment about it.

> FacesContext not available on application startup
> -------------------------------------------------
>                 Key: MYFACES-2730
>                 URL:
>             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: Jakob Korherr
>             Fix For: 2.0.2-SNAPSHOT
> 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.

View raw message