spring-data-examples | Examples for using Spring Data for JPA MongoDB Neo4j | Security library

Yes, you can do it:

In order to let spring knows what DataSource is related to what Repository you should define it at the @EnableJpaRepositories annotation. Let's assume that we have two entities, the Servers entity and the Domains entity and each one has its own Repo then each Repository has its own JpaDataSource configuration.

1. Group all the repositories based on the Data Source that they are related to. For example

Repository for Domains entities (package: org.springdemo.multiple.datasources.repository.domains):

The first query is actually the correct one and it is working fine.

The problem is in your test. models is a Map, but you treat it like a List which compiles because a list index is also a valid map key.

If you change the last two assertions in your test like this they will succeed:

Eclipselink uses ASM to parse the entity classes and generate metadata which in turn gets used to decide whether an entity class is actually an entity (i.e. carries the @Entity annotation).

When encountering the "nested member" (i.e. nested enum) in my entity classes, ASM 6.2 throws an UnsupportedOperationException which makes eclipselink discard the already collected metadata for this class and generate dummy metadata which contains no annotations. Hence the error.

There are four ways to fix this:

1. Do not use nested classes in entity classes for now
2. Compile your own version of eclipselink where you set the ASM api level to ASM7_EXPERIMENTAL in eclipselink's MetadataAsmFactory$ClassMetadataVisitor constructor. I have not tested this but according to this it should fix the issue.
3. Use a lower bytecode level (9 or 10 should work, theoretically). Again, I have not tested this but according to this it should fix the issue.
4. Use another JPA provider

Apparently, this has already been fixed in eclipselink master and their 2.7 branch, so the fix should be available in the next release.

This looks like DATAJDBC-228

Almost quoting (with generalized version information):

The root cause of the problem is that current GA releases of Spring Boot specify the version of Spring Data Commons as 2.0.x But the version of Spring Data JDBC requires 2.1.x which also gets pulled in automatically by Maven when Boot is not present.

To fix this just add an explicit dependency to your pom:

You're using an in-memory database: jdbc:hsqldb:mem:testdb. When the jOOQ code generator starts, it receives a new database that is empty, not the database that you may have created elsewhere.

One of the solutions I can think of is this:

In your repository,I have defined a method getValueLyingBetween and written a simple query:

Sounds like you have multiple TransactionManager beans in your Spring context. Camel does not know which one to take. You have to help your Camel a bit.

Define a SpringTransactionPolicy and reference the TransactionManager to be used in the Camel route.

I followed the tutorial for Spring Security OAuth: https://projects.spring.io/spring-security-oauth/docs/oauth2.html

In particular you have to enable the resource server. This is my (modified) configuration):