This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
As coincidence would have it I just added a section to the docos:
If you are using a database platform that is not in the
list of supported platforms, you may be able to use one of the
supported types, if the SQL variant is close enough. To do this
you can use the
raw JobRepositoryFactoryBean instead of
the namespace shortcut and use it to set the database type to
the closest match:
(The JobRepositoryFactoryBean tries
to auto-detect the database type from
the DataSource if it is not specified.)
The major differences between platforms are mainly accounted for
by the strategy for incrementing primary keys, so often it might
be necessary to override
the incrementerFactory as well (using one fo
the standard implementations from the Spring Framework).
If even that doesn't work, or you are not using an RDBMS,
then the only option may be to implement the
various Dao interfaces that
the SimpleJobRepository depends on and
wire one up manually in the normal Spring way.