Hi Tom,
many thanks for the quick answer.
But when I regard this example, it does not solve the problem with the
password-change of the db-user:
<jdbc-connection-descriptor
jcd-alias="default"
default-connection="true"
platform="Sapdb"
jdbc-level="2.0"
jndi-datasource-name="java:DefaultDS"
username="sa" <-------------
password="" <------------------
eager-release="false"
batch-mode="false"
useAutoCommit="0"
ignoreAutoCommitExceptions="false"
>
Christine
[EMAIL PROTECTED]@inet schrieb am 03.08.2005 16:20:12:
> > We use OJB 1.0.1 in a web-app under JBOSS 3.2.6 and with Oracle 9i.
> > If I pack repository.xml into the war-File, all works fine.
> >
> > But in production the database-settings are changed one or two times a
> > year. For example, if they change the password of the db-user, which we
use
> > to connect, we have to change and deploy the web-app.
>
> The normal way in which webapps handle this, is to use JNDI
> datasources. These are configured in the server configuration and
> you'll give OJB only the jndi name (and the repository.xml file stays
> in the war). Have a look here for an example:
>
> http://db.apache.org/ojb/docu/guides/deployment.html#%
> 0A++++++++++++++++++++++++-N1022A
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
