Hello,
here is quite a strange situation we have to deal with ...
We have a series of Entity and Session Beans using a pool in order to connect
to a database.
Nothing special exepect the fact that the database switches during the day and
night for maintenance reasons. The weblogic server (4.5.1) can not be shutdown
and the customer doesn't want to redeploy the beans at every switch. The information
on which
database is currently up is maintened in an administrative database that is
stable and doesn't failover...
So I was wondering what design pattern I could apply to cope with this scenario ?
1) Is there a way to define a "virtual pool" that could bind me with the currently
active DB ?
2) Should I proceed with a select to the admin datatabase every time, in order to
dynamicaly
determine which database (i.e pool) I should use ?
3) Is there a way to update an env. property of the bean with the info in the admin
database ?
Thanks in advance for all input.
Alain
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
