It depends on whether same application can access more than one database on
*one server*. If so, you must really use dynamic creation of DataNodes.
But the most common case is when there is one connection, but you do not
know it when you're building war archive. Then you can use
JNDIDataSourceFactory for your datanodes and configure DB settings in
application server using its JNDI container.
15 декабря 2009 г. 14:01 пользователь Рябицкий Евгений <
eryabitski..iasoft.ru> написал:
> Didn't understand the question. :(
> We are producing only war archive.
> This war archive can be deployed on hundreds of servers... So there is used
> external configuration file (like log4j.properties) to configure DB
> settings.
>
> Evgeny.
>
>
> -----Original Message-----
> From: Andrey Razumovsky [mailto:razumovsky.andre..mail.com]
> Sent: Monday, December 14, 2009 10:38 AM
> To: de..ayenne.apache.org
> Subject: Re: XML file changes: dropping .driver.xml
>
> Hi,
> Why can't you use JNDI for different server deployments?
>
> 14 декабря 2009 г. 10:29 пользователь Рябицкий Евгений <
> eryabitski..iasoft.ru> написал:
>
> >
> > Let me share my usage experience:
> > We don't use driver.xml at all. Just some empty file.
> > Usually there is one node and DataSource for this Node is overridden by
> our
> > configuration. We can't just build-in it in cayenne.xml because data base
> > configuration can various on different server deployments.
> > I mean that when all database settings are strongly set in cayenne.xml
> > (that is inside your JAR/WAR) you can't change it so easy.
> >
> > I have some ideas about dynamic adding of DataNodes. Is it possible?
> >
> > Evgeny.
> >
> >
> >
> > -----Original Message-----
> > From: Andrus Adamchik [mailto:aadamchi..pache.org]
> > Sent: Sunday, December 13, 2009 11:45 PM
> > To: de..ayenne.apache.org
> > Subject: XML file changes: dropping .driver.xml
> >
> > Since I am rewriting the project load/save code, I am going to add one
> > more format change - move .driver.xml stuff into cayenne.xml. The
> > original motivation for a separate file was to allow users to swap it
> > in different deployment environments, e.g. to protect their production
> > password. Now we have the password encoder facility that does not
> > require file swapping, and most JEE environments are using JNDI
> > anyways, so makes sense to reduce the complexity, and store the
> > <driver>..</driver> section right in cayenne.xml.
> >
> > Andrus
> >
>
>
>
> --
> Andrey
>
-- Andrey
This archive was generated by hypermail 2.0.0 : Tue Dec 15 2009 - 07:11:47 EST