"asookazian" wrote : hmm. when the user selects another manager in the h:selectOneMenu, it's like they're started another session (similar to logging in as another user). So, then invalidate the session. anonymous wrote : the reason the injected NoteAction is session scoped is because it needs to handle all the note data that is entered in the main form dataTable (other SFSB) prior to submission (i.e. user may enter notes for multiple rows/employees prior to saving the first one). | | if the scope of the NoteAction was conversation I would not be able to meet the functional requirement UNLESS I forced the user to enter and save one row at a time by disabling all inactive rows... | | so if this is the case, i don't understand why the context/scope of the two SFSB's is incorrect.... I don't quite see why this means it must be Session scoped, only data/actions which should be used over the time the user has their browser should be session scoped. Anyway, this is application design, which you have to decide on ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115512#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...