> Harkness, David [mailto:[EMAIL PROTECTED]
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> once said: > > [ I'm trying to use inheritance with EJB entity beans ... ] > > > > Have I missed some subtlety of the EJB spec or XDoclet? > > I think you missed the part of the EJB spec that says, "Do > not attempt to use standard object-oriented concepts like > inheritance and polymorphism with entity beans unless you are > criminally insane." For lack of evidence, let us assume > insanity and go from there. Is that EJB or XDoclet speaking? I've had no problem with using inheritance before, without XDoclet. The ejb-jar.xml file doesn't have a problem with it, as it knows what class of bean its dealing with and has no problem with superclass returns. And it does seem to be something that XDoclet should be doing. Otherwise why insist on having a fully qualified signature in @ejb.finder signature if it's just going to be overwritten? Lets just assume insanity. > My angle of attack so far has been to handle these issues in > the session bean layer. This is what I have been doing. But it's as ugly as a drunken bridegroom. Huge gobs of unmaintainable if-then-elses. ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
