myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Manfred Geiler <manfred.gei...@gmail.com>
Subject Re: Thread-safety of JSF DataModel / TreeModel
Date Wed, 07 Sep 2005 08:42:34 GMT
Sorry for bothering, just saw that Sean already has replied to this mail.
-Manfred

2005/9/7, Manfred Geiler <manfred.geiler@gmail.com>:
> Any tree expert has an idea about this?
> Mathias Werlitz, any new perception?
> -Manfred
> 
> 2005/8/26, mathias.werlitz@daimlerchrysler.com
> <mathias.werlitz@daimlerchrysler.com>:
> >
> > Hi,
> >
> > as no one on the user list responded I will post my question / observation
> > here:
> >
> > I was thinking about to improve the TreeModel for the tree2 but came to a
> > more general problem regarding thread-safety.
> > When a component (UIData / UITreeData) uses a local model there are no
> > problems at all, everything runs in one thread per request.
> > Now if you move your model to any higher scope than request (e.g. providing
> > a session scoped DataModel) as far as I can see there are potentially
> > problems with threadsafety ... in a multi-threaded servlet environment. Two
> > views with different components using the same model could interfere each
> > other - setting different rows in the DataModel. The user could provide a
> > special model but with the concept of setting a row and than retrieving data
> > about that row its somehow impossible to do a synchronization in the model
> > itself, so that every component gets the right data for its row currently
> > processing.
> >
> > Is this a flaw in the spec or do I miss something here? I have found no
> > comments about that in the spec. The component implementation does no
> > synchronization nor this is done in any DataModel impl.
> > Does anybody has experience with not-request-scoped DataModel?
> >
> > Your comments?
> >
> >
> > Regards,
> > Mathias Werlitz
>

Mime
View raw message