[Opensource] Maintaining 2 contexts, one for Expresso tables, one for business logic tables?

[Dcomeau at xenos.com]

Just curious about something,

For the project I'm doing, I was given a set of DB tables (around 20) to
work with.  I am developing an Expresso app to manage the data in those
tables.  Another component in the system (that I'm not working on) will read
the data in the table to perform processes.

The other team isn't too keen on my adding the Expresso tables to their
database and are insisting that I use a seperate database for the Expresso
tables.  So I need to have my app maintain two seperate contexts.  Is this a
common thing?  I am trying to make sure that there are no problems in doing
so.  

I figure I just have to have store another variable in the session that
contains the context/dbName for the business tables and always make sure
that getDBName() returns the context that contains the Expresso tables.

I'm thinking that I can do this type of thing:

  MySpecialDbObject dbo = new MySpecialDbObject();
 
dbo.setDBName(request.getInitParameter("CONSTANT_FOR_NON_EXPRESSO_CONTEXT"))
;

...where I get the logon controller to store the
"CONSTANT_FOR_NON_EXPRESSO_CONTEXT"  as an initParameter in the request, and
make sure that request.setDBName() provides the context containing the
Expresso tables.

Am I overlooking anything?