However, regardless, after trying out 't:updateActionListener' I see why its cool. I have to rearchitect my app a bit, but it does make life quite a bit easier.
Thanks.
On 5/10/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
On 5/10/06, Kevin Galligan <[EMAIL PROTECTED]> wrote:
> I'm frustrated because I'm not doing a redirect, but it still just won't
> work. So, how would I set a top level managed bean with a value at the
> request scope without putting it into the session?
It is possible to do this programmically (I used to do it this way),
but it's far easier to use t:updateActionListener.
If you want to keep fighting it, you can take a look at
http://wiki.apache.org/myfaces/AccessingOneManagedBeanFromAnother
Option 1) context.getExternalContext().getRequestMap().put("testObject",
testObject) looks like the right track to me, so that'd probably the
path to pursue (Search MyFaces user list archives for postings on
managed beans and maps, probably written by Craig McClanahan.)
However, doing it like this is far easier:
<h:commandLink
value="Select Detail"
action="" do something">
<t:updateActionListener
property="#{testObject}"
value="#{currentRowObject}" />
</h:commandLink>
One thing that might be required is to add a layer of indirection:
<t:updateActionListener
property="#{someBean.testObject}"
value="#{currentRowObject}" />
