With iBATIS, you can supply configuration properties at runtime - look at the API for the constructors of the sqlmapclient - one of them allows you to pass a properties object into it - those can be used to configure the data source.
Larry On 9/27/07, Ashish Kulkarni <[EMAIL PROTECTED]> wrote: > Hi > This sounds intresting > I am also working on an application which is suppose to get data from more > then one database and then merge and create one xml file and send it back. > > So in this case, i will have to work with more then one JNDI, > Has anyone experience with working this kind of application, any > suggestions. > I am using ibatis for SQL mapping > > Ashish > > On 9/27/07, Nils-Helge Garli <[EMAIL PROTECTED]> wrote: > > > > The idea of the local JNDI reference (which exists for the application > > instance only) is to decouple it from the actual, physical JNDI name > > of the resource. The mapping of the datasource name is (usually) done > > when the application is deployed. I am not familiar with how WebLogic > > handle this, but maybe this website can help: > > http://edocs.bea.com/wls/docs92/webapp/configureresources.html > > > > Nils-H > > > > On 9/27/07, Ashish Kulkarni <[EMAIL PROTECTED]> wrote: > > > Hi > > > But suppose i have to install the same war file on same application > > server, > > > one installtion pointing towards database1, and > > > other installation pointing towards database 2. > > > And this is quite possible to happen, if database 1 is prodution > > database > > > for site1 and database 2 is production database for site 2. > > > > > > So there cannot be one JNDI name, but 2 JNDI in web application server, > > > so what about this scenario > > > > > > On 9/27/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote: > > > > > > > > 2007/9/27, Ashish Kulkarni <[EMAIL PROTECTED]>: > > > > > Hi > > > > > We a to develop a web application which we want to be able to deploy > > on > > > > any > > > > > J2EE compatiable application server. > > > > > We would create a war file for deployment, but there is a issue with > > > > > database connection, > > > > > We do not know the JNDI name, > > > > > So we thought we would put xml file under WEB-INF folder, and after > > > > > deploying the application, modify the JNDI name in this XML and > > restart > > > > the > > > > > application, > > > > > Is this a good way of doing it, since BEA recommends not to modify > > any > > > > thing > > > > > after deploying the application, > > > > > We would be giving this war file to more then one deployment, and we > > do > > > > not > > > > > want to maintain different war files one for each deployment, but > > just > > > > have > > > > > one far which we can use for deployment in all servers. > > > > > > > > IMHO, you have to decide (and not change) your data source JNDI name, > > > > and then configure it in the container. > > > > > > > > Antonio > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
