You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by Michał Więckowski <mi...@gmail.com> on 2017/07/28 10:15:33 UTC

SessionImpl getAtribute(...) wrong lock required?

Hi Developers,

during my work with Tapestry 5.4.3, I may find a bug.

If you go to class org.apache.tapestry5.internal.services.SessionImpl, line
48.

There is "write" lock acquired, while any other "read" methods are getting
"read" lock.

Is it a bug or is it done on purpose?

-- 
regards

Michał Więckowski