On Jul 25, 2006, at 7:24 PM, Scott Kurz wrote:
So the method I was referring to had signature:
ModuleComponent loadModuleComponent(String name, String uri)
The replacement is
Component<?> deploy(CompositeComponent<?> parent,
ComponentDefinition<I> componentDefinition)
where the parent determines which composite the new component will be
added to and the definition contains things like the name of the
component etc.
The name and uri are not calculated by Tuscany, and not implicit in
the
SCDL.
They are supplied by the host in the definition being deployed.
Maybe I should have phrased my question: will Tuscany's host API
support
registration of Composite Context name and uri supplied by the host
environment?
For now we do name. Adding URI should be easy once we figure out what
it should be (from the spec) - in 0.9 we mostly ignored it.
Maybe this will be one option among several, including some where the
name,uri are supplied by Tuscany or calculated somehow.
Depends what you mean by "Tuscany" - the core will never take a guess
at these, it will always use values supplied to the deployer. They
could be specified by the user, or they could be determined by the
deployment environment (for example, the directory scanner uses the
filename sans extension as the component name).
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
