Question

Am I right in thinking that this may not be the best idea:

private static Application app = FacesContext.getCurrentInstance()
        .getApplication();

… or any other call to FacesContext.getCurrentInstance() when you can’t be sure that the current thread of execution is due to a servlet request?

The way I understand it, FacesContext.getCurrentInstance() works by assigning the current faces context to the thread (e.g. ThreadLocal variable). The above will probably usually work in a class like a JSF backing bean or JSF component class, since the thread of execution that happens to load the class and instantiates the class members (static variables) is usually going to be a FacesServlet request. But I still don’t think it’s a good idea to count on it.

Agree or disagree? Ideas? Thanks.

Answer 1

Using FacesContext.getCurrentInstance() during initialization may or may not be a good idea depending upon the context.

I can’t imagine a scenario where assigning it to a static var would ever be a good idea, though.