Hi Jacob,
Seam's state-saving method is server-side, right? The conversation
will be stored on the server? Is that a persistent storage - in the
sense of a database, or a volatile storage - in the sense of a server
session (ok, I know, server side sessions can be persisted, too;) ?
option 1) So i
Yeah, that's correct, who says ViewState actually has to be your component
model? :-)
I've thought about progressing the stateless JSF solution to instead just write
Seam's converstation ID as the ViewState (a numeric long) to match up to model
state. This kind of solution makes a lot more sen
