Replies: 1 comment
-
|
I guess what I'd like here is for the the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Would it be possible somehow to allow associations to entities which are not in the current classpath?
Suppose I have two Spring Modulith modules,
FooandBar, each modelling their own aggregate. And suppose I want to allowBarentities to refer toFooentities by id. But, I wantBarto be as loosely coupled toFooas possible, so I don't even wantBarto be allowed to referenceFoo. (At the persistence level, we can imagine that thefoo_idcolumn onBarentities is just a plain column (e.g. UUID) without a foreign key constraint. The same use case would occur ifFooandBarwere separate microservices.)Since I don't want to be able to reference
FoofromBar, I can't write e.g.:... because I can't (and don't want to) be able to reference
FoofromBar.However, I'd still like somehow to record that
foois a reference to theFooaggregate, so that e.g. the automatic document generation would still work.Is this possible with the current jmolecules? Or if not, could this feature possibly be added?
Beta Was this translation helpful? Give feedback.
All reactions