Arash Rajaeeyan schrieb: > and may be thats because shale has chosen a different approach? > No... Actually I think the fusion conversation system is one level lower than shale dialog. While shale dialog basically follows the approach -> configuration of dialog scopes, have something which can keep objects in ram during the dialog.
the fusion conversation system is along the lines of: providing a programmatic accessible scope mechanism based on spring 2.0s basic scope control which also is able to handle orm entity manager control, no dialog configuration whatsoever (except for a spring bean entry). Nothing speaks against accessing this programmatic control from a configuration based dialog system, and only a few things currently prevent it from being accessible from other webframeworks outside of the jsf scope. But as Mario said, who knows what the future will bring.
