On 1/24/07, Jim Marino <[EMAIL PROTECTED]> wrote:
I've converted most of the binding and container extensions to reference the 0.1-pre-spec-SNAPSHOT kernel. Also, I started to convert the samples under java/samples/sca/ specifically: - calculator - echo.binding - inner.composite - loanappconversation - simplecallback - spring - spring.simple - supplychain I *did not* convert any of the web app, binding or container extension samples (with the exception of Spring). As part of the reorganized build tree outlined by Jeremy, these samples will be grouped with their respective extensions. It would be helpful if people working in those extension areas can take this move on as well as change the samples to refer to the kernel 0.1-pre-spec-SNAPSHOT. This will allow the extensions to be developed and released individually.
So if I was to go ahead and do this for things like Axis2 and the various dynamic language containers then what is the expected structure? Do they stay under services or move to new folder, and do they include things like the itests as well? For example: tuscany/java/sca/axis2/binding tuscany/java/sca/axis2/databinding tuscany/java/sca/axis2/itests tuscany/java/sca/axis2/samples tuscany/java/sca/axis2/tools Another question, so far the only things changed to use 0.1-pre-spec-SNAPSHOT are the containers, bindings, databindings, and samples, everything else, like other things in the services or the runtime folders haven't changed over. Is this just a point in time thing or is it not the intention to change them? I guess I'm not clear about if the kernel release is just the things in sca/kernel or if its also other things, and if so should there be some more restructuring of the folders? ...ant
