On May 24, 2006, at 3:04 PM, Jeremy Boynes wrote:
On 5/24/06, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi,
Thanks for the explanations.
I can help to port/develop the implementation/componentType
loaders. As the
first step, I'm trying JavaImplementationLoader and
JavaComponentTypeLoader.
Here're a few more questions/comments:
1) ComponentTypeLoader.load(...) should take DeploymentContext in
addition
to Implementation.
Yes - it was late last night :-)
2) LoaderRegistry doesn't have an "unregisterLoader()" method to
unregister
ComponentTypeLoader. Is it automatically removed when the
ImplementationLoader is delisted?
No, we need to add unregister methods here (again it was late :-) )
and on the BuilderRegistry as well
3) What's the replacement for "org/apache/tuscany/core/config/**"
which uses
to host the class like "Java5ComponentTypeIntrospector"?
Jim added a more general annotation processing framework into core in
the trunk. The component type loaders should use that for
introspecting the implementation.
Yea the idea with that is it's visitor based which allows people to
extend it with custom processors (i.e. the runtime doesn't know about
any annotations). Jeremy mentioned he was going to plug this into the
load process, so when that's done we can look at how that fits into
the loader work.
--
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]
