Hi all,

I've got a question about seam regarding the use of nested conversations and 
more specifically, how I can pass data between nested conversations. To 
explain, consider the following hypothetical use case of a banking application:

I have a generic "web-component" (i.e. set of classes, faces-config.xml, JSP's, 
etc), which can be used to search for clients or create new clients. This 
component is used from a number of different locations, like creating new 
accounts (adding owners of the account), or requesting a loan.

I'm not an expert in seam, but from what I've seen (and tested), the pageflow 
to this component can be handled using jPDL (subprocess tag). Using nested 
conversations, each of these components can have their own scope for data.

The problem I'm thinking about is how to pass data between these two 
conversation scopes (i.e. from the account scope to the client scope when the 
client component is called and the other way around to pass the selected client 
back to the account component). 

I know child-scopes can access their parent scope (in a read-only fashion), 
however I'd like the client-component in this case to be agnostic of the 
calling component. Is there some generic best-practice in Seam how to handle 
this case?

Thanks for your thoughts,

Jeroen

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072339#4072339

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072339
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to