What are the implications of creating a custom managed bean scope?
In our case, we have the following requirements:
1. Our model is hierarchical and upto 10 levels deep. (i.e model object size
is big)
2. Need to associate state to an use case. A use case includes multiple
screens that populate
Adusumilli [EMAIL PROTECTED]
11.04.2007 17:19
Please respond to
MyFaces Discussion users@myfaces.apache.org
To
MyFaces Discussion users@myfaces.apache.org
cc
Subject
Custom Managed Bean scope
What are the implications of creating a custom managed bean scope?
In our case, we have
Hi!
What other ways such a problem can be handled?
You can use JBoss Seam or Apache MyFaces Orchestra (which is the
successor of the MyFaces conversation tag).
JBoss Seam is a rather full blown thing which can do much more
please refer to their homepage for further informations.
Orchestra
Hi Mario,
Does Orchestra require you to use Spring?
Many thanks,
Fintan
-Original Message-
From: Mario Ivankovits [mailto:[EMAIL PROTECTED]
Sent: 11 April 2007 14:44
To: MyFaces Discussion
Subject: Re: Custom Managed Bean scope
Hi!
What other ways such a problem can be handled
Hi Conway!
Does Orchestra require you to use Spring?
Yes, parts of it.
Some reasons are:
*) Defined way to create a custom scope, means, in your spring config
you can configure your beans with 'scope=conversation'
*) Aspects. They are used to solve the ORM stuff and use cases where
e.g.
Hi Conway!
Uhm .. sorry, should have been Hi Fintan!
Hi Ivan, 8^)
Do not worry, you are not the first person to do this, and probably will
not be the last :-)
-Original Message-
From: Mario Ivankovits [mailto:[EMAIL PROTECTED]
Sent: 11 April 2007 15:30
To: MyFaces Discussion
Subject: Re: Custom Managed Bean scope
Hi Conway!
Uhm
7 matches
Mail list logo