Feb 4th, 2013, 12:49 PM
UsersRepository, and User domain object with Spring Security
OK, we have a custom UserDetails object for our Spring Security. It stores that data in a table in our relational database.
So, would it make more sense to store the social user data "create table UserConnection", but put all those fields into the same table as the Spring Security data?
Since we use Hibernate/JPA it would be nice to have one domain object for our User, rather than two. Although to be honest some of our user data is in Postgres and the some in Neo4J. And we have two separate domain objects. Because trying to get Spring Data Neo4j and Spring Data JPA to work together, caused us to do it this way. Even though, Spring Data Neo4J has "cross-store" functionality, it required AspectJ, and we use Groovy, so all heck broke loose.