Hey, I had considered that, and part of my reluctance is the messyness involved in keeping a new subwidget informed of it's widget and vice versa. The subwidget has a property called Widget which refers to the owning widget. The Widget has a property called getSubWidgets which returns the list of subwidgets. The edit widget page is in a long running conversation, so I think the only way to start a separate conversation is by issuing a GET request and not use any conversation propagation, starting a new conversation using a link such as /editSubWidget?subWidgetId=123. You don't need to pass any parent widget information since you are editing an existing subWidget, and it already has a parent Widget. However, when you want to create a new subWidget, say by not sending in the subWidgetId, then you do need to provide a widgetId to indicate which widget is the parent, and you need to load that widget and use it with the new subWidget. By keeping everything in the same conversation, I can just reference the bijected widget variable to get the widget I am currently working on and will be the parent of my new subWidget. Additionally, if I create a new subWidget in a separate conversation, I then have to find a way to notify the original Widget instance that it has a new child. I could start getting into seam event handlers to do that but again, it starts getting messy. Neither are overly complex, but we are aiming to keep things simple due to really tight deadlines, and our inexperience with web development and seam. To add to the problems, we are trying to do it all using pageflows since the editing process can have multiple steps, which complicates matters as far as nested conversations go. I don't know, maybe we're looking for too simple a solution, does everyone else go through these kinds of hurdles in order to deliver web sites with seemingly logical editing navigation? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055785#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...