I've been using EJB2.0 beans (including container managed relationships)
with considerable success for several months now. It works (mostly).
Don't give up :-)
I haven't seen that particular error message, but I have noticed that
occasionally Orion screws up the deployment and forgets to
recompile/rebuild something. I get a lot of milage out of wiping out my
application deployment directory and letting Orion rebuild from scratch.
Watch out if you have a lot of changes to your deployment xml files,
though. You may just need to delete the deployment cache and restart
the server.
More than likely, though, you have something misspecified in your
deployment descriptor. Make sure you read the comments in Sun's EJB2.0
DTD thoroughly.
If this doesn't help, you can try posting your deployment descriptor.
Good luck,
Jeff Schnitzer
[EMAIL PROTECTED]
>-----Original Message-----
>From: Peter Pontbriand [mailto:[EMAIL PROTECTED]]
>Sent: Friday, December 08, 2000 1:03 PM
>To: Orion-Interest
>Subject: EJB2.0 Generated class uncompilable
>
>
>Hello All.
>
>We've just written our first pair of 2.0-spec EJBs and are
>experiencing some
>really strange problems deploying them. Orion 1.4.4
>auto-generates the DB
>tables for these beans, but then spits out the following
>message for every
>CMP field in each EJB:
>
>_______________________________________
>
> 6. public class FooBean_PersistenceManager22 extends
>com.foo.components.authorization.bean.FooBean implements
>ContainerManagedObject
> <-------------------------------------->
>*** Error: The abstract method "void setBar(java.util.Set
>$1);", inherited
>from type "com/foo/components/authorization/bean/FooBean", is not
>implemented in the non-abstract class
>"FooBean_PersistenceManager22". Since
>the type "com/foo/components/authorization/bean/FooBean" was
>read from a
>class file, it is possible that it just needs to be recompiled
>because after
>having inherited method "void setBar(java.util.Set $1);" from
>an interface,
>the method was subsequently removed from that interface.
>Error compiling file:/C:/orion/applications/foo/admin-ejb.jar: Error in
>source
>_______________________________________
>
>We're totally at a loss here. What's removing what from what interface?
>There's no indication in the message of what the problem is in
>the source.
>We've already spend an incredible amount of time trying to sort out
>extremely cryptic deployment error messages with 1.1 and now
>2.0-spec CMP
>Entity EJBs. We're definitely beginning to wonder whether
>there is any point
>to CMP at all - it seems like we could have ported BMP Entity
>EJBs to quite
>a number of different DBs in the time its taken to try and
>deal with CMP
>problems like this.
>
>Anybody have any light to on this latest problem?
>
>P. Pontbriand
>Canlink Interactive Technologies Inc.
>
>
>
>
>
