> Exactly! What's wrong with handing off your partially implemented
> domain, letting the consultant subclass some of the classes for
> white-box reuse and then GENERATE THE ENTITY BEANS using a tool? From
> my reading of this list, it seems that many people feel that the best
> thing is for the Entity bean to wrapper the domain object anyway, so
> this would lend itself to tool use. If your EJB server does not include
> one, then your group could create one without too much trouble.
Having to write a tool to generate my code tells me the model is broken.
> And then where EJB shines is for your group to create COMPONENTS that
> the consultants can use without subclassing, that might provide for
> common functionality that pops up.
This is fine, as long as it covers the majority of cases. However, it
is overshadowed by any fatal flaw of the model.
> The issues that you brought up exist in every component model.
Every component model fails to support inheritence?
tim.
===========================================================================
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".
