I have a number of CMP beans running in JBoss 4.0.1, some which reference data in one database and some that reference data in another database. In the event that one of the databases is unavailable, I would still like the CMP beans for the other database to work. Currently, if JBoss is unable to fix a table name for one of the CMP beans, all of them throw an "IllegalStateException: createBeanClassInstanceCommand == null." I don't understand why all my CMP beans should fail. Shouldn't only those EJBs which can't contact their backing store fail?
The only way I have found to work around this is to group my CMP beans by datasource and deploy them in separate ejb jar files. Is this my only option? Would using JBossCache or Hibernate solve my problem?
hi pate....i know that using a cmp with more resource reference is not recommended. Then I think that it can to give collateral effects. But you can to use two entities of same type and different name that using different databases. The important thing is that for each entity must to exist a only resource reference