relation between backing beans

[Manu dv]

I have form which takes user name and password and populates it into a backing 'LoginBean'

  
<h:form>
	<h:panelGrid border="1" columns="2">
		<h:outputText value="Name"></h:outputText>
		<h:inputText value="#{loginBean.name}"></h:inputText>
		<h:outputText value="Password"></h:outputText>
		<h:inputSecret value="{loginBean.password}"></h:inputSecret>
	</h:panelGrid>
	<h:commandButton value="Login" action="#{loginHandler.doAuthentication}"></h:commandButton>
	</h:form>
  

On press of button "Login" another class LoginHandler is supposed to do processing on the instance of LoginBean.
It has a property to accept the 'LoginBean' instance:

   public class LoginHandler {
	private LoginBean userInfo;

	public LoginBean getUserInfo() {return userInfo;}
	public void setUserInfo(LoginBean userInfo) {this.userInfo = userInfo;}
	public String doAuthentication()
	{//do some processing like authenticate(userInfo);}
}
 

How do I populate userInfo in LoginHandler class. Is it via <f:parm> tag in <h:commandButton> in the form or some other way?

soory if it is a noob question, I am just starting out with JSF.

[Shasi Mitra]

Hi - Is "loginBean" declared as managed bean in faces config? In that case, once you click login button, name and password values are populated in the bean.

[Manu dv]

Shasi Mitra wrote:Hi - Is "loginBean" declared as managed bean in faces config? In that case, once you click login button, name and password values are populated in the bean.

Yes, it is. And name & password were getting populated properly. I was not sure what was the standard way to retrive the instance of LoginBean from the session inside LoginHandler.doAuthentication().

I asked around and found that the way to do that is via FacesContext.getCurrentInstance().getExternalContext().
I tried this and it's working now.

   
public class LoginHandler {
	......
	public String doAuthentication(){
		if(userInfo==null)
		userInfo = (LoginBean) FacesContext.getCurrentInstance().getExternalContext().getSessionMap().get("loginBean");
                               //do some processing like authenticate(userInfo);}   

		}
}
 

[Shasi Mitra]

Use this instead

<managed-bean>
<managed-bean-name>loginHandler </managed-bean-name>
<managed-bean-class>com.LoginHandler</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>loginBean</property-name>
<value>#{loginBean}</value>
</managed-property>
</managed-bean>
<managed-bean>
<managed-bean-name>LoginBean</managed-bean-name>
<managed-bean-class>com.LoginBean</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
Now you put setter for loginbean in your loginhandler and you can access it..When the instance of loginhanlder is created, login bean is injected to the loginhandler.

[Manu dv]

thanks Sashi. <managed-property> is the kind of thing I was looking for.