Dims, (I appologize if this doesn't "thread" properly. I'm replying to a message in a digest as I wasn't a subsciber to this list until a few minutes ago. I'm not sure how well that works.)
> Are u with me so far? > > - CeltixFire's vision is to be a SOA Infrastructure project with all > things pluggable. > - CeltixFire aims to include both ServiceMix and Tuscany I'm not sure if "include" is the right word here. More like "integrate with" or "provide services to" or similar. I don't expect CeltiXfire to ship copies of Tuscany or ServiceMix. > - ServiceMix and Tuscany both support multiple soap engines AFAIK. > > Again, Are u with me so far? > > So, why is it a crime to ask if Axis2 can be one-of-many pluggable > soap engine in a "SOA Infrastructure" project? > Where did my logic go haywire? You didn't "go haywire" and you are completely correct. In the future as we go forward, there is no reason why we wouldn't be able to plug an Axis 2 based soap stack into CeltiXfire. Just "not right now" only due to technical reasons related to timing. We're already busy trying to get our heads around two large code bases, merging them together, figuring out differences/similarities, etc.... As anyone that has tried that before knows, that's enough of a headache. Throwing a third piece of technology would cause even more headaches (and delays). Likewise, in the future, we hope to work with other Apache projects like Synapse and others to integrate CeltiXfire capabilities into those projects. If the stacks in those projects are truely "pluggable" (aka, not directly tied to Axis 2), that should be possible and welcome from those projects. Tuscany was just one of the first instances where we've done that from the Celtix team. (we have also done some work with Geronimo, Petals, JOnAS, etc..., but I don't know all the details on those) I believe ServiceMix and several others have done so with XFire. Anyway, once we've completely moved the codebases to apache (assuming acceptance) and finished (strong word, more like "come close to stabilizing") the integration/merger stuff, we'd definitely welcome help in providing alternative plugins, additional capabilities, other improvements. Accepting those contributions is a very important part of the community, especially as we try to grow the community, foster discussions, etc... The other thing we will be working on is helping those other projects "upgrade" to the new CeltiXFire code. Since we are merging codebases, there WILL be API changes (obviously, all the package names change to org.apache), idea changes, etc... and we hope to be involved with the other projects in guiding/helping them to use the newer apache based code instead of/in addition to the older ObjectWeb/Codehaus code. Those are good question and very valid concerns. I hope this helps alleviate some of them. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 F:781-902-8001 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
