In addition to the three previous errors, when I add the throws clause to the ejbCreate and ejbPostCreate methods, I get the following error:
./medinex/server/entitybean/JOnASMDXAccountingCodeBean.java:56: unreported exception javax.ejb.CreateException; must be caught or declared to be thrown
super.ejbCreate(p1, p2, p3, p4);
^
Is there some other way I need to be "defining" the CreateException? Also, how would that help with the RemoveException and the DuplicateKeyException?
-----Original Message-----
From: Philippe Coq [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 07, 2001 12:08 AM
To: Skidmore, Walt
Cc: '[EMAIL PROTECTED]'
Subject: Re: New error...
> "Skidmore, Walt" wrote:
>
> So, this means that I now have to make all of my beans conform to the
> EJB2.0 spec rather than the EJB1.1 spec that they already conform to?
No, I think there is a misunderstanding of my last mail.
I was only saying that we have thought it was important
to catch CreateException or DuplicateKey exception correctly
because some users ask us to fix the problem.
The only modification to do is to modify the throws clause
of ejCreate (and ejbRemove)in a way that will be conform to the EJB2.0.
> I tried adding the required throws onto the method declaration (e.g.
> public MDXAccountingCodeKey ejbCreate(...) throws RemoteException,
> CreateException, DuplicateKeyException), and it actually created
> another error. Is there some other way I need to be defining
> javax.ejb.CreateException? Why the switch to the EJB 2.0 spec?
>
Can you be more precise on the exact error you have?
regards,
--
Philippe
Philippe Coq Evidian Phone: (33) 04 76 29 78 49
Bull S.A - 1 rue de Provence - 38432 Echirolles Cedex France
Download our EJBServer at http://www.objectweb.org
