I've used conversation scope extensively in Seam 2.x apps with RichFaces modalPanel components (just search the Seam forums for proof!) It's usually not much special you must do for that combo other than refreshing data when users click action links/buttons if there are dataTables/forms embedded in the modalPanels.
1. What version of Weld and what version of RF are you using? I'm assuming Weld 1.0.0 and RF 4 or RF 3.x (if it's compatible with EE6/Weld?)
2. I find it almost amazing that you never used conversation scope in Seam before, that's one of the main benefits/features of using Seam along with business process scope for jBPM integration. For usecases involving multiple HTTP req/resp cycles (like a checkout wizard, etc.), LRCs are ideal. Also, SMPCs are tied to conversation scope so if you use SMPC and Hibernate manual flush you can avoid LIEs. In your situation in a Weld app, this feature may be unavailable/irrelevant as it most likely will be a feature of Seam3, a PE of CDI/Weld.
3. There are actually a couple ways to show a modalPanel. Check out the RF users forum for info or read Practical RF book.
4. post any exceptions/stack trace for any errors
5. In Weld, you must use begin() and end() methods to start and end a LRC, the @Begin and @End annotations will be available in Seam3.
it looks like the underlying issue is that you can't (or shouldn't?) be starting a conversation with something that's @Produces and is called from the UI. I added an empty method to the bean to fake it out and the modal pops up and everything's status quo again. i think.
John Ament wrote on Dec 06, 2009 16:15:
it looks like the underlying issue is that you can't (or shouldn't?) be starting a conversation with something that's @Produces and is called from the UI.
if this is true, why?