SequenceManager's integrity

[Pulat Yunusov]

Currently, all PersistenceBrokers that use SequenceManagerHighLowImpl 
share one Map for keeping sequences. That map keys sequences essentially 
by table name in many common cases.

I understand if two databases have tables with the same name, accessing 
them within a single OJB instance will lead to corruption of the 
sequence manager's internal map as one entry can potentially be replaced 
with another with the same key (same table name).

Is this a valid and a known problem and are you aware of any workarounds?
Thank you,
Pulat
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]