You'll need t ask Jeremy on bootstrapping but you don't need to
bootstrap the container to test you component extensions - the Spring
and Groovy examples show how to do this.
The Groovy issue was brought up on this list earlier and it's not
related to Tuscany at all. It's a problem with the
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
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
Jean-Sebastien Delfino wrote:
- 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:
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
