Edward Slattery wrote:
[snip]
In the case of SDO, it was just the logical pattern for implementation
hiding.
The implementation was fine up to the point where we wanted to start
thinking about
the static SDO api, and were proposing to allow code generators to
inherit
from some DataObject base class and add their own methods such as
"getName()" etc.
We cant do that with DataObject, as all the DataObject pointers given out
are really
DataObjectImpls. The prototype code I put in the test directory uses
containment instead
of inheritance to allow a MyDataObject to contain a reference to a
DataObject, and delegate
its DataObjectish behaviour.
cheers,
Ed.
Just to confirm I understand this correctly:
Are you saying that inheritance was the logical pattern for
implementation hiding in SDO?
But then this caused a problem for generated code? Can you describe the
problem with having the pointers inherit from DataObjectImpl vs contain
a DataObjectImpl?
Also if inheritance was the logical pattern for implementation hiding in
SDO, why wouldn't it work the same way for SCA?
Maybe I'm missing something but I'm not seeing why inheritance would not
work for ComponentContext as well. Could you please explain?
Thanks,
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
