Hi Thomas,
the generator probably won't like references to unknown tables, but
maybe you could include the schema containing the referred tables? For
example:
<external-schema filename="other-schema.xml" />
With kind regards,
Hidde.
[EMAIL PROTECTED] wrote:
Hi Wieger,
I did not thought about solution C lol. Well the fact having "dependencies"
from schema B to A is because the webapp B has some other tables having relationship with
it, let's say, the A.om.Country
The om generator will stop if you specify a foreign key that cannot be found in the same schema?
right? That's the reason why I specify the same table B.om.Country but only with the primary key
and the properties baseClass="A.om.Country" basePeer="A.om.CountryPeer"
skipSql="true"
The fonctionnal reason having webapps pointing to the same db is that they share a small amounth of data such user authentication .. They are modules having different features. We want them completly independant.
Many thanks for your thoughts,
Best regards,
Thomas
--
Hidde Boonstra
Us Media B.V.
Stadhouderskade 115
1073 AX Amsterdam
t: 020 428 68 68
f: 020 470 69 05
www.usmedia.nl
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
