Thanks for the answers. I have to think a little more about wether page or
maybe conversation scope would work in my case.
Gavin, you're proposal makes sense. However it would save me some work if the
code that wraps a collection in a ListDataModel would be made public.
Why should I duplicate
huh? the code is: new ListDataModel(myList)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3946909#3946909
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3946909
---
All
*ashamed*
See, I only started with JSF for about a couple of hours when I realized that I
am missing the funcionality that Seam offers.
Now you made the clickable list tutorial sound so nice and easy that I thought
it would be much more complicated with pure JSF.
Should have read some more.
Now
No problem ;-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3946973#3946973
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3946973
---
All the advantages of Linux
You can always do it in the standard JSF way, and create a ListDataModel that
you keep inside your component.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3946308#3946308
Reply to the post :
Surely something like
| @Stateless
| @Name(employeeManager)
| public class EmployeeManagerBean implements EmployeeManager {
|
|@DataModel(scope=PAGE)
|private ListEmployee employees;
|
|@In(required=false)
|private Boolean internal;
|
|
