Daniel Rall <[EMAIL PROTECTED]> writes:
Hi,
as far as I can understand, Velocity nowadays can be instantiated
multiple times, no?
But I understand that the current Velocity Service cannot be used with
different configurations.
This actually poses an interesting question: Shall the avalonized
services have the "singleton" lifecycle pattern just as our services
or should it be possible to request components multiple times creating
multiple instances (and running into possible trouble).
Regards
Henning
>Henning P. Schmiedehausen wrote:
>> Daniel Rall <[EMAIL PROTECTED]> writes:
>>
>>
>>>EmailService is basically a copy of VelocityService, but we needed a
>>>different configuration. I'm hoping that this is something that an
>>>Avalon container can help with.
>>
>>
>> Can you describe what this does in difference to the Velocity Service?
>Scarab's EmailService is functionally equivalent to VelocityService. It
>was created because we needed a separate instance of Velocity's
>RuntimeInstance which uses a separate configuration. EmailService was
>created so that that instance would be configured and fired up by
>Fulcrum initialization (i.e. lifecycle managed). Since VelocityService
>uses the singleton pattern and a separate configuration was need, it was
>impossible to use...thus my allusion to Avalon.
> - Dan
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
"Dominate!! Dominate!! Eat your young and aggregate! I have grotty silicon!"
-- AOL CD when played backwards (User Friendly - 200-10-15)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
