I think I may have answered my own question. I believe the module name I referred to is the module implementation name. But a ModuleComponent (MC) is a configured instance of a module, and so one could have multiple MC's with a given module implementation.
I think once subsystem support is added (it's not there yet, right?), then this will be clearer. For now there is sort of an implied subsystem around all the MC's and the host environment (e.g. Tomcat) is resposible for naming MC's somehow. Sound good? Scott On 6/26/06, Scott Kurz <[EMAIL PROTECTED]> wrote:
I was wondering why there isn't an option to derive a module component's name from the name attribute on the <module> element in SCDL. All the methods defined on the ModuleComponentConfigurationLoader interface, e.g. loadModuleComponent(String name, String uri), require the client to pass in a module component name. This seems like a natural option and an alternative to coming up with an environment-specific mechanism for keeping track of the MC names registered on the runtime's root context. Or is there some reason why this would be a bad thing? Thanks, Scott Kurz
