0 Replies Latest reply on Dec 25, 2003 2:30 PM by kobezig

    difference in bcel.jar , xsltc.jar code not working in 3.2.2

    kobezig Newbie

      I have code that is not working in 3.2.2 or higher that works in 3.2.1

      here is the exception:

      2003-12-24 10:49:28,725 INFO [STDOUT] 175553 [TP-Processor3] DEBUG ServiceLocator - Exiting getEJBLocalHome(jndiHomeName), returning EJBLocalHome CustomerNameEJBLocalHome

      2003-12-24 10:49:28,795 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackLocalException in method: public abstract java.lang.Long com.taliantsoftware.framework.dto.Auditable.getUserIdCreated(), causedBy:

      javax.ejb.EJBException: Method is not a known CMP field accessor, CMR field accessor, or ejbSelect method: methodName=getUserIdCreated

      at org.jboss.ejb.plugins.cmp.bridge.EntityBridgeInvocationHandler.invoke(EntityBridgeInvocationHandler.java:106)

      at org.jboss.proxy.compiler.Runtime.invoke(Runtime.java:59)

      at CustomerNameBean$Proxy.getUserIdCreated()

      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

      at java.lang.reflect.Method.invoke(Method.java:324)

      I also have code that works well in 3.2.1 but need to upgrade to 3.2.2 or higher because there is a bug fix in optimistic locking that is required.

      I have also tried moving the old version of bcel.jar from jboss3.2.1 and that didnt fix things.

      It seems that others have had this problem but some were able to resolve this by ensuring that the same version of bcel.jar is used in jboss and the jdk.

      It seems for those using IBM jdk1.4.1 for linux there is a fix because bcel.jar is in one of the jar files.

      However for those (including myself) using windows and the sun jdk1.4.1 or higher there bcel.jar or xsltc.jar is nowhere to be found.

      Does anyone have the answer?

      Does anyone know the bugID of this in sourceforge.. if it has been reported.