FYI this is done. There is now a separate sql.properties.
Florent
On 11 Jun 2007, at 20:42, Vincent Dutat wrote:
OK,
at least, can org.nuxeo.ecm.sql.jena.databaseType property moved to
a separate property file, for the reason I mentioned earlier ?
Florent Guillaume wrote:
We would like that too, however datasources are a JBoss concept
and are read by JBoss, so the only variable replacement in the -
ds.xml files are done using JBoss variables.
There are several options to make this work:
1. launch JBoss by giving it too al system properties file to
read, so that they are taken into account in the datasource.
This is easy to do, but changes the way JBoss is launched which is
platform-dependent (as the executable scripts depend on the
platform).
See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossRunParameters
for the -P option.
2. do the replacement at Nuxeo pre-deployment time and point JBoss
to a datasource directory with nuxeo-replaced variables instead.
This would be more transparent but is more code to write.
So for your own project you may want to use the first option until
we find the time to code a datasource preparsing.
Florent
On 11 Jun 2007, at 19:37, Vincent Dutat wrote:
it would be nice if datasource properties like
org.nuxeo.ecm.sql.jena.databaseType are placed in an other config
file (i.e. datasources.properties) so that these properties are
overriden more easily (without having to maintain in the
overriding file other general properties not related to
datasources).
Regards.
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
