I am trying to create a master-detail screen scenario and am following the best-practices guide in the wiki (the simple CRUD cycle - http://wiki.apache.org/myfaces/A_simple_Crud_Cycle) and it does not actually work. Am I doing something wrong? Here is what I have:
MasterView has a BO which it uses to fetch a list of all target objects (just like in the example). DetailView is in its own detail related flash conversation (as mentioned in the bottom of the example), and has a reference to the BO as well. (manual/flash makes no difference whatsoever) When I do a save on the DetailView, if I call refreshList on the MasterView after saving using the DetailView "instance" of the BO, the list does NOT contain my changes. I understand why this is happening. The BO in the MasterView has its own entity manager as it is in a different conversation than the DetailView. It does not help to do Conversation.getCurrentInstance().invalidate() in the DetailView before doing a list refresh on the master view as there is still nothing to force the entity manager in the MasterView to dump its cached objects. The example is quite unclear on many details and was wondering if I am doing something wrong here. I have found several ways to make it work as expected, but they are NOT like the example, and are a bit more difficult to figure out as to what is going on without documentation. My test is extremely simple and is NOT working as advertised! Can anyone help? -- View this message in context: http://www.nabble.com/-orchestra--Conversation-issues-with-master-detail-tf4894353.html#a14017094 Sent from the My Faces - Dev mailing list archive at Nabble.com.
