Berin Loritsch wrote:
Leo Sutic wrote:
I was thinking... Could we remove the @deprecated tags from the classes in question and just leave it with a note in the JavaDocs saying that the service.* package is much much better and that you should use it
instead unless you have a reason not to?
As I understand it, every container must support ComponentManager,
Composable, etc. anyway... At least until Avalon 5.
True, but can't we do it in the same manner that Phoenix, Fortress, and Merlin all do it? Either we upgrade to JDK 1.3 minimum requirements, or we need to add in a utility class to use BCEL for the dynamic component proxies.
ECM does have dynamic proxy generation (JDK 1.3 compliant). The JDK 1.3 dynamic proxy version can be replaced with a BCEL enabled proxy generator and all will be well if it is absolutely a requirement to stay with JDK 1.2. There is no need to repeal the deprecation. However we should extend the framework JavaDocs to explain how to live without it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
