We started our project a while ago, but Seam is only a recent addition to our toolset.
I have a hard time figuring out how to implement conversations, so that the extended persistence context as well as multiple browser windows and backbutton works.
In general my impression is that to make use of conversations you must have conversations in mind right from the start when you design the user interface of your app. However there's no way we can make fundamental changes to the UI at this stage of the project.
Is there any way to implement conversations correctly with this basic style of UI:
Menu-Links: Employees | Clients | Projects | ... ------------------------------------------------ List Selected Project Details ---- ------------------------ Project A | Project B | Name: _______ Project C | Lead: _______(Employee Dropdown) Go-> (Link to selected employee's details) Project D | ... Project E | Save-Button New-Button
Anybody?
Is it in general a bad idea to use a form to view (and only possibly edit) data?
Can I start a conversation with an "edit" button that uses ajax to simply switch all fields from disabled to editable and starts a conversation remotely?