>Has anyone lived through this? Or are all EJB projects tackled by
>members of this list so far simply one-off client solutions without any
>intention of reuse of the beans involved?
I've been working on a project with similar goals, so I appreciate your
frustration. I believe the right solution is for the EJB spec to evolve to
support inheritance of EJBs, and that is one of the items in the JSR for
EJB2.0 so I am hopeful that it will be addressed soon.
I think the advice others gave about making the leaf classes be the only
EJBs is appropriate if you need to deliver EJBs now that have no dependency
on EJB server support beyond the scope of the EJB1.1 spec. The project
I've been working on doesn't have that restriction, so we've been using
inheritance of EJBs, and counting on the spec to address it relatively soon
so that our EJBs can become fully spec compliant then.
Erik Voldal
Email: [EMAIL PROTECTED]
Phone: 507-253-4788
===========================================================================
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".
