Re: [seam-dev] BijectionInterceptor
On Nov 10, 2008, at 2:03 AM, Shane Bryzak wrote:
In BijectionInterceptor, can anyone remember why we decided to
perform outjection only after the last concurrent thread had
finished invoking the component? It's in relation to the following
issue:
https://jira.jboss.org/jira/browse/JBSEAM-3652
Well, disinjection follows outjection, and disinjecting after a nested
call would be a disaster. I don't know how you are seeing concurrent
access to a component.