spring-content-s3-boot-starter drags spring-data-jpa dependency about spring-content HOT 3 CLOSED

Hi @neVERberleRfellerER, the idea of Spring Content is to be an abstraction layer over the storage, just like Spring Data is the abstraction layer over the database. So, you can use any JPA database with filesystem storage, or S3 for example. You wouldn't, and are not, forced to use BLOBs (i.e. SC JPA). Some seem to belong together Spring Data Mongo and Spring Content Mongo. The intention was you could use, for example, Spring Data Cassandra with Spring Content S3 and build a horizontally scalable ECM - and that is not something that the traditional ECM vendors can do.

So your original assessment is correct. If you are not using "locking and versioning" then it shouldn't be pulling in spring-data-jpa for sure. That said, "locking and versioning" is a new feature and ONLY supports JPA right now. The design of this feature should match the goals of the Spring Data/Spring Content project but might not be quite correct right now but might not be quite there. We'll continue to iterate on it.

from spring-content.

@neVERberleRfellerER. Thanks for raising this as an issue and I apologize for the tardy response times. We can take a look at this. When we add the locking and versioning feature I assume we created this. Will take a look and see if we can remove it for you.

from spring-content.

@paulcwarren Thanks, but after my small investigation I came to conclusion, that this is my fault and it's not worth fixing on Spring Content side. Somehow I expected that Spring Content does not care about persistence layer used for domain objects and that I can use whatever persistence mechanism I want (e.g. MyBatis or Spring Data MongoDB), but this is not the case as illustrated by @Query annotations in spring-versions-commons. This also explains why all examples use JPA which I attributed to "most common use case should be best documented". Merely supporting versioning for non-JPA use cases is impossible now, due to lack of persistence agnostic versioning annotations. Maybe just mention JPA dependency in documentation, because all examples using JPA is only hint
So, feel free to close this. I'll stay at 0.4.0 for now thinking about possible solutions for my problem (but due to time constraints I'll probably just use S3 directly in this case).

from spring-content.