Справочник Пользователя для IBM SG24-6320-00
6320ch_DEV_post_migration.fm
Draft Document for Review July 28, 2004 7:33 pm
150
Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
If one of the ejbCreate methods in your entity bean is not declared to return an
object of the primary key type, WebSphere Studio Application Developer V5.1.1
will show the following warning in the Tasks panel:
object of the primary key type, WebSphere Studio Application Developer V5.1.1
will show the following warning in the Tasks panel:
CHKJ2406W: The method should return the primary key type <BeanName>Key.
(EJB 1.1: 9.2.3,9.4.2,9.4.7.3)
(EJB 1.1: 9.2.3,9.4.2,9.4.7.3)
Where
<BeanName>
is the name of the bean, including the java package.
Remove java.rmi.RemoteException from remote methods
As per EJB 1.1 specification, throwing java.rmi.RemoteException from the
following methods have been deprecated:
following methods have been deprecated:
ejbCreate
ejbPostCreate
ejbActivate
ejbPassivate
ejbLoad
ejbStore
ejbRemove
All remote methods
The exception
java.rmi.RemoteException
was used in EJBs following the EJB
1.0 specification to indicate non-application exceptions.
If a non-application exception needs to be signalled to the EJB container, the
remote method should throw the
remote method should throw the
javax.ejb.EJBException
or another unchecked
exception. An unchecked exception is an exception that derives from
java.lang.RuntimeException
and that does not need to be declared in a
throws
clause for the method.
For some of the mentioned methods, if they have
java.rmi.RemoteException
in
their
throws
clause, WebSphere Studio Application Developer V5.1.1 will show
the following warning for the method in the Tasks panel:
CHKJ2400W: Deprecated use of a java.rmi.RemoteException (EJB 1.1: x.y.z)
Note: As the
ejbCreate
method on session beans must have return type void,
they are not encompassed by this change. See section 6.10.3 of the EJB 1.1
specification for details on
specification for details on
ejbCreate
methods for session beans.
Note: This change only pertains to the use of
java.rmi.RemoteException
. Any
application specific exceptions may be declared for, and thrown in, the
mentioned methods.
mentioned methods.