>>>While hacking the @ViewScoped Good, but I wish you try to hack OWB to complete specification implementation and pass TCK. :) I think , otherwise, we are loosing our road map.
For other issue, Serialization is related with instance of bean instance not the bean itself. what do you mean by "session security?" --Gurkan 2010/2/2 Mark Struberg <[email protected]> > sorry, meant Contextual have to be serializable (in most cases), not the > Context objects itself. > > LieGrue, > strub > > --- On Tue, 2/2/10, Mark Struberg <[email protected]> wrote: > > > From: Mark Struberg <[email protected]> > > Subject: serialization issues > > To: [email protected] > > Date: Tuesday, February 2, 2010, 12:20 PM > > Hi folks! > > > > While hacking the @ViewScoped I came to the conclusion that > > we have to think about whether our Context implementations > > have to be Serializable. > > > > The problem arises when we store our Context map in e.g. > > the JSF ViewMap which gets serialized when the view got > > rendered. > > > > We should also think about storing our SessionContext and > > ConversationContext in the session instead of a singleton > > map. This is really needed for making OWB clustering > > capable, and would also make it more safe (in terms of > > session security already handled by the AppSrv)! > > And for making this possible, we also need make our > > internal Contexts serializable + create some wrapperContext > > objects for non-serializable portable Contexts. > > > > LieGrue, > > strub > > > > > > > > > > > > > > -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
