RE: ContainerManager and Sub-containers

[Leo Sutic]

> From: Berin Loritsch [mailto:[EMAIL PROTECTED]] 
>
> Either that, or have child containers that specialize an area.

Automatic instantiation of child containers for components that
require it? Would work.

So we have:

Component A requires component B, component C requires component B. A
wants a
B differently configured from C, for example, while A wants a
DBConnectionPool
to jdbc:A, C wants it to jdbc:C. So A and C can not use the same B.
Component
D uses A and C.

Solution:

  Container
     |
     +-- D
     |
     +-- Subcontainer(A)
     |        |
     |        +-- B
     |        |
     |        +-- A
     |
     +-- Subcontainer(C)
              |
              +-- B
              |
              +-- C

OK, so for D, a lookup(A.ROLE) will do this: lookup (A) in the mapping, 
determine that it is a subcontainer, and grab the primary component (A).

/LS


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>