Here's the scenario...

Project A uses cayenne
Project B also uses cayenne

They both have a cayenne.xml and nodes and domains, etc.

Package A uses package B. I'm finding that when package A first
initializes cayenne, subsequent initializations when classes from
package B are instantiated ignore the cayenne.xml file from package B
and it's underlying maps,nodes,domains, etc. causing some chaos. I bet
this is the expected behavior. I could merge and copy the cayenne.xml
files so that all packages use the same file. I bet there's a better
way, though. Perhaps even the /best/ (tm) way...

Please advise!

CG

Reply via email to