> >Since we would really like to have an autoload
> >feature of components. I'd propose the following:
> >
> > <component class="org.apache.something" autoload="true">
> > <parameter name="test" value=""/>
> > </component>
> >
> >In configure
> >
> > componentManager.configure(conf)
> >
> >the componentManager is supposed on autoload="true" to
> >do a subsequent lookup of this component (or whatever
> >is appropriate to create an instance of this component)
> >
> >Is this a possible sollution?
>
> I am not sure I understand you - could you expand?
> Cheers,
Well, although I don't really need it any longer (since
Cocoon2 now loads all it's components on startup)
I still think it is a useful feature to decide inside
the configuration the startup time of component.
For what I understood the configuration only defines/registers
components to the manager. A flag to tell the component
manager e.g. "at least one instance should be created" the
time it is defined would be reasonable IMHO - particular
for runnables...
See what I mean now?
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
