> 1) Is CeltiXFire planning to create an intermediary runtime or support > endpoints or both? CeltiXfire is focused on service creation and service consumption capabilities at the endpoint. The architecture is flexible enough to be used in either way - we are not trying to build to a particular constraint in that regard (i.e. neither solely endpoint oriented nor solely intermediary). Because of it's multi-protocol, multi-transport architecture it can be used as a protocol switch, i.e. taking a message in as one format over one transport and then creating a new service with a different format over a different transport based on the payload of the incoming service, i.e. SOAP over JMS to CORBA over IIOP. The current architecture is WSDL centric with SOAP plug ins (including Xfire so far), and open to collaboration with other projects (Tuscany, Geronimo, ServiceMix so far for example) that could use Celtix as a component within an ESB, application server etc. On top of this the value that we bring to Apache is the close alignment with the Java community specifications.
On the topic of Synapse, I am very interested in seeing (once we move to Apache after acceptance etc..) both communities working together on integrating CeltiXfire and Synapse. I know Synapse is tightly coupled with Axis 2 (Correct me if i am wrong), Is synapse community open to making it work with CeltiXfire? Thanks, Adi Sakala > -----Original Message----- > From: Paul Fremantle [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 22, 2006 12:39 PM > To: general@incubator.apache.org > Subject: Re: [PROPOSAL] CeltiXfire Project > > > I think there is a very clear distinction between an intermediary > (like a JBI container, Mule, ServiceMix, Synapse, etc) and a Web > Service client and server framework. While I agree with you that the > term ESB is pretty vacuous, it is clear that all the ESB code out > there fits into the world as some type of intermediary/mediation > model. You can take Mule, ServiceMix, Synapse (or WebSphere ESB, or > AquaLogic) and deploy them *between* two existing endpoints. > > The standards that are quoted (JAX-WS/JAX-WSA/JSR-181) are not about > building intermediaries/brokers but instead about building and > deploying endpoints. > > So I have two clear questions about the proposal. > > 1) Is CeltiXFire planning to create an intermediary runtime or support > endpoints or both? > 2) Given the "meaninglessness" of the term ESB, maybe the Celtix team > could clearly articulate what *they* mean when they say Celtix is an > ESB? > > Thanks > Paul > > > > > 6/22/06, James Strachan <[EMAIL PROTECTED]> wrote: > > Lots of people use the ESB word these days to talk about lots of > > different kinds of technology, so its a pretty meaningless > term. (e.g. > > Some Synapse folks claim its an ESB too while others claim its an > > Axis2 mediation framework). > > > > So its better to focus on the specifications which are the > aims of the > > project rather than these woolly marketing terms like ESB & > SOA which > > don't really mean anything ;) > > > > On 6/22/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > > > On Thu, 2006-06-22 at 17:30 +0200, James Strachan wrote: > > > > > > > > CeltixFire is aimed at implementing the JAX-WS/JAX-WSA/JSR-181 > > > > standards which are the newer standards for working with SOAP & > > > > WS-Addressing on the Java platform > > > > > > Thanks for the clarification. So its basically an > alternate to Axis2 as > > > we are working on all these specs there too; which of > course is cool .. > > > alternates are a good way to figure out different ways of > skinning a cat > > > and eventually we'll find the right way (hopefully before the cat > > > dies ;-)). > > > > > > I thought XFire does all these specs too > > > (http://xfire.codehaus.org/Stack+Comparison; except for obviously > > > JAX-WSA as that's not even done yet). So what part of > Celtix (other than > > > the name) is in Celtixfire in that case? > > > > > > However, I'm not certain Iona folks look at it as just an > impl of these > > > specs- at least that's not the impression I've gotten so > far. Adi or any > > > of the Iona folks can you indicate what exactly > Celtixfire is from your > > > point of view? Celtix is still marketed as an ESB and > James' picture > > > doesn't quite fit. From http://celtix.objectweb.org/: "Celtix 1.0 > > > provides users with a feature-rich, open source ESB > runtime that can > > > support any organization's adoption of Service Oriented > Architecture > > > (SOA) in the enterprise." > > > > > > I'm confused exactly what Celtixfire is going to be. > > > > > > Sanjiva. > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > > > James > > ------- > > http://radio.weblogs.com/0112098/ > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Paul Fremantle > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair > > http://bloglines.com/blog/paulfremantle > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
