Thanks!
Leon
Marco Rolappe wrote:
hi again,
you can have it that factory way; implement a component/service whose sole purpose is to give you a ComponentManager/ServiceManager via a static method. have that component declare ThreadSafe (so there's only one instance of it and it gets instantiated at startup) and e.g. Servicable to receive a ServiceManager.
-----Ursprungliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von Leon Widdershoven Gesendet: Freitag, 9. April 2004 13:09 An: [EMAIL PROTECTED] Betreff: Re: AW: How to obtain the Manager, or a Component
Thanks,
it sounds pretty complicated. though, especially the configuration of cocoon.xconf. I have a problem declaring app specific data in the global context; it is unclean. I *was* hoping for a Cocoon.getInstance() or ServiceManager.getInstance() like construct. Alas.
I think I just use both standard java.sql libraries for testing and let my flowscript cocoon.getComponent( dbname ) pass the datasource to my objects for real - so much simpler.
The point is that implementing a change in cocoon.xconf requires that cocoon be restarted - which would bring all other applications off-line. Not a problem for the development version but a huge problem for the deployment server.
In any case, thanks for the quick and clear response.
Regards, Leon
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
