RE: Problem with TurbineAvalonComponentService

[Eric Pugh <ep...@upstate.com>]

I ran across a similar problem..  To initialize only once, your component
needs to implement the ThreadSafe marker interface.  This will cause the
init to be called only once for your component when running in Excalibur.

The reason we have Excaliber only right now is that what was contributed.
There is also a MerlinComponentService as well, however it needs completion.
To be honest, I don't see why Turbine can't support multiple containers, so
that people can use what they like.

I would love to see some updated containers..  Either use Fortress, or
finish up the MerlinCompoenentService (which is where we really need to be).
It just takes someone willing to do the work (hint hint!).

My schedule is a little full right now, and I am pretty much just have time
to work on the pipeline stuff, but I will happily review and commit any
patches.

Eric

> -----Original Message-----
> From: David Wynter [mailto:david@roamware.co.uk]
> Sent: Sunday, February 29, 2004 9:51 PM
> To: Turbine-User
> Subject: Problem with TurbineAvalonComponentService
>
>
> I have 4 services using the AvalonComponent service. The
> standard Torque use
> of it and 3 other. For one of them I use exactly the same
> lookup calls the
> other 2 I have added to Turbine.  It looks like this
>
> 			TurbineAvalonComponentService tacs =
> (TurbineAvalonComponentService)
> TurbineServices.getInstance().getService("AvalonComponentService");
>
> 			try {
> 				blissedservice =
> (DefaultBlissedManager) tacs.lookup(
>
> "com.blah.rwtransform.avalon.blissed.BlissedManager");
> 			} catch (ComponentException e) {
> 				log.info("Failed to load the
> Blissed component - " +
> 					e.getMessage());
> 			}
>
> The problem occurs in Excalibur, everytime the lookup is used
> it calls the
> services' Initialize method, which is incorrect. If my
> understanding is
> correct the service should have Initialise called once when
> starting up, not
> each time it is looked up.
>
> Trouble is that it seems that Excalibur is deprecated in
> favour of Fortress,
> so I cannot get the source code anymore to trace into it to
> find out what is
> wrong. Does anyone have the source code? Also why is Turbione
> using this
> deprecated container?
>
> I am on JSDK 1.4.1, W2K and Turbine 2.3
>
> Thanks,
>
> David Wynter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org