Jeremy, > A project "core" that: >........ > Baseline services that are distributed with the core that: >........ > Baseline extensions that are distributed with the core: > * programming models that are part of the specification > (currently Java, futures being C++, Spring, J2EE, BPEL, ...)
How come you broke those sections up in the above part, but in the project structure, you lumped them all together.... > # "baseline" services and extensions > sca/baseline/service/monitor > sca/baseline/service/security > sca/baseline/service/transaction > sca/baseline/service/work > sca/baseline/container/java > sca/baseline/transport/axis2 > sca/baseline/data/sdo > sca/baseline/policy/security Next question: where would something like my celtix transport/binding thing go? I suppose into "optional", but it's really designed as a replacement for the axis2 one. If we (Celtix folks) were to ship a version of tuscany with our distribution, we probably wouldn't ship the Axis stuff. Thus, does axis belong at the same level as the true "core" services? Mostly just throwing out some thoughts.... -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED]
