Martin Marinschek wrote:
Yes - but the beans themselves are maintained fully on the server, as
far as I understood it - using request beans with saveState instances
and preserveDataModel doesn't make much sense with Seam, as far as I
saw through the Seam docu..
Sure, as Werner wrote the "conversation" state handles all we need - at
least i hope so, I am close before to jump to seam.
But - as far as i understand - even seam only works successfully if you
design your beans to always request database-data
using the entitymanager.
So the main advantage seam provides is to handle the
"(database)session-per-application-transaction"
in a sophisticated way.
Its still save, and I would say necesssary to use e.g. saveState when
you have to pass application-states (NOT pojo instances)
from one http-request to another. I mean values sort of "current", e.g
current order-number, current item-id, ...
Those values often have to live after a conversation ended, but putting
them in session scope is still too broad.
---
Mario
