over to Framework as the WrapperServiceManager.
That is fixed now. No problem.
What would you think about moving the ComponentProxyGenerator over as well. Doing so would
remove the need for the Container package by the Component package (?) Seems to make
as much sense as moving the WrapperServiceManager class.
Cheers,
Leif
Leif Mortenson wrote:
Peter Donald wrote:Hi,Good idea. I went ahead and modified the ExcaliburComponentManagerCreator and
Could someone look at ExcaliburComponentManagerServlet. Has it ever been released? If no one objects, can I change the exporting of the ComponentManager into the Context into exporting of ServiceManager?
and ExcaliburComponentManagerServlet to provide access to a ServiceManager
object. The ComponentManager is still available, but it is now deprecated.
I also added a new AbstractServiceManagerServlet class and deprecated the
AbstractComponentManagerServlet class. These classes can be used to easily write
servlets which have immediate access to a Com.. (ahem) ServiceManager,
LoggerManager and InstrumentManager. They are also instrumented by default, making
it easy to do performance tests of servlets.
Take a look at my changes and let me know if you have any additional changes you
would like.
Cheers,
Leif
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
-- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
