On 10/7/06, Jim Marino <[EMAIL PROTECTED]> wrote:
On Oct 7, 2006, at 10:42 AM, Jim Marino wrote: > > On Oct 7, 2006, at 7:22 AM, ant elder wrote: > >> This is all working quite well now so i'd like to move it from my >> sandbox to >> be with the other containers. BSF 2.4 has just come out and the >> jar is >> available from a proper maven repo and the script container >> supports all the >> SCA things like references, properties and async, also the start of a >> website page describing it which I'll move to the site once its a >> bit more >> done: >> https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/ant/ >> container.script/doc/sca-java-container-script.xml >> >> https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/ant/ >> container.script/ >> https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/ant/ >> container.easy/ >> > I'm fine with this as long as the name of "container.easy" can be > changed to something that denotes it has to do with scripting, > something like "container.bsf". > After looking at the code more instead of having something separate, why wouldn't we look to see if we can merge the "easy container" into the extension API? I'd like to get a clearer direction on this before we move things around. Specifically, I have a few questions related to this: 1. Is this container just for scripting? It appears not to be tied to scripting 2. What value does this container provide over the extension API? Does it automate certain coding tasks only relevant to a subset of containers or all containers? Could we just merge such automation with AtomicComponentExtension 3. There appears to be a bit of code duplication, some of which may be a vestige from the Groovy container which needs to be refactored. For example, AsyncInvoker. In a merge, maybe we could eliminate the need for this? Jim
Way back I was moaning about the complexity of the SPI and it was suggested having a separate extension project for a simplified SPI for extensions with simpler requirements. I can't find a link, maybe the 1st sandbox phone call or an old IRC chat? Thats where this came from. Its not quite finished yet, there's some parts that could be simplified further. I'd also like to do the same thing for bindings but haven't got to that yet. This is not necessarily tied to only scripting containers but thats all we've tried it with so far, and as Venkat suggests there likely is a bit more work required to make it more generally useful. There probably are some parts that could be moved to existing SPI classes, but there are also parts that may be a bit inflexible to be made part of the general extension SPI. As you point out the async bit does seem pretty isolated so that probably could be easily moved out. Given we're trying to get an M2 release out real soon I'm not sure about messing with the existing SPI classes now. How about for now moving the obvious bits like async out but keeping the rest in say a separate container.helperproject or in a separate SPI package like org.apache.tuscany.spi.extension.container? ...ant ...ant
