Holy J(2)EE Utils / News: Recent posts

Version 1.2.0 of the DbUnit Test Skeleton (dbunit-embeddedderby-parenttest) has been released.

A major upgrade release:
(1) Upgraded to DbUnit 2.4.7
- includes migration to SLF4j for logging
(2) Various improvements:
- RowComparator made fluent - all assert* now return this so that calls can be chained
- createDataSetFromFile modified to search on the calling class' classpath
=> data set file may be next to a test class
- replaceDatabase: added logging of duplicated PKs for easier troubleshooting
- improved JavaDoc, improved logging
- Improved error reporting, e.g. when the derby db is locked by another process, for failed DB startup
- Fixed broken DatabaseCreator
- Added few utility methods to the *TestCase (getSqlConnection) and EmbeddedDbTester (setConn.Prop., resolveConn.Prop., getSqlConnection)
- Addedd RowComparator.withErrorMessage and, .withOneTimeErrorMessage and more unit tests
- RowComparator: a custom check other than .equals can be done in the RowComparator's assertNext
by passing a value of the type ValueChecker
- RowComparator: added assertNext(.., String[]) to make the possibility of type-insensitive comparison clear + appropriate JavaDoc update... read more

A new snapshot of the version of 1.2.0 (svn rev. 90) with even more cool features has been released to the Maven snapshot repository http://oss.sonatype.org/content/repositories/jakubholy-snapshots/net/jakubholy/testing/dbunit-embeddedderby-parenttest/1.2.0-SNAPSHOT/ - look for the latest one (ending with -3.*). Only the .zip failed to upload :-(

What's new since the latest stable release 1.1.0?
- RowComparator made fluent - all assert* now return this so that calls can be chained
- filled missing comment part, little insignificant refactoring
- Proceeding with 1.2.0 development - switched to the latest DbUnit and its SLF4j for loggin. Aside of that, createDataSetFromFile modified to search on the calling class' classpath => data set file may be next to a test class.
- replaceDatabase: added logging of duplicated PKs for easier troubleshooting
- EnhancedDatabaseTesterDecorator: added hints to an error message
- Refactoring - created DbUnitUtils, added log to tester's setDataSet
- commented, improved logging
- extended getDataSet's JavaDoc comment
- Improved error reporting when the derby db is locked by another process.
- Fixed broken DatabaseCreator, added few utility methods to the *TestCase (getSqlConnection) and EmbeddedDbTester (setConn.Prop., resolveConn.Prop., getSqlConnection).
- Addedd RowComparator.withErrorMessage and .withOneTimeErrorMessage and more unit tests.

VERSION 1.1.0 of the DbUnit Test Skeleton (dbunit-embeddedderby-parenttest) has been released.

This is a major reorganization and feature release:
(1) All functionality moved to EmbeddedDbTester so that extending the AbstractEmbeddedDbTestCase
isn't necessary anymore, which is useful e.g. in JUnit 4 or when extending another JUnit
derivation. It's also a standard DbUnit's IDatabaseTester.
(2) It's now possible to change completely the DB used by defining some JDBC
properties in dbunit-embedded.properties
(3) Added utility methods getDataSource, getSqlConnection and a convenience method
createCheckerForSelect, some of those implemented in the EnhancedDatabaseTesterDecorator
so that they can be added to any IDatabaseTester.
(4) Switched from Java util logging to commons-logging for better configurability.... read more

Since the latest release 1.0.2 of DbUnitTestSkeleton (dbunit-embeddedderby-parenttest) the binaries will be also available in the Maven Central repositry and thus immediately available to all maven users. Check the repository at http://tr.im/NrUA and a blog about how to achieve this with Sonatype at http://tr.im/mvnblog

DbUnit Test Skeleton 1.0.1 has just been released.

This is a minor feature release, I've only added the method replaceDatabase to the abstract parent test to make it possible to replace the content of the test database from a data set file at the beginning of a test method that requires other data than the default ones.

See the project's wiki page for more info about this (sub-)project and the methods JavaDoc for info about usage

I've just released a new sub-project - DbUnit Test Skeleton.

Creating a a DbUnit test case may be time consuming. With this project you can have your DbUnit test including an embedded database with structures and data ready in a few minutes. (At least if you are fast enough in writing SQL and preparing your data :-) ).

This project helps you to setup a DbUnit test using an embedded Derby database by providing... read more

From the release notes:
Groovy 1.6, the latest major and stable version of the popular dynamic language for the JVM, has been released on Feb 2009. In a nutshell, it brings great compile-time and runtime performance improvements, multiple assignments, optional return in if/else and try/catch blocks, Compile-time Metaprogramming - AST Transformations and all the provided transformation annotations like @Singleton, @Lazy, @Immutable, @Delegate and friends, the Grapes and grab() and its @Grab annotation, various Swing builder and Swing console improvements, the integration of Groovy JmxBuilder, JSR-223 scripting engine built-in, and various metaprogramming improvements, like the ExpandoMetaClass DSL, per-instance metaclasses even for POJOS and runtime mixins. Details in Jira: http://jira.codehaus.org/browse/GROOVY?report=com.atlassian.jira.plugin.system.project:changelog-panel

Groovy 1.5.4 has been released recently. According to its webpage, it brings new features like Java 5 annotations, generics and enums, it provides significant performance gains, new meta-programming capabilities, and a few other additions in its syntax, like the new Elvis operator or the ability to omit parentheses in methods with named arguments to make DSLs even more readable. It brings many Java 5 features but can still be run in a 1.4 JVM.
One nice feature I've noticed is that it supports the java-style for-loop with a typed variable (for(String s: myArray)) and gives a nice warning with a suggestion of the 'correct' syntax for an untyped variable. ... read more