Problem with my FacesContext

[Yudiel Guerra]

Hi I have the following problem in my application, I am using a method called timer () and inside of the not recognize me the visual of the application ie the different components of the view that if they are in that moment .. Cheers and thanks beforehand

public void timer() {

System.out.println("Entro a TEMPORIZADOR");         
 ses = Executors.newScheduledThreadPool(1);

    // Ejecutar dentro de 4 segundos, repetir cada 3 segundos
    ses.scheduleAtFixedRate(this, 4 * 1000, 3 * 1000, TimeUnit.MILLISECONDS);

}

public void run() {

System.out.println("Entro a RUN");  

FacesContext fc = FacesContext.getCurrentInstance();
if(fc != null){
    UIComponent comp0 = fc.getViewRoot().findComponent("form_dashboard:id_office0");
    UIComponent comp1 = fc.getViewRoot().findComponent("form_dashboard:id_office1");
    UIComponent comp2 = fc.getViewRoot().findComponent("form_dashboard:id_office2");
    UIComponent comp3 = fc.getViewRoot().findComponent("form_dashboard:id_office3");
    UIComponent comp4 = fc.getViewRoot().findComponent("form_dashboard:id_office4");
    UIComponent comp5 = fc.getViewRoot().findComponent("form_dashboard:id_office5");
    UIComponent comp6 = fc.getViewRoot().findComponent("form_dashboard:id_office6");
    UIComponent comp7 = fc.getViewRoot().findComponent("form_dashboard:id_office7");
    UIComponent comp8 = fc.getViewRoot().findComponent("form_dashboard:id_office8");

}}

[Tim Holloway]

We've got a FAQ topic called "ItdoesntworkisUseless". Because truthfully, I don't know what your problem is.

Well, actually, I may, but it isn't the problem that you are thinking of.

J2EE request/response handling objects are forbidden by the J2EE spec from spawning threads. Anything that you do on a timer needs to be in a resource that isn't running under request/response processing. Which means that in particular, spawning a thread and/or waiting on a resource is not allowed in JSF backing beans or in code that they invoke.

Beyond that, a common beginner fault is being too swift to consider grabbing UIComponent objects and mucking around with them, JSF is designed to work primarily with POJO objects, so when you start touching stuff that's outside of the javax.faces model classes, it's usually an indication that you're doing it wrong.

Speaking of common beginner stuff, the FacesContext is something that's built by the FacesServlet to serve a single HTTP request/response processing cycle and immediately destroyed as soon as the response has been sent back. People who attempt to obtain and work with the FacesContext in a non-JSF context, such as a generic servlet or JSP are often frustrated to discover that what they get back is null, not a FacesContext.