3 Replies Latest reply on Dec 29, 2005 11:10 PM by Sachin Shah

    JBoss 4.0 & Entity Beans

    Sachin Shah Newbie

      Hi,

      I am migrating from JBoss 3.2.6 to 4.0.1. All my entity beans were working fine with jaws.xml under JBoss 3.2.6. Now when i try to deploy the same beans under JBoss 4.0.1 the deployment does not give any error but when i try to invoke any finder method it gives error invalid SQL or No such entity in certain cases.

      I changed jaws.xml to jbosscmp-jdbc.xml and change all jaws.xml's finder method to declared sql in jbosscmp-jdbc.xml still i am getting the same error.

      Any idea what is the problem? Is there something missing from configuration point of view or i have to change anything in my code?

      Sachin

        • 1. Re: JBoss 4.0 & Entity Beans
          Sachin Shah Newbie

           

          "sachinvshah" wrote:
          Hi,

          I am migrating from JBoss 3.2.6 to 4.0.1. All my entity beans were working fine with jaws.xml under JBoss 3.2.6. Now when i try to deploy the same beans under JBoss 4.0.1 the deployment does not give any error but when i try to invoke any finder method it gives error invalid SQL or No such entity in certain cases.

          I changed jaws.xml to jbosscmp-jdbc.xml and change all jaws.xml's finder method to declared sql in jbosscmp-jdbc.xml still i am getting the same error.

          Any idea what is the problem? Is there something missing from configuration point of view or i have to change anything in my code?

          Sachin


          Sorry forgot to specify the stacktrace

          16:30:41,072 INFO [STDOUT] javax.transaction.TransactionRolledbackException: cr
          eateBeanClassInstanceCommand == null; nested exception is:
           java.lang.IllegalStateException: createBeanClassInstanceCommand == null
          16:30:41,072 INFO [STDOUT] at org.jboss.ejb.plugins.AbstractTxInterceptor.i
          nvokeNext(AbstractTxInterceptor.java:244)
          16:30:41,072 INFO [STDOUT] at org.jboss.ejb.plugins.TxInterceptorCMT.runWit
          hTransactions(TxInterceptorCMT.java:313)
          16:30:41,072 INFO [STDOUT] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke
          Home(TxInterceptorCMT.java:126)
          16:30:41,072 INFO [STDOUT] at org.jboss.ejb.plugins.SecurityInterceptor.inv
          okeHome(SecurityInterceptor.java:99)
          16:30:41,072 INFO [STDOUT] at org.jboss.ejb.plugins.LogInterceptor.invokeHo
          me(LogInterceptor.java:121)
          16:30:41,072 INFO [STDOUT] at org.jboss.ejb.plugins.ProxyFactoryFinderInter
          ceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93)
          16:30:41,072 INFO [STDOUT] at org.jboss.ejb.EntityContainer.internalInvokeH
          ome(EntityContainer.java:508)
          16:30:41,072 INFO [STDOUT] at org.jboss.ejb.Container.invoke(Container.java
          :891)
          16:30:41,072 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke0(
          Native Method)
          16:30:41,072 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke(N
          ativeMethodAccessorImpl.java:39)
          16:30:41,072 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invo
          ke(DelegatingMethodAccessorImpl.java:25)
          16:30:41,072 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:5
          85)
          16:30:41,072 INFO [STDOUT] at org.jboss.mx.interceptor.ReflectedDispatcher.
          invoke(ReflectedDispatcher.java:144) .....
          


          • 2. Re: JBoss 4.0 & Entity Beans
            Sam Nasr Newbie

            You figured out what the issues were? I am curious what would cause CMP issues going from JBoss 3.2.1 -> JBoss 4.0.1.

            Thanks.

            • 3. Re: JBoss 4.0 & Entity Beans
              Sachin Shah Newbie

              No couldn't find te solution. Do post it here if you find anything

              Sachin