Ou can use Java class inheritence when implementing your enterprise beans and push
the common functionality into the superclass.
What EJB currently does not have is the concept of "component inheritence". We are
looking into it as part of EJB 2.0.
Vlada
----- Original Message -----
From: Masters.Robert <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 17, 1999 3:39 PM
Subject: Inheritance and EJB
> Greetings all. I have a number of EJB's that are going to require access to
> some standard information. Ie for the userIdentiry get the User EJB (useful
> in some cases), get the system date etc. Pretty much generic information
> that is going to be used across a wide variety of beans. Currently these
> general "utility like" methods are done in a stateless session bean (as some
> db access is required etc). I have been thinking on creating a EJB
> superclass that implements my generic methods. However the spec states EJB
> not to support inheritance. As the methods I will be creating are generic,
> they should have no bearing on ejbCreate etc so is it good practice to use
> inheritance to solve this issue? and/or are there any other patterns to
> effecting such approaches as shared behaviour amongst ejb's?
>
>
> Regards
>
> Rob Masters
> Sun Certified Java Programmer
> Sun Certified Java Developer
>
> Comcare Australia
> (w) 02 6275 0632
> (f) 02 657 4045
> [EMAIL PROTECTED]
> http://www.comcare.gov.au
>
> ===========================================================================
> 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".
>
>
===========================================================================
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".
