Jesper Pedersen wrote:
That makes me sad.
The @DataSourceDefinition workaround sounds like it'll work, but it's a shame to have to use two different methods of datasource config. It'll also complicate how I set up my dev/staging/prod environments.
For the record, I'm needing a non-tx datasource in order to be able to use Quartz's JobStoreCMT. If anyone has suggestions on a way to configure these more elegantly, let me know.