1 Reply Latest reply on Feb 24, 2005 4:39 PM by Luca Stancapiano

    Multiple Entity Beans against multiple datasources - all fai

    Chirag Patel Newbie

      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?