Multiple Datasources Problem WSAD4.0.3

Question

Hi,
I am using WSAD4.0.3 in our project. For our application we have an Oracle 9i DB. I created a Datasource in WSAD Test Server with JNDI name as jdbc/ds1. For one of the task i have to connect to a entire different Oracle 9i DB. This is only for this module. The rest of the application uses the first DB. I have created a second Datatsource with JNDI name as jdbc/ds2. From my DAOs i pass the jndi name to get the connection to the corresponding database. From the EJB test client i was able to run my EJBs, connect using ds2 and run my queries.
The problem i am facing is once the server connects to a database, and afterwards for my next task if i was trying to get connection to the other database, i am not getting any code errors. But apparently the datasource is still connected to the first database and that is giving me a Table or View does not exist error. Its happening both ways. First connects through ds1 when i login to our project. If i do something related to that same database, it works. But if i try getting connection through ds2, i get table does not exist error, because its executing the query in the first database and those tables obviously dont exit in that DB.
I was able to get direct connection to the second database from my DAO. But thats not what i want to do, because i foresee us updating table in 3-4 different databases for this task and we want to use Datatsources because we have change the code whenever they make changes to the Database or the machines where it is.
Could someone please help me on my problem. Any kind of input is appreciated.
Thanks,
Ravi.

Answer 1

Hi Ravi,
I'm not sure I understand your problem. I too use WSAD and have multiple datasources configured for each database I need to connect to without issue. However, it sounds as if you are trying to use the datasources to connect to different db's such as 1 for dev, 1 for test, 1 for qa(?). So you want the datasources to dynamically allow you to run the same code against different db instances. Is this the case?
If so, I'd suggest using the same datasource as default, but configure your system (and I think it can be done in the datasource but I'm not positive) to use property file which defines the db you wish to connect to. You'd still need a restart, but no code changes other than to tweak the property file (and WSAD can be set up to store the data in memory which allows you to write a seperate class which could refresh the memory on changes without a restart).