Hello all, I am currently researching EJB as the architecture on which to build the next phase of our product. Unfortunately, our product makes great use of inheritance for extending entities; not a strong point of EJB's from what I have seen so far. In particular there are issues with inheriting home interfaces (can't overload the findByPrimaryKey method if you want to use the same PK class for all entities - as the return types will be the same), and attempting to cast remote references that have been returned to a more specific type. With the latter, we have explored the possibility of some method on our base entity bean, called 'getRemoteReferenceToMostDerivedClass()' which would use some component of the primary key to find out the deepest class name of the entity bean, from which the home interface could be derived. findByPrimaryKey() could then be invoked and a more specific remote reference returned. The transaction and locking issues that could result boggle the mind however. I'm keen in discussing this matter further! Regards, James W. -------------------------------------------------------------------------- Visit us at Cards Australia 2000 on Stand 31A. Cards Australia will be held at the Melbourne Convention Centre from July 4-6 2000. -------------------------------------------------------------------------- This e-mail is from Cards Etc Pty Ltd (ACN: 069 533 302). It may contain privileged and confidential information. It is intended for the named recipient(s) only. If you are not an intended recipient, please notify us immediately by reply e-mail or by phone on +61 2 9212 7773 & delete this e-mail from your system. -------------------------------------------------------------------------- =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
