One of the key things about a module is that a module defines the
boundary of visibility. In other words, components in a module cannot
directly reference out and cannot be directly referenced by
*components* in other modules. All references go through entry points
and external services (except when doing Module.locateService from a
non-component resource). One issue that was brought up is being able
to have a non-component resource do Module.locateService on two
different modules.
Jim
On Feb 9, 2006, at 5:46 PM, Jeremy Boynes wrote:
hung tran wrote:
hello all,
i'm wondering if dynamic invocation of components is possible.
As I've been only testing Tuscany on Tomcat, it currently seems
that i
would need to be in the same webapp as the component i'm trying to
invoke.
What i would like to do is be able to invoke any component in any
module
from basically anywhere within the server.
Yes, we basically only have intra-module (where a module has the same
scope as a webapp) running at the moment. The current flurry of
changes
from Jim will add subsystem support that enables us to combine
multiple
modules (webapps) into one subsystem (Tomcat server) with wires
between
them and call from one application to another as easily as from one
component to another.
This is slightly different from dynamic invocation where a
component can
look up a service by name rather than by having a reference to it.
IIRC
this needs a little more work from the spec side before this can work
between modules. We will have that but it may be a while away.
--
Jeremy
