Hi folks,
remembering the following pieces
http://excalibur.apache.org/apidocs/org/apache/avalon/framework/component/Component.html
http://wiki.apache.org/excalibur/ExcaliburHistory (How Components Became
Services)
IMHO it seems reasonable to remove the Component ...
Cheers,
Siegfried Goeschl
Carsten Ziegeler wrote:
Leo Simons wrote:
Ah, it seems like you took out the "implements Component" nearly
everywhere.
This will break all applications using excalibur components with a
container that depends on "Component" being implemented. Removing an
implements interface can also break stuff like serialization...
I think that unless there's a really good reason for it, you should
roll these back :-/
The reason is to remove the dependency to avalon interfaces from the
components interface and make them "real" independent interfaces.
Now, I thought that all avalon implementations can cope with a component
not implementing the Component interface today. And if there are
solutions out there, they could for example stick to the old version?
So the idea is to "pojofy" the compoents stuff from excalibur.
What do others think about it?
I can revert the stuff, if required, no problem.
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
