Filter
Top Products
Chapter 2: Restrictions
2-6
Restrictions on the EJB Service
Table 2-5 Restrictions on the EJB Service
No. Restriction Remarks Date of
Removal
1 The long type data type cannot be used as an argument
or return value for the client/server communication.
None Not
determined
2 In JDK/JRE 1.2.2, any class in which String data of 64
KB or more is set to one variable in the class cannot be
used as an argument or return value for EJB
applications.
None Not
determined
3 In the client/server communication in JDK/JRE1.2.2,
when the interface shown below is used in business
method parameters and return value, the method for the
stored interface type cannot be issued. This is the case,
even if the interface type that can be communicated in
the application execution by the RMI over IIOP was
stored in that interface.
- java.util.Collection
- java.util.Enumeration
None Not
determined
4 When defining a Bean in the Rapid invoking Bean, if it
uses JDK/JRE1.2.2, the return value cannot use the
finder method of java.util.Enumeration or
java.util.Collection.
None Not
determined
5 Using "remove" as a business method name may lead
to unexpected results.
None Not
determined
6 When distributed transactions are used, if any of the
following methods from the javax.ejb.EJBContext API
are called from some particular methods, an
IllegalStateException will be thrown.
- getCallerIdentity()
- getCallerPrincipal()
- isCallerInRole(Identity role)
- isCallerInRole(String roleName)
If any of the above methods are called from one of the
following methods, an exception will be thrown.
- For STATEFUL Session Bean
beforeCompletion
afterCompletion
- For Entity Bean
ejbStore
None Not
determined