On Wed, Feb 07, 2001 at 10:20:57PM -0800, Jon Stevens wrote:
> on 2/7/01 8:58 PM, "Java Apache CVS Development" <[EMAIL PROTECTED]> wrote:
>
> > just wanted to make sure this is noted. i'm cognizant that
> > making the servlet config a static field in the TurbineBaseService
> > is not ideal but i think what it provides is useful.
>
> Actually, I'm -1 on this. The issue is that having it static will prevent
> other Service based systems that point to different ServletConfig objects
> from being able to work within the same Classloader.
>
> Turbine has two cases of using a ServletConfig object. Either through
> TurbineConfig or through the ServletConfig object that is handed to us from
> the Servlet Container...
>
> Please find a better way to implement this. :-)
Is this another argument for breaking this functionality out into a
ContextService, as per Raphael's suggestion? It would seem to be a clean
way of doing it, although it involves adding another Service which other
services are dependent upon a la LoggingService and ResourceService...
Sean
--
Sean Legassick
[EMAIL PROTECTED]
Ek is 'n man: niks menslik is vreemd vir my nie
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
