Okay, now I understand your approach. So the company information is persisted prior to adding address info. Then the address info is persisted if added... So this becomes a little tricky due to the approach. The difficulty is determining where to end the conversation. If the user simply submits company information and we don't end the conversation (because they may want to add addresses) navigating away from the page would leave the conversation in memory even though the unit of work is complete. Your current approach is possible, but just wondering if it could be a little easier to manage :) Would it be possible to include the addresses as an optional part of the unit of work prior to persisting the data? For example, user inputs the company information. User can either submit (which persists company information and ends conversation) or click on the already visible address tab. If the user selects the tab the long-running conversation continues which maintains your state. Then on submit of the address information persist both company information and address information and end the conversation. That way you're sure the conversation is always ended appropriately once the unit of work is complete. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086868#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...