Managed Bean Life cycle

[Ramaguru Ramasubbu]

Hi
Just wondering when does an object for the managed bean with session scope get created.
If I have 2 jsp pages and both of the uses the same bean(with session scope), does the constructor of the managed bean called twice?
For example I have a page which has 2 Frames. And the jsps of both the Frame refer to the diffrent properties of the same bean. How many times the constructor of the bean is called?
And How to get and set the current value of one bean's property from the other bean?

Thanks in advance
Ramaguru

[Gregg Bolinger]

If the managed bean is in session scope and both pages are referencing the same bean, the constructor only gets called once.

[Jeff Albertson]

As for the second half of your question, it's common to "inject" one bean into another in the config file:

<managed-bean> 
<managed-bean-name>apple</managed-bean-name>
<managed-bean-class>com.acme.Apple</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope> 
</managed-bean>
 
<managed-bean> 
<managed-bean-name>orange</managed-bean-name>
<managed-bean-class>com.acme.Orange</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope> 
<managed-property>
<property-name>amigo</property-name>
<property-class>com.acme.Apple</property-class>
<value>#{apple}</value>
</managed-property>
</managed-bean>

This is like writing:

orange.setAmigo(apple);

so in your Java code, the orange object is able to send messages to the apple object.