Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0, 1.0.1, 1.1.0-RC1, 1.1.0-RC2, 1.1.0, 1.2.0, 2.0.0-RC1, 2.0.0, 2.1.0-RC1, 2.1.0-RC2, 2.1.0-RC3, 2.1.0-RC4, 2.1.0-RC5, 2.1.0, 2.2.0-RC1, 2.2.0, 2.3.0-RC1, 2.3.0-RC2, 2.3.0, 2.4.0-RC1, 2.4.0, 2.5.0-RC1, 2.5.0-RC2, 2.5.0, 2.5.1
-
Fix Version/s: 2.7.0
-
Component/s: JMock 2.x.x Library
-
Labels:None
Description
The Mockery is not thread safe but people often use jMock with multithreaded code.
Thread-safety can be easily implemented as a decorator that wraps the imposteriser. It can then be plugged into the Mockery when needed.
The only other issue to address is that expectation failures are swallowed by background threads. Issue JMOCK-183 will address this issue.
The Imposteriser decorator is checked into SVN.
Resolution of this issue is waiting on the implementation of
JMOCK-183.JMOCK-183.