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..
>
> regards,
>
> Martin
>
Same impression here, the scoping is done via ejb session beans, seam
introduces a new scope (conversation)
the usage of savestate does not make any sense once you have moved to seam
the conversation scope does everything for you in that regards, as far as
I understood the docs.
