On Aug 3, 2006, at 7:49 AM, Yang Lei (JIRA) wrote:
Need a extendable way to register SCDL loaders
----------------------------------------------
Key: TUSCANY-593
URL: http://issues.apache.org/jira/browse/TUSCANY-593
Project: Tuscany
Issue Type: Improvement
Components: Java SCA Core
Affects Versions: Java-M1
Environment: windows XP
Reporter: Yang Lei
Please let me know if Tuscany offers extendable way to register
SCDL loaders , so we can always use the root of the loader such as
ModuleLoader to load a SCDL without manually register each
individual loader. The problem with this approach is if some one
add an extension to the SCDL, we also needs to know the new loader...
Our modularity story is based on people being able to provide
extensions that are complete in themselves. For example, someone
would provide an extension for a new implementation type (like
JavaScript) or a new binding (like RMI). Each extension hooks into
the runtime at three points:
1) a loader that handles extension-specific XML elements
2) a builder that creates extension-specific components
3) the runtime components that hook into the wiring fabric
Each extension is packaged as a composite which can be <included> in
another or which can be deployed into the system. When the composite
starts, all the components it contains register themselves with the
appropriate registries in the runtime (e.g. the LoaderRegistry).
How each extension is registered is determined by the host
environment. In M1 this was done by adding system.fragment
definitions to the classpath; in trunk this is done through extension
components such as the DirectoryScanExtender.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
