My idea was something like model import capabilities, so you can import
models inside models, this needs to have 2 different paths: file path
for modeler and runtime paths
Still this forces to have some special project layout between modules
wich is not the best thing to enforce.
The main use
On Oct 24, 2012, at 2:58 PM, Ramiro Aparicio
wrote:
> If thats possible even if the configuration must be done in a Java class (I
> would prefer XML but it is better that nothing) the only failing point is
> relationship between models of diferent modules, if they are 1-N it can be
> easily
ServerRuntime runtime = new ServerRuntime(new String[] {
"com/example/cayenne-project.xml",
"org/foo/cayenne-library1.xml",
"org/foo/cayenne-library2.xml"
});
There is also a "Merging Multiple Projects" chapter in cayenne-guide.pdf
included with 3.1B1 release. It has some more details.
Umm I thougth a ServerRuntime could load only one configuration file,
can you point me how can I load several?
If thats possible even if the configuration must be done in a Java class
(I would prefer XML but it is better that nothing) the only failing
point is relationship between models of di
> I am a big fan of making everything as modular as possible,
me too :)
> and this configuration helps, but what I think it would be perfect is being
> able to put the diferent model files in diferent modules and just orchestrate
> DB nodes and model composition in the project file, like a mav
Hi,
After upgrading to 3.1 it is now more evident that you can split the
data model and data nodes as it is needed so the model can span several
DBs or several models can be in the same DB.
I am a big fan of making everything as modular as possible, and this
configuration helps, but what I thi
