CODEWITHSUNDEEP
javaspringmaven
Ignasi
Ignasi

Reputation: 6185

Java domain objects shared between projects

I have two Java projects with same domain objects.First project is the administration of a webapp. And second project is the webapp.

I've chosen this approach in order to allow deployment of administration without downtime for my webapp.

So both projects use same database. I'm using spring-data and marking entities with @Entity.

My question is: is there any way to replicate domain objects in each project? For example creating another maven module with the domain objects and mark as a dependency. (But in this case @Entity will still work?).

Upvotes: 2

Views: 3297

Answers (3)

br11Developer
br11Developer

Reputation: 1

It seams that you will need at least three modules. 1st - the domain module with the enitity annotated domain classes; 2nd - the application itself witch depends on the domain module; 3rd - the adm module witch also depends on the domain.

Now that you have a multi-module maven project you should have a 4th project formally listing the other three as its child modules.

P.s.: Resist to the temptation of creating separate git repositories and evolving the versions of the modules separately.(just an advice)

Upvotes: 0

radai
radai

Reputation: 24202

the way is just as you said it - create a maven module (usually called datamodel, infomodel or something along those lines) that contains all of your JPA classes (@Entity classes).

this model can either be a completely separate 3rd project (more work) or, more likely, pick one of the 2 projects as the "owner" of the module and the other project will simply list it as a dependency. in both cases you'll need to think about things like version compatibility (what happens when you update administration but not the webapp and the entities changed? who updates the database, how do you make sure the older code can still read/write it?)

as for working, JPA classes work just fine in their own jar.

Upvotes: 4

Uyak
Uyak

Reputation: 27

Like you have raised is a good approximation, separating two different maven projects.

What you're trying to do is very similar to the structure of Broadleaf Commerce. It is a multi-module project using Maven and Spring, is open source, so you can look at how it is structured to see if it helps.

Here you have another guide of how to implement it step by step. Hope it helps.

Upvotes: 0

Related Questions