|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
0.12d
|
|
|
Remaining Estimate:
|
0d
|
|
|
Time Spent:
|
0.12d
|
|
|
|
|
When using an alternate table prefix in the batch repository schema and
setting this property on the JobRepositoryFactoryBean, the setting is properly injected into the three primary daos
( JdbcJobInstanceDao, JdbcJobExecutionDao, JdbcStepExecutionDao ).
However the setting is not injected into the JdbcExecutionContextDao, resulting in an inconsistent table naming prefix strategy in the batch schema.
It appears to me that the JdbcJobExecutionDao and JdbcStepExecutionDao each create an instance of the JdbcExecutionContextDao, referred to as "ecDao", and should inject the tablePrefix.
They already set some properties of the "ecDao" in their afterPropertiesSet() .. but seems they neglect to inject the tablePrefix as well.
Should be a simple one line fix in each dao?
|
|
Description
|
When using an alternate table prefix in the batch repository schema and
setting this property on the JobRepositoryFactoryBean, the setting is properly injected into the three primary daos
( JdbcJobInstanceDao, JdbcJobExecutionDao, JdbcStepExecutionDao ).
However the setting is not injected into the JdbcExecutionContextDao, resulting in an inconsistent table naming prefix strategy in the batch schema.
It appears to me that the JdbcJobExecutionDao and JdbcStepExecutionDao each create an instance of the JdbcExecutionContextDao, referred to as "ecDao", and should inject the tablePrefix.
They already set some properties of the "ecDao" in their afterPropertiesSet() .. but seems they neglect to inject the tablePrefix as well.
Should be a simple one line fix in each dao?
|
Show » |
|
Bug
Closed
Major
tablePrefix property is not injected into JbdcExecutionContextDao
It is actually three lines :-) ,but the third one may be the one you don't like:
Making tablePrefix protected in the abstract dao? Otherwise create a public getter ... your call.
thanks for a great product
davidv
ps: You might want to correct the typos in the issue title.