Hi ,

     I am not aware of the environment and hence I don't understand how the
IDE regenerates the mapping etc

     But on the same lines I fail to understand why using interfaces should
not work :

     If it is an issue of maintaining common behaviour across structurally
( different schema  / logic etc  )

     Why can't  'Contact' be an interface that Insured and Collector
implement with only one hiccup that I see : Primary key Type needs to be
the same in the 'Account' entity bean. If the entity bean is using value
objects anyway other attributes are encapsulated in there and can have
their own object graph

     To me if the IDE or CMP is proving to be a barrier they are only
secondary in nature... Primary being performance/maintainability

I am not sure if I understand the problem fully...
Thanks for any comments
Vaidya




                    Victor Langelo
                    <victor@ECLIPSESER       To:     [EMAIL PROTECTED]
                    VICES.COM>               cc:
                    Sent by: A mailing       Subject:     Re: Using Entity Beans for 
multiple projects
                    list for
                    Enterprise
                    JavaBeans
                    development
                    <EJB-INTEREST@JAVA
                    .SUN.COM>


                    10/24/2002 09:59
                    AM
                    Please respond to
                    Victor Langelo






Juan Pablo Lorandi wrote:
          I recommend you consider using different classes for Client A
          and Client B. It is true that this will prevent the automatic
          reuse of any changes that you make to these classes in the
          future, but it will significantly reduce the complexity of
          extending the class in a manner that is consistent with the
          needs of both clients.

     I tend to agree. This has always been the major drawback of white-box
     reuse, inheritance, in OO enabled languages, especially whenever the
     "owner" or coder that maintains the class changes.
This is Bull S---. Charles' use of inheritance is one of the very classic
uses of OO languages, i.e. a framework. The real problem here the
limitations of the IDE.

--Victor

===========================================================================
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".

Reply via email to