WebSphere Application Server V6.1 Feature Pack for Enterprise JavaBeans 3.0 (EJB) allowed the EJB 3.0 binding file to contain duplicate binding names. The V7.0 server runtime environment added uniqueness checks on names used in the EJB 3.0 bindings file, ibm-ejb-jar-bnd.xml. It also validates that class names for session interfaces and interceptors are fully qualified. Applications with uniqueness errors do not start in V7.0 even though the same application worked on the Feature Pack for EJB 3.0.
This rule validates the EJB 3.0 bindings file to verify binding name uniqueness. It also validates that class names for session interfaces and interceptors are fully qualified.