Ryan Shaw wrote:
> Berin wrote:
>
> ||| When designing it, I had in mind that the Container would
> ||| have a special interface that you would call to handle whatever
> ||| request you needed.
>
> <snip>
>
> ||| This would allow you to use it like this:
> |||
> ||| void service( ServletRequest request, ServletResponse response )
> ||| {
> ||| Environment env = new Environment( m_servletContext, request, response );
> ||| Processor proc = (Processor) m_containerManager.getContainer();
> |||
> ||| proc.process( env, request.getRequestURI() );
> ||| }
>
> Okay, I see what you had in mind now. However, it seems that the
> Container implementation (Processor in this example) still needs
> access to the child ComponentManager. So am I correct that the
> visibility of m_childManager in AbstractContainer needs to be
> changed from private to protected?
:/
Possibly, or maybe better a protected getter for the ComponentManager.
----------------------------------------------------
Sign Up for NetZero Platinum Today
Only $9.95 per month!
http://my.netzero.net/s/signup?r=platinum&refcd=PT97
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
