myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gurkan Erdogdu (JIRA)" <...@myfaces.apache.org>
Subject [jira] Reopened: (MYFACES-3006) FacesContext current instance is null in managed bean action method for Tomcat 7
Date Wed, 12 Jan 2011 06:55:45 GMT

     [ https://issues.apache.org/jira/browse/MYFACES-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gurkan Erdogdu reopened MYFACES-3006:
-------------------------------------


Indicated above.

> FacesContext current instance is null in managed bean action method for Tomcat 7
> --------------------------------------------------------------------------------
>
>                 Key: MYFACES-3006
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3006
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.0.2
>            Reporter: Gurkan Erdogdu
>            Assignee: Leonardo Uribe
>
> Hello, 
> Actually I am not sure that this is an error related with MyFaces.
> In a managed bean action method, I have stopped an application "Tomcat Context"(not same
with the current JSF application).
> public String stopContext(){
>      
>      FacesContext.getCurrentInsatnce() --> It is ok, faces context is not null
>      Context context = get Tomcat application context;
>      //Stop tomcat context
>      context.stop();   --> This is any application on Tomcat, not same with current
JSF application
>      FacesContext.getCurrentInstance() --> Problem, it is NULL
> }
> I think that Tomcat clear current JSF application thread locals. But I ask to stop other
application context, therefore it must not destroy current application thread locals.
> What do you think?

-- 
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