7 Replies Latest reply on Mar 22, 2002 3:25 AM by Bernie Meyer-Willner

    Can't deploy CMP entity beans with JBoss 3 beta (CVS) and my

    Bernie Meyer-Willner Newbie

      Hi,

      I downed JBoss beta from CVS yesterday, got it built and up and running. It even deployed my mySQL datasource; only the syntax of mysql-service.xml had to be changed a little. (I had used the JBoss 3 alpha from jboss.org before, and all worked fine and I also deploying CMP entity beans worked like a charm).

      Now when I try to deploy the jar file with my CMP entity beans (which worked before - and remember, the datasource is deployed) I get the following exception stacktrace:
      (PartnerJur is the first CMP entity bean)

      2002-03-20 14:56:40,297 INFO [org.jboss.ejb.EjbModule] Deploying BenutzerSession
      2002-03-20 14:56:40,587 INFO [org.jboss.ejb.EjbModule] Deploying PartnerFacade
      2002-03-20 14:56:40,728 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.PartnerJur] Initializing CMP plugin for PartnerJur
      2002-03-20 14:56:41,168 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.PartnerJur] Loading standardjbosscmp-jdbc.xml : file:/C:/Programme/GNU/WinCvs/jboss-all/build/output/jboss-3.0.0beta2/server/default/conf/standardjbosscmp-jdbc.xml
      2002-03-20 14:56:41,609 ERROR [org.jboss.ejb.EntityContainer] Exception in service lifecyle operation: create
      java.lang.NullPointerException
      at org.jboss.ejb.plugins.cmp.jdbc.JDBCTypeFactory.createTypeSimple(JDBCTypeFactory.java:113)
      at org.jboss.ejb.plugins.cmp.jdbc.JDBCTypeFactory.getJDBCType(JDBCTypeFactory.java:75)
      at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMPFieldBridge.(JDBCAbstractCMPFieldBridge.java:55)
      at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.(JDBCCMP2xFieldBridge.java:43)
      at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.createCMPField(JDBCEntityBridge.java:274)
      at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.loadCMPFields(JDBCEntityBridge.java:141)
      at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.(JDBCEntityBridge.java:101)
      at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.create(JDBCStoreManager.java:276)
      at org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager.java:138)
      at org.jboss.ejb.EntityContainer.create(EntityContainer.java:329)
      at org.jboss.ejb.Container.invoke(Container.java:765)
      at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1003)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:745)
      ...

      How come? Are there any significant changes in any of the (CMP specific) config files that I should be aware of? Like in jboss-service.xml... do I have to put anything else into it? If this is of help: I tried putting the following line in my jboss-service.xml:


      org.gjt.mm.mysql.Driver


      This worked before with JBoss alpha, but now if I put it in JBoss doesn't even start up.

      Thanks! Any answer will be greatly appreciated!
      Bernhard