Hi,

Please see my comments in line.

Thanks,
Raymond

----- Original Message ----- From: "Jeremy Boynes" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, January 26, 2007 11:29 AM
Subject: Model changes to support separate contributions


At the moment the Java configuration model contains references to artifacts associated with Java definitions - for example, JavaImplementation references the actual Class for the implementation. This works fine when all runtimes have access to the applicable contribution artifacts that provide these definitions but breaks down when we start to distribute the assembly model over a heterogeneous domain.


Agree.

To address this I am going to make changes to the model so that these definition references can be represented as simple types - for example, instead of using the actual Java Class, use its name and the id for the contribution that provides its bytecode.

In most of the cases, we can represent the references as either a URI or a qualified name as they are declared in the SCDL.


However, we still need information from these artifacts to determine things like the component type, to introspect bindings and other annotations, resolve autowires and verify composite structure. To support this, I plan to add two new phases to the deployment process: resolve and verify. The resolve phase will resolve these abstract definitions into concrete model objects e.g. actually loading the component type for an implementation. The verify phase will be responsible for verifying that any model change is valid to make so we can catch errors like duplicate component names.


I have been looking into the artifact addressing and resolving. I would like to contribute to this area once you have the two new phases added.

--
Jeremy



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to