We get lots of EJB failures with AVK relating to the EJB 2.1 specification. However, the EJBs that we are testing are 1.1 EJBs. AVK seems to assume that they are 2.1 EJBs. Each module has its own EJB 1.1 ejb-jar.xml descriptor.
How can we get AVK to correctly test our 1.1 EJBs?
On the basis of deployment descriptor, AVK 1.4.2 should automatocally figure out the version and exclude running EJB 2.1 rules for your app. Can you provide details about the kinds of failures you are seeing?
The EJBs are currently deployed on Borland Enterprise Server (BES). We are migrating them to WebSphere Application Server v6 (WAS) and want to make sure that they conform to the standard because WAS is strict. The EJBs function correctly with BES.
Examples of failures are below. There are several others.
Methods used in exclude-list must be methods defined in the enterprise bean's remote and/or home interface. Please refer to EJB 2.1 Specification Section #21.3.2 for further information.
Methods used in [unchecked] must be methods defined in the enterprise bean's remote and/or home interface. Please refer to EJB 2.1 Specification Section #21.3.2 for further information.
Role name conforms to lexical rules of NMTOKEN. Please refer to EJB 2.1 Specification Section #23.5 for further information.
An application exception must not be defined as a subclass of java.lang.RuntimeException or of java.rmi.RemoteException in home interface methods. Please refer to EJB 2.1 Specification Section #18.1.1 for further information.
You said your EJB is an EJB 1.1 application. Are you sure you are using EJB 1.1 deployment descriptor? I am saying this because, AVK reported about exclude-list element. I don't think exclude-list element was not present in ejb-jar_1_1.dtd. It was introduced in ejb 2.0 dtd. Can you check your deployment descriptor?
Secondly, although AVK report contains references to EJB 2.1 spec, the rules are usually applicable to previous versions of the spec.