Dynamic bean call in JSF - is it possible?

Question

Is there a way to make a method call on a backing bean that is only known at runtime?
For example, in the code below:
<h:commandButton value="Click" action="#{bean.foo}" />
public class Bean
    public String foo()
        // Execute action
        return "navigation";
}the call to bean in +<h:commandButton>+ is static. But what if I only know which
backing bean I'll call at runtime? I would like something like this:
<h:commandButton value="Click" action="#{(systemBean.beanName).foo}" />
public class SystemBean
    public String getBeanName()
        if (some test)
            return "bean1";
        else
            return "bean2";
}Is there a way to do this or a workaround?
Thank you.
Marcos

Answer 1

Marcos_AntonioPS wrote:
It's the case for bookmarked URLs Take a look for PrettyFaces.
and a way to let the application developer
do an action when a page loads and to know if it is a postback or not. If it had this
last feature I wouldn't be with the problem that I am now. In ASP.NET the Page class
(which all other pages derive) has the OnLoad method which is called everytime your
page loads. In Java you have the constructor for that. Or if initialization is to be done after setting the managed properties, then use a method annotated with @PostConstruct.
There you can check the IsPostBack property to find if it is a postback
or not.You can use ResponseStateManager#isPostBack() for that.
My problem is that I have to navigate to other page but at the same time execute an
action (call a method) in the page that I'm going to. The first problem (navigate) is
simple to solve, but not the second.As said: use the constructor or @PostConstruct.
This is my situation: I have a +<h:selectOneMenu>+ in a page with many options. The user
will select an option and click on a button. The action property of the button points
to a method. In the method I'll check what the option was and return a String to the
next page. So the navigation problem is solved. But I also need to call a method in the
backing bean related to the page that will be called for the page to reset its values
to start to collect new data from the user.I don´t fully get the picture, but this at least sounds like that the bean is been put in the session scope instead of the request scope.
JSF doesn´t make things complicated. Your way of thinking and designing is complicated.