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.
2) LoaderRegistry doesn't have an "unregisterLoader()" method to unregister
ComponentTypeLoader. Is it automatically removed when the
ImplementationLoader is delisted?
3) What's the replacement for "org/apache/tuscany/core/config/**" which uses
to host the class like "Java5ComponentTypeIntrospector"?
Thanks,
Raymond
----- Original Message -----
From: "Jeremy Boynes" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, May 24, 2006 11:16 AM
Subject: Re: svn commit: r409076 - in
/incubator/tuscany/sandbox/jboynes/sca/containers/container.spring: ./ src/
src/main/ src/main/java/ src/main/java/org/ src/main/java/org/apache/
src/main/java/org/apache/tuscany/ src/main/java/org/apache/tuscany/containe
On 5/24/06, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi, Jim/Jeremy.
I don't see XXXImplementationLoader (except SystemImplementationLoader)
any
more in the sandbox code. Are they just not implmented or do we now have a
new model to populate the implementation metadata based on the bean
properties for the implementation class?
I am still porting loaders over from the current core and help doing
that would be appreciated (e.g. JavaImplementationLoader). One
difference with these is that the LoaderRegistry has been enhanced to
support componentType loading so the implmentation loader can call
back for that rather than having to do it itself.
I don't see TuscanyRuntime either, what's the new way to bootstrap
Tuscany?
I am actively working on this. I am refactoring the bootstrap process
to get rid of the remaining duplicate code in the different host
environments (j2se, tomcat) and introduce an extensible bootstrapper.
I'm also separating the loaders/builders used during bootstrap from
those that will be used once the runtime is up - this will provide
full configuration of the deployment infrastructure from SCDL rather
than as a mixture of Java code and SCDL.
I also added a "launcher" that allows a J2SE application to be
bootstrapped without requiring the Tuscany runtime on the classpath -
this will help prevent library conflicts between applications and our
implementation.
Sorry to ask questions on the sandbox code, but it would be really helpful
for me to understand the new contract.
Keep asking ...
--
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]
