Nader Aeinehchi wrote:
> Hello
>
> What is thread safety policy of Qi4j?
>
> In several places, there are composite actions that are subject for
> failure unless the code is guaranteed to be thread confined. For
> example, in PropertyInstance, there is no obvious synchronization
> strategy to guard <code>value</code> from invisibility:
>
> public T get()
> {
> if( value == ImmutablePropertyInstance.UNSET )
> {
> return (T) ( (PropertyDescriptor) propertyInfo ).defaultValue();
> }
> return value;
> }
Not that for persistent state, i.e. EntityComposite, this is irrelevanty
since they are accessed through UnitOfWork, which only one thread at a
time uses anyway.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
