http://www.kaigrabfelder.de/en/ yet another blog about java, software, movies and more... http://www.kaigrabfelder.de/en/2011/10/29/latest_ibatis_2_documentation.html With the move of the iBATIS persistence framework from apache to google code and the rename to mybatis</a> it got a little bit complicated for end users of iBATIS 2.x to get the latest iBATIS 2 documentation documents...<p><a href="http://www.kaigrabfelder.de/en/2011/10/29/latest_ibatis_2_documentation.html">Read more...</a></p> http://www.kaigrabfelder.de/en/2011/07/17/integration_of_socialengine_with_external_user_administration.html I recently had the task to integrate a SocialEngine installation with an external user administration system (written in PHP). Social Engine users should be automatically created/enabled/disabled when a user in the external system is created or deleted. In addition to that the passwords should be kept synchronized: i.e. whenever the password of a user is changed in the external system it should automatically be changed in SocialEngine as well...<p><a href="http://www.kaigrabfelder.de/en/2011/07/17/integration_of_socialengine_with_external_user_administration.html">Read more...</a></p> http://www.kaigrabfelder.de/en/2011/04/02/mockito_spring_abstractjunit4springcontexttests.html I know some people consider it bad practise. But nethertheless I still believe that there is sometimes no alternative to tests that include startup of spring application contexts and initialization of in memory database. Actually I quite like those tests because if I don't include my database layer and my spring application contexts in my test I always have a bad felling about the quality of my software....<p><a href="http://www.kaigrabfelder.de/en/2011/04/02/mockito_spring_abstractjunit4springcontexttests.html">Read more...</a></p>