Make sure the Component also implements one of the lifestyle
interfaces:
SingleThreaded (instantiated by factory method)
ThreadSafe (one instance shared)
Poolable (multiple instances recycled after use)
The ComponentManager in Excalibur makes the safest assumption
it can in the absence of these: it assumes the Component is
SingleThreaded.
The implications of choosing the lifestyle of choice are:
SingleThreaded: Creation is delayed until you actually request
it. There is never a Component in reserve.
ThreadSafe: It is created on initialization, and the one instance
is shared between all requesters.
Poolable: It is created on initialization with multiple instances.
as it is requested, unused instances are given to the
client.
Torsten Curdt wrote:
>
> > > > Also, is our TODO list up to date?
> > >
> > > Well, could someone please help and have
> > > a look at the sub sitemap error?
> > > (I need this to work real badly)
> > >
> > > Or proove I'm wrong...
> >
> > It's fixed. The 2.0 branch got broken during the
> > code merge--and 2.1 was never updated properly.
> > It should work for you now.
>
> It does!! Berin, I officially want to state that I love you ;))
> Well, at least a thousand thanks for the fast fix!!
> This night I can sleep well again...
>
> One more question regarding the Components load on startup:
> My component now implements Component, Configurable, Composable
> and Contextualizable. I see the role in the logs but no
> instance is created - well, at least
>
> void configure(Configuration conf)
>
> is never called. Are the components only initialized and
> not configured on startup? Or what have I missed?
>
> Thanks!!
> --
> Torsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
