Wednesday, 27 January 2010
current session cache. Or that's how I understand this article.
Thursday, 21 January 2010
When we get errors like:
java.lang.IllegalStateException: 2 matchers expected, 1 recorded.
It means we are missing a matcher for our mocked classes.
Take this code, for example:
Map<String, Object> params = new HashMap<String, Object>();
List<Integer> groupIds = Arrays.asList(1,2,3);
Replace the last line with:
"If you would like to use matchers in a call, you have to specify matchers for all arguments of the method call."
Otherwise, it should only be known values.
If you are mixing known values with matchers, you will have to use the eq() ("equals) static method
2. when mocking classes that are not an interface, like
SimpleJdbcTemplate, we need to use the createMock, replay, and verify
methods FROM org.easymock.classextension.EasyMock NOT FROM
otherwise, we get this error when running the test:
java.lang.IllegalArgumentException: not a proxy instance
Update 11 November 2010:
You no longer need to do the easymock.classextension package in (2) if you are using EasyMock 3. The package and classes still exist in EasyMock 3 only for backward compatibility. See the documentation.
Saturday, 16 January 2010
<username removed of course>@optus.com.au
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the
recipient domain. We recommend contacting the other email provider for
further information about the cause of this error. The error that the
other server returned was: 550 550 5.7.1 Inappropriate language
used:SHIT (state 18)."
I wonder if Telstra do the same to their work emails.
Tuesday, 12 January 2010
Monday, 11 January 2010
I don't really know what's going on, but somehow each of the package
groups has the 1st character missing. Bizarre.
I'll clean out the IDEA cache using "File --> Invalidate Caches" and
see if that fixes it.
Further down the stacktrace it shows the right name:
Caused by: java.lang.ClassNotFoundException: