I've changed the annotation processing callbacks
(ImplementationProcessor) to take the parent context of the
implementation to be visited as in:
void visitClass(CompositeComponent<?> parent,
Class<?> clazz,
PojoComponentType<JavaMappedService,
JavaMappedReference, JavaMappedProperty<?>> type,
DeploymentContext context) throws
ProcessingException;
This will allow us to contribute custom annotation processors
(implementations of ImplementationProcessor) that can inject a
property or reference based on access to the parent context, for
example, access to CompositeContext as defined in the SCA spec.
In order to do this, I had to change the signature of of things like
DeployerImpl to pass the parent composite through. Perhaps a better
long-term solution will be to add a method to DeploymentContext that
will return the parent composite, as that is also passed through. To
do this, we may need to refactor how deployment evaluates nested
composites as I believe it passes a single deployment context through
as child composites are processed.
Thoughts?
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
