Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-tck-dev] How are we grouping EJB 2.x view test requirements?


On 2/25/21 8:25 PM, David Blevins wrote:
Per the Jakarta Enterprise Beans spec the original EJB 2.x remote interfaces are marked optional.  These optional tests are distinct and orthogonal to any CORBA topics.  Do we have these somehow grouped in the TCK and is this grouping (if it exists) separate from any CORBA-related tests?

None of the optional EJB 2.x tests are directly using org.omg.CORBA.ORB (or any org.omg.CORBA class).

We have a ejb_2x_optional test group which are the following test packages:

com/sun/ts/tests/ejb/ee/bb/entity/cmp20, com/sun/ts/tests/ejb/ee/deploy/entity/cmp20, com/sun/ts/tests/ejb/ee/bb/entity/cmp20

We have a ejb_1x_optional tests group which are the following test packages:

com/sun/ts/tests/ejb/ee/bb/entity/bmp, com/sun/ts/tests/ejb/ee/bb/entity/cmp, com/sun/ts/tests/ejb/ee/bb/entity/lrapitest, com/sun/ts/tests/ejb/ee/bb/localaccess, com/sun/ts/tests/ejb/ee/bb/localaccess/ebaccesstest, com/sun/ts/tests/ejb/ee/deploy/entity/bmp, com/sun/ts/tests/ejb/ee/deploy/entity/cmp11, com/sun/ts/tests/ejb/ee/bb, com/sun/ts/tests/ejb/ee/deploy, com/sun/ts/tests/ejb/ee/pm, com/sun/ts/tests/ejb/ee/sec, com/sun/ts/tests/ejb/ee/timer, com/sun/ts/tests/ejb/ee/tx

The only tests that are directly using org.omg.CORBA.ORB are under the `com/sun/ts/tests/ejb30` package (none of these are in the optional EJB 2.x test group.


The background of this question is in relation to PortablRemoteObject.narrow calls, which are currently a requirement users must meet to portably use EJB 2.x remote interfaces.  Support for EJB 2.x remote interfaces is optional and this is unrelated to their choice in if they do or do not use CORBA.  For example:

 - A server that choses to support CORBA may still chose not to support EJB 2.x remote interfaces, opting to only use their CORBA support to enable EJB 3.x remote interface views.

 - A server that choses not to support CORBA may chose to support EJB 2.x remote interfaces, in which case they must ensure PortablRemoteObject.narrow is present.

Either way, this axiom is currently true:

 - If an application uses EJB 2.x remote interfaces it must also use PortablRemoteObject.narrow as it does not know if the target server does or does not use CORBA.

Where discussions are currently if we were to keep PortablRemoteObject.narrow, we would need it tied to an implementation's decision to support the optional EJB 2.x interfaces.  We would not be able to tie PortablRemoteObject.narrow calls to any CORBA-related flags or settings as has been previously discussed.

Thanks for mentioning the background here so all can follow!  For others, the ejb-dev ml discussion is at https://www.eclipse.org/lists/ejb-dev/msg00176.html

Scott

Back to the top