DATAJDBC-293 @EnableJdbcRepositories support multi jdbcTemplate

[kdlan]

If the application use multiple DataSources for different domain classes, Spring Data JDBC does support it directly
with @EnableJdbcRepositories add a property jdbcOperationsRef in order to support this.

[pivotal-issuemaster]

@kdlan Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

[pivotal-issuemaster]

@kdlan Thank you for signing the Contributor License Agreement!

[schauder]

Unfortunately, this seems to break backward compatibility in cases where a unique NamedParameterJdbcOperations bean is present but has a different name.

We need a backward compatible to do this.

Also, please add @author tags to the files changed with your name written in latin letters.

[kdlan]

@schauder

Reference to determineAutowireCandidate, for backward compatible JdbcRepositoryConfigExtension should be implemented as following

• if jdbcOperationsRef has text, use it as field reference bean name
• if jdbcOperationsRef has no text, for bean names of class NamedParameterJdbcOperations:
  • if only one bean name, use it as field reference bean name
  • if multiple bean names
    • determine primary bean name
    • determine highest priority bean name
    • determine bean name equals field name jdbcOperations
    • throw NoUniqueBeanDefinitionException
  • if no bean names throw NoSuchBeanDefinitionException

Is that ok?

[schauder]

That sounds correct.

[kdlan]

Make a new commit for backward compatible.

Reference to OrderUtils, the priority of bean definetion depends on javax.annotation.Priority and this is not used in project now. So I did not implement the determine highest priority bean.

[schauder]

That's polished and merged. Thanks.