myfaces-dev mailing list archives

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


Leonardo Uribe commented on MYFACES-2730:

MYFACES-2730-2.patch has an alternative I'm working on. In theory StartupFacesContextImpl
must implement as many features as possible to prevent exceptions. For example, if getResponseWriter()
is called, return a "dummy" one and so on.

 I think we can use the original ServletExternalContextImpl and use _SystemEventServletRequest
and _SystemEventServletResponse as request and response objects, instead a new instance. The
new instance has the advantage that we can throw description exceptions, but it has the disavantage
of make maintain more difficult, because in future versions we should update it too.

> 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: Leonardo Uribe
>             Fix For: 2.0.2-SNAPSHOT
>         Attachments: MYFACES-2730-1.patch, MYFACES-2730-2.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.

View raw message