Berin Loritsch wrote:
Nicola Ken Barozzi wrote:You lost me here.
>
> Berin Loritsch wrote:
>
>
> What about all the client code that checks for Component and won't find it in the Cocoon components, and the ones that extend Cocoon components?
It won't break compilation. Cocoon component interfaces extend the
(Component) interface so all the clients have to do to release is
m_manager.release(foo);
We want to remove depecation warnings. Or we remove @deprecated, or we remove Component from the Cocoon component interfaces.
If we do the latter, as Vadim points out, this is not going to work for our users:
Component c = ((ComponentSelector)manager.lookup(Generator.ROLE + "Selector")).select("something");
Basically all the code that casts to Component will stop working.
I'm trying to see all the tradeoffs.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
