My orginal mindset is that we need some context for the resolving,
for example, a resolver might use the classloader to resolve
relative URIs.
Isn't DeploymentContext designed for Load/Resolve/Build?
With the federated architecture, we can't assume DeploymentContext
anymore or that the steps above occur in the same VM. I posted a
message earlier today outlining some of this but the key thing is
that building happens on slave nodes and it is against a
PhysicalChangeSet, not the logical model. The logical model will be
handled on the Controller, which will also be responsible for
resolution, normalization, and generation of PhysicalChangeSets sets
comprising PhysicalComponentDefinitions, PhysicalWireDefinitions, and
PhysicalResourceDefinitions. This will be marshalled across to the
appropriate nodes.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
