Carsten Ziegeler wrote: ...
I strongly suggest that we start with org.apache.cocoon.* to avoid these problems down the road (including, yes, gump problems)
Yes, I understand of course all these problems, but I'm really afraid
of changing all the components now from Avalon interfaces to Cocoon
interfaces which are more or less the same but just use a different
package. In that case these components run in Cocoon but not in any
other container anymore that provides Avalon compatibility. And
that's imho bad. Not every project uses Cocoon, so it's absolutely preferable to have components that I can use in several projects.
Ok, I think if we decide to use our own versions of the interfaces it will still be possible to do some hacky things and still provide compatilibity with the Avalon versions.
So what do others think?
Cocoon components will never work putside of Cocoon. Non-cocoon components should not use the Cocoon interfaces.
I don't see the problem, as long as we don't mix all like we did with Avalon.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------