On Tuesday, February 11, 2003, at 11:20 AM, Stephen McConnell wrote:
Not sure what you use-case is - but my understanding of the purpose of these classes is to aid migration from CM -> SM.That is the purpose. My use case is thus:
Cocoon running as a servlet inside of Sevak inside of Phoenix.
Cocoon is ECM-based and thus needs a parent ComponentManager, not ServiceManager. Since the services it will be accessing are all other phoenix blocks, which have the Component interface already added via a dynamic proxy, there is no need for anything beyond what the current implementation does.
Do you have a problem with these classes moving out of the framework and into a seperate jar? At least if we do that we can make sure we have a complete migration solution.Yes. As long as the current classes are documented as to their behavior, I do not believe they pose a problem. I have no problem with a separate jar providing a more robust wrapper though. I just do not see the need to remove the current, simple, wrappers.
-pete
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
