-
1. Re: Application failing after 3.0.4 to 3.2.5 upgrade
kabirkhan Jul 7, 2004 1:47 PM (in response to gseel)Your session bean class must contain the following method:
public void ejbCreate() throws CreateException{
}
Copied and pasted from the ejb spec section 7.10.3
7.10.3 ejbCreate methods
The session bean class must define one or more ejbCreate(...) methods whose signatures
must follow these rules:
• The method name must have ejbCreate as its prefix.
• The method must be declared as public.
• The method must not be declared as final or static.
• The return type must be void.
• The method arguments must be legal types for RMI/IIOP if there is a create<
METHOD>(...) corresponding to the ejbCreate(...) method on the
session beanÂ’s remote home interface.
• The throws clause may define arbitrary application exceptions, possibly including the
javax.ejb.CreateException.
Compatibility Note: EJB 1.0 allowed the ejbCreate method to throw the java.rmi.RemoteException
to indicate a non-application exception. This practice was deprecated in EJB 1.1—an EJB 1.1 or
EJB 2.0 compliant enterprise bean should throw the javax.ejb.EJBException or another RuntimeException
to indicate non-application exceptions to the Container (see Section 18.2.2). An EJB 2.0 compliant
enterprise bean should not throw the java.rmi.RemoteException from the ejbCreate method . -
2. Re: Application failing after 3.0.4 to 3.2.5 upgrade
gseel Jul 7, 2004 2:40 PM (in response to gseel)Thanks
So in 3.2.5 it isn't a warning although it says it is!
Seems to be solved by making the superclass (AFCWSessionBean) abstract.