Thanks for the responses. Unfortunately, putting the DataModel into PAGE scope
doesn't change anything- selectedOrganization is still NULL in
selectOrganization().
I'm stuck in phase two (disillusion) of Gavin's
twocoasttb wrote : I don't see why this finder bean itself should require any
state. Am I wrong? It certainly shouldn't have to around in SESSION scope.
It needs some state - a stateless bean looses state between each invocation -
it is invoked update data model (i think?) to set the
Oops.
anonymous wrote : Don't ever set var=org in a dataTable. Doing so causes
Seam to go nuts searching contexts and it eventually throws an exception
because can't find a property called 'jboss' in the entity bean. Should I
report this as a bug? I'd be happy to provide a test case. Using
Ok. I understand why PAGE scope is appropriate, and recognize why it's the
right scope for my finder bean. A conversation isn't required until an item in
the list is selected for editing. A SFSB can't have PAGE scope (right?), so I
assume the DataModel should. So my finder bean now looks
declare the datamodel under PAGE scope.
@DataModel(scope=ScopeType.PAGE)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4008669#4008669
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4008669
