------------------------------------------------------------------------
r64114 | vivishal | 2015-09-22 00:58:59 -0700 (Tue, 22 Sep 2015) | 3 lines

EjbDescriptor abstract class implements JndiNameEnvironment and WritableJndiNameEnvironment. For some of these methods, though there is a generic implementation (For example via CommonResourceDescriptor), these methods still needs to be implemented in a specific way within EjbDescriptor abstract class to get the expected behavior whenever these methods are invoked in EjbDescriptor's context. To ensure the same, a new unit test is being introduced within source workspace, namely EjbDescriptorInheritedMethodImplementationTest,which basically ensures following two things: All methods defined in JndiNameEnvironment and WritableJndiNameEnvironment have a direct implementation within EjbDescriptor abstract class and all these methods are marked final in EjbDescriptor to ensure that sub-classes of EjbDescriptor don't override these methods accidentally, possibly causing unexpected behavior.
The changes have been reviewed and approved by Bill Shannon. Build, quick look and ejb dev test run went fine with this change.

------------------------------------------------------------------------
r64115 | romain_grecourt | 2015-09-22 09:09:35 -0700 (Tue, 22 Sep 2015) | 1 line

exclude test from report if unable to get record
------------------------------------------------------------------------