enhanzo : I think the problem there is that the information has to cross the conversation boundary. The bean receiving the param needs to exist in the next page's conversation, and the entity containing the param exists only in the previous conversation which we probably just ended and is therefore no longer available. Gavin : Interesting suggestion, having a quick look through the source code for the redirect component, it looks like it might work. My only problem is that again, it's a question of spanning conversation boundaries, and being on the right view when I capture it. I usually start conversations in pages.xml so it seems impossible for the redirect component to be in the right conversation when I capture the view since the conversation is only started on the first page of the pageflow. If I do it it on the old view, the one I want to capture, then the new conversation hasn't started so the redirect component will not be in the new conversation. @Begin annotations don't help since the conversation only begins after it has executed, so while it may capture the right view, it will be in the wrong conversation. In general, regarding the issue of conversation boundaries and passing information across those boundaries, I've found the only practical and effective way is to use parameters to pass Ids around. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058325#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...