Jim Marino wrote:
Which code base are you intending to use: the M1 which implements the "old" .9 spec or the sandbox one which implements support for the new recursive model, or both?

In terms of how to specifically improve the extensibility story, my opinions have been embodied in the sandbox code and presentation Jeremy and I gave the other week (there are several slides providing high-level overviews of how to extend things) :-) Comments on that approach would be appreciated.

Jim

On Jun 19, 2006, at 6:25 PM, Jean-Sebastien Delfino wrote:

In order to better understand our extensibility story and how we can improve it for M2, I'd like to experiment a little with our extensibility APIs and try to develop two simple extensions: - a jruby implementation extension (I won't be starting from scratch, we already have an initial implementation, but I'll try to add support for properties, references, lifecycle management, and deployment maybe)
- a simple TCP/IP (socket) binding implementation

I'll bring any questions and issues I run into and improvement proposals on the mailing list and I'm thinking about keeping track of this on a Wiki page as well.

I'm going to start with the component implementation extension. If anybody wants to help and start the TCP/IP binding extension, please let me know and we can coordinate (I think we'll find common techniques and patterns between the two).

--Jean-Sebastien


---------------------------------------------------------------------
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]


I'm starting with both. Interestingly most of the differences between the two sets of SPIs are not related to the spec changes to support recursive composition, I found this surprising.

I'm also going to propose, in the form of prototypes, improvements to the SPIs, there are good (and less good) things in both code streams, and I'd like to try to combine the best of both.

Right now I'm prototyping this with the head stream, as I don't see yet how to run a simple sample with the code in sandbox, I'm running into the following issues:

- I cannot find TuscanyRuntime anymore, has this been removed? has the mechanism for a client to bootstrap the runtime changed? is there a sample anywhere?

- I was counting on the groovy container that you pointed me to yesterday to understand better the new SPIs but I'm not able to build it, the test cases fail with: java.lang.NoSuchMethodError: org.objectweb.asm.ClassVisitor.visit(IILjava/lang/String;Ljava/lang/String;Ljava/lang/String;[Ljava/lang/String;)V at org.codehaus.groovy.classgen.AsmClassGenerator.visitClass(AsmClassGenerator.java:317) at org.codehaus.groovy.control.CompilationUnit$7.call(CompilationUnit.java:690) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:956) at org.codehaus.groovy.control.CompilationUnit.classgen(CompilationUnit.java:629) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:464) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:300) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:262) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:257) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:233) at org.apache.tuscany.container.groovy.GroovyAtomicComponent.createInstance(GroovyAtomicComponent.java:77)

--
Jean-Sebastien


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

Reply via email to