-
1. Re: s:button action cannot resolve el expression
pmuir Oct 14, 2007 7:40 PM (in response to tynor)item isn't available when the jsf tree is recontructed in the restoreview phase. Try with h:commandLink (which causes the view to be reconstructed, and so the item variable should be available). Let us know whether that works :)
-
2. Re: s:button action cannot resolve el expression
tynor Oct 14, 2007 8:01 PM (in response to tynor)Thanks Pete. That gets me closer -- I now invoke the proper action on the backing bean.
I left out a bit of detail in my original query - and that detail is still causing probs. My backing bean has a "getHomeComponent()" function that does a Component.getComponent() on the proper EntityHome class - that's where my action method actually lives. The action method is being called on the a proper Home object, but h:commandButton is not interacting well with my page params, so the setFooFooId() function is never getting called - and I end up instantiating a new object with each action. Is there a way to get s:button style page parameter behavior with an h:commandButton?<h:commandButton value="Undelete" action="#{item.homeComponent.unmarkForDeletion}"> <f:param name="clientClientId" value="#{item.clientId}" /> </h:commandButton>
(Thanks again Pete - do you ever sleep?) -
3. Re: s:button action cannot resolve el expression
dhinojosa Oct 14, 2007 8:19 PM (in response to tynor)in jsf, <f:param> puts the parameter in the request, and doesn't (I believe) set the values to the component the way seam does in pages.xml.
There are a lot of ways to skin this cat though...but from what you are doing it looks like you will fare better with @DataModel @DataModelSelection solution. -
4. Re: s:button action cannot resolve el expression
tynor Oct 14, 2007 9:47 PM (in response to tynor)Thanks dhinojosa,
That pushed me in the right direction - I've refactored my code to use @DataModel/@DataModelSelection and all is working fine.
Thanks to both of you for your help.