Noah Clements wrote:
> 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?
Nothing is really wrong with it, in the sense that that will certainly
work. It's more work for the consultant than other framework-based
solutions I've given in the past, where the consultant subclasses maybe
2 out of every 10 classes of a set of, say, 200 to implement custom
behavior--in which he only typically overrides two methods. In your
example, lots of what the consultant will have to do is boring, tedious,
entirely avoidable work if only EJBs could inherit from one another.
Cheers,
Laird
===========================================================================
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".
