|Of course it is. The transitive closure *is* the scope.
...
(I am sure some are having a hell of a time with this discussion)
ok the CL grand daddy needs to be the System ones (the classes from
jboss.jar) but the CL that are associated with the Application (now that we
agree on the terms) are associated with the application and the jars/wars
shipped by the client.
It's irrelevant.
|Yes, and the scope of an ejb-link name becomes the system and not the
|local application in which it is used, hence it is the transitive
|closure of the system it is a child of.
Transitive closure of the modules making up the application, yes (client
modules)
|> That the parent CL is the "System" CL is another matter entirely,
|
|Nooooo, the system does not have a CL. The system does not have any
|concrete substance, it is just the structure of the applications. The
|nodes are the applications, but the links between them is the "system".
pffffff. can we agree on the "system" = jboss.jar classes? and associated
drivers, connectors etc etc?
system = JMX loaded server.
application = ContainerFactory (or to be written application factory) loaded
client modules
|> why this should be seen at the XML layer is beyond me :)
|
|We just use XML as a convenient way to denote how the applications
|relate.
not to the system rickard... we all agree that XML is the proper way to
describe the modules relationships
|Use a LISP notation if you prefer that. It doesn't really matter.
ok....
marc
|
|/Rickard
|
|--
|Rickard �berg
|
|Email: [EMAIL PROTECTED]
|
|
