Then yes, make the entire Employees conversational - you want to make the link
not propagate the conversation, then add a <begin-conversation /> element to
the page definition in pages.xml. You might consider a nested conversation for
editing an employee along with manual flush mode to make that atomic. You
don't need to end the conversation - it can either timeout OR you can specify
*which* conversation to join when you click the link and make it so when
Employees are clicked you go back to the same conversation (workspace). To do
this you need to specify the conversation id (unique across the app, perhaps
Employees-). Or you can use natural conversations in Seam2.
<conversation name="EditEmployee"
| parameter-name="employeeId"
| parameter-value="#{employee.id}"/>
|
| <page conversation="EditEmployee" />
is a natural conversation - so less wiring than manually specifying ids (but
still the same thing under the bonnet).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085463#4085463
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085463
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
