You might use such number of different connections but it will increase the complexity.
If you use entities (EJB2 or EJB3) you have to deploy the entity for each schema/connection in one jar.
Also I don't surveying the performance impacts, it bring more overhead and synchronization work ...
Thank you Wolf-Dieter Fink. Is there any that we can increase Performence and reduce complexity.
All my schemas have same tables but different data.
- many persistence jar's
- it will be complex to understand at runtime
- enlist more than one datasource in a transaction
For example the access to connection pool and transaction manager must be done (just duration) and in case of parallel access these must be synchronized. So that might become as a bottleneck and scalability blocker.
Thank you Wolf-Dieter Fink.