Thanks Vivek, unfortunately that will not solve the problem.
I need whole screen object on next page, not url parameter only. I pasted simplified (next page) code to communicate requirement.
There must be a way in SEAM to propagate selected/clicked object to next page, I wonder if that has anything to do with its conversation scope.
Anybody to help please?
So now the screenList is in the bean we just made as a list of screens (you'll have to populate it)
When you select a screen from your list, the DatamodelSelection annotation makes it really easy for us, and will automatically map the screen you clicked to the screen in the bean. Now you have that bean in the conversation and you can do whatever you want with it, before you end the conversation.
Let me know if that helped...I am still new to Seam myself...
Joined: Jul 10, 2008
Thanks Ryan for your help. I tried similar code earlier, but was not able to make that work. I am sure it will work and I was missing something (I was using ScopeType.Conversation for Screen object, not for the SB used to populate screen objects).
But good thing is problem is solved now with a very small change. I am still using ScopeType.EVENT for Screen object. Only thing changed is view file. Instead of using h: outputLink tag I am now using s: link with view attribute. Earlier I had tried s: link with action element and I was confused as to how to provide a JSP/JSF file to action which was supposed to call a method. I was not paying attention to view attribute of s: link. See the code below, it works and gives me selected screen object on next page: