yes it is general problem, I tried with other beans that had request scope
and got the same problem
On Fri, 03 Oct 2008 13:11:45 -0400, Guy Bashan <[EMAIL PROTECTED]>
wrote:
Did you try another bean test? Does this behavior happens in this
specific bean, or is this a general problem?
Sent from my iPhone
On Oct 3, 2008, at 6:52 PM, "Alex Diaz" <[EMAIL PROTECTED]> wrote:
I am just using the the managed-bean like:
<managed-bean>
<managed-bean-name>ChangeTreeValueHelper</managed-bean-name>
<managed-bean-class>beans.ChangeTreeValueHelper</managed-bean-
class>
<managed-bean-scope>request</managed-bean-scope>
</managed-bean>
On Fri, 03 Oct 2008 11:39:44 -0400, Andrew Robinson
<[EMAIL PROTECTED]> wrote:
Are you by any chance using t:saveState or something else to pin the
object in memory like using managed-property?
On Thu, Oct 2, 2008 at 7:37 PM, Alex Diaz <[EMAIL PROTECTED]> wrote:
Yes my managed bean is in the faces-config.xml and the scope y set to
request. but still have de same problem.
Thanks
On Thu, 02 Oct 2008 09:45:04 -0400, Guy Bashan <[EMAIL PROTECTED]>
wrote:
Beans in request scope are recreated on each request.
Make sure:
1) Your bean is in the faces-config.xml.
2) The scope is really "request".
Guy
-----Original Message-----
From: Alex Diaz [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 02, 2008 4:47 PM
To: users@myfaces.apache.org
Subject: managed bean with request scope
Are the managed beans with request scope destroyed after each
request to a
page? If so, then why the beans constructor is not being called after
subsequent requests?
Thanks.
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
--Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
