> There is not any difference between a container and a component (as far
> as a component implementation is concerned)- the difference rest on how
> the component (acting as a container) is handled by its appliance. In
> the case of a component acting as a container - it is handled by a Block
> - which adds the notions of separation of published services from its
> internal component structure (implementation).
I probably do a mistake (I'm a poor english reader/writer :-( ) could
tell me what is the right interpretation :
schema :
Conatiner Root
+--Component A
+--Container B
+--Component B.A
+--Component B.B
+--Container B.C
+--Component B.C.A
+--Component B.C.B
+--Container C
+--Component C.A
+--Component C.B
+--Component D
a) service provide by internal component are accessible by other
component (and container) children of the same container but not by
sibling component or container of parent/ancestror container :
* Component B.A could access : Component A, Component B.B, Container
B.C, Container C, Component D
* Component B.A couldn't access : Component B.C.A, Component B.C.B,
Component C.A, Component C.B
b) service provide by internal component are accessible by other
component of the same conatiner (but not children) and by sibling
componaent or container of parent/ancestror container :
* Component B.A could access : Component B.B, Container B.C, Component
B.C.A, Component B.C.B
* Component B.A couldn't access others.
--
--------------------------------------------------------------
David "Dwayne" Bernard Freelance Developer (Java)
mailto:[EMAIL PROTECTED]
\|/ http://dwayne.java-fan.com
--o0O @.@ O0o-------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
