JBossDeveloper

Thanks Chris, I am going through your example now. Just one thing, you have a MySQL datasource defined in persistence.xml You should change this to Hypersonic for the example so it will run "out of the box". Just requires a change to DefaultDS as the JNDI name of the datasource in persistence.xml.

Ok I finally have this working. I think it had to do with not having my tags enclosed in a trh:body element which is required to get PPR working. I thought a tr:document would suffice but I guess not?

Also I have done some limited testing with the Phase Listener/Action Listener provided by earlier in the thread. I don't think these are necessary to get Dialogs working in the most basic sense. If all you need to pop up the window and return a value, a new short-lived conversation will be created by Seam. This is fine since the dialog should not need to know anything about the conversation you came from. This may not be true for other Use Cases where you need to pass a value to the dialog.

I still can't find a way to propagate the conversation to the dialog window. I have tried the above mentioned Phase Listener and also the s:conversationPropagation tag in Seam's Library. Neither seem to work.

I would love to hear other ideas on the subject.

Thanks to both Chris and dajevtic for your help on this.

Chris, I have followed your instructions and am not seeing the conversation propagated.

1st page has a conversation id (cid) of 1
2nd page (long running conversation) cid=2
3rd page(page with dialog link) cid=2
dialog page cid=4

I have not changed anything in your project other than the DataSource reference in persistence.xml

Maybe something in Seam 1.3. Probably need to use the trinidad-seam extension that the JBoss guys are creating with some added "glue" to get the conversation to propagate correctly across dialogs. Hopefully with this ground work they can think of something a little more elegant than this quick hack.

Please check in my provided listeners, if you are using "conversationId" paramter name od "cid" parameter name...

which is correct? coversationId or cid?

The one that is configured in your components.xml.
In your case probably "cid" ?!

Ok thanks. It was consistent between components.xml and the phase listener.

Can one of you create a JIRA issue for me? I need to know what the exact problem you are encountering is (and how I can replicate), and what you are doing to solve it and the relevant classes. Then I can roll it into the jboss-seam-trinidad.jar and seamdiscs example. Thanks!

I have created the jira, Chris or dajevtic, feel free to add anything I may have left out.

http://jira.jboss.com/jira/browse/JBSEAM-1289

Hi,

As of last week Seam 2.0 has become productive. Has the situation changed in any way?

What I noticed is that the original way of propagation of this hack is not possible anymore with Seam 2.0 because the line

Manager.instance().restoreConversation(createParameterMapForConversationRestore(convId));

is not possible anymore due to changes of the Seam API.

So if at least we could save this hack and have Seam 2.0 running with Trinidad with this respect, the next question is which Seam method to use instead of above line. Any ideas?

Thanks,
Wolfgang.

No. I've scheduled the issue however.

Try replacing the line with

ConversationPropagation.instance().setConversatonId(convId);
Manager.instance().restoreConversation();