You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@synapse.apache.org by stlecho <st...@gmail.com> on 2008/06/24 09:18:40 UTC

Re: ServiceMix website explaination for difference with Synapse

Is this "more balanced comparison" somewhere available ?

Regards, Stefan Lecho.


pzfreo wrote:
> 
> LiChung
> 
> In fact because Synapse also supports REST, any XML message over any
> transport can be brokered by Synapse. In addition, we can also route and
> mediate message that use MTOM to encode binary data.
> 
> I don't think you can completely rely on the view promoted by the
> ServiceMix
> team. I will try and put together a more balanced comparison.
> 
> Paul
> 
> On 2/1/06, Davanum Srinivas <da...@gmail.com> wrote:
>>
>> Yes, that statement is wrong. each endpoint can have ANY soap stack
>> that implements the WS-* specifications needed.
>>
>>
>>
>> On 2/1/06, LiChung Liu <li...@gmail.com> wrote:
>> > Hi I'm new to the list, and have question about the difference between
>> > ServiceMix
>> > and Synapse, please let me know if I'm asking the qustion on the wrong
>> list.
>> >
>> > I know this question probably has already been asked, but my question
>> is
>> > regarding
>> > this:
>> >
>> > http://servicemix.org/How+does+ServiceMix+compare+to+Synapse
>> >
>> > More specifically, the paragraphs:
>> >
>> > "...Building an SOA on Apache Synapse would presume that all exchanges
>> > in the SOA would be Web Service exchanges based on SOAP, that the
>> > management of the exchanges would be invoked exclusively by means of
>> > WS-*, and that the underlying SOAP technology at each brokered endpoint
>> > would be Apache Axis2.
>> >
>> > ServiceMix is a full ESB that can work with many different SOAP Stacks
>> such
>> > as
>> > Axis, WSIF, XFire, ActiveSOAP and JAX-WS...."
>> >
>> > I'm abit confused by the statement "at each brokered endpoint would be
>> > Apache Axis2".
>> > First, is this statement correct?  If it is, why would this be the
>> case?
>> If
>> > Synapse acts
>> > as a broker that relies on the WS-* in the SOAP header, then shouldn't
>> any
>> > other
>> > technology (like .NET) that has the same ability be able to
>> send/receive
>> > messages
>> > with Synapse?
>> >
>> >
>>
>>
>> --
>> Davanum Srinivas : http://wso2.com/blogs/
>>
> 
> 
> 
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> 
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
> 
> "Oxygenating the Web Service Platform", www.wso2.com
> 
> 

-- 
View this message in context: http://www.nabble.com/ServiceMix-website-explaination-for-difference-with-Synapse-tp2704121p18085308.html
Sent from the Synapse - User mailing list archive at Nabble.com.


Re: ServiceMix website explaination for difference with Synapse

Posted by Ruwan Linton <ru...@gmail.com>.
Hi Stefan,

No. For the moment there is no comparison AFAIK. But we have made a friendly
request to update that page in the servicemix site and Guillaume Nodet has
accepted that and promised to change the content.

At the same time we will also provide a comparison of Synapse with compared
to mule and servicemix soon. (May be as a blog post)

Thanks,
Ruwan

On Tue, Jun 24, 2008 at 12:48 PM, stlecho <st...@gmail.com> wrote:

>
> Is this "more balanced comparison" somewhere available ?
>
> Regards, Stefan Lecho.
>
>
> pzfreo wrote:
> >
> > LiChung
> >
> > In fact because Synapse also supports REST, any XML message over any
> > transport can be brokered by Synapse. In addition, we can also route and
> > mediate message that use MTOM to encode binary data.
> >
> > I don't think you can completely rely on the view promoted by the
> > ServiceMix
> > team. I will try and put together a more balanced comparison.
> >
> > Paul
> >
> > On 2/1/06, Davanum Srinivas <da...@gmail.com> wrote:
> >>
> >> Yes, that statement is wrong. each endpoint can have ANY soap stack
> >> that implements the WS-* specifications needed.
> >>
> >>
> >>
> >> On 2/1/06, LiChung Liu <li...@gmail.com> wrote:
> >> > Hi I'm new to the list, and have question about the difference between
> >> > ServiceMix
> >> > and Synapse, please let me know if I'm asking the qustion on the wrong
> >> list.
> >> >
> >> > I know this question probably has already been asked, but my question
> >> is
> >> > regarding
> >> > this:
> >> >
> >> > http://servicemix.org/How+does+ServiceMix+compare+to+Synapse
> >> >
> >> > More specifically, the paragraphs:
> >> >
> >> > "...Building an SOA on Apache Synapse would presume that all exchanges
> >> > in the SOA would be Web Service exchanges based on SOAP, that the
> >> > management of the exchanges would be invoked exclusively by means of
> >> > WS-*, and that the underlying SOAP technology at each brokered
> endpoint
> >> > would be Apache Axis2.
> >> >
> >> > ServiceMix is a full ESB that can work with many different SOAP Stacks
> >> such
> >> > as
> >> > Axis, WSIF, XFire, ActiveSOAP and JAX-WS...."
> >> >
> >> > I'm abit confused by the statement "at each brokered endpoint would be
> >> > Apache Axis2".
> >> > First, is this statement correct?  If it is, why would this be the
> >> case?
> >> If
> >> > Synapse acts
> >> > as a broker that relies on the WS-* in the SOAP header, then shouldn't
> >> any
> >> > other
> >> > technology (like .NET) that has the same ability be able to
> >> send/receive
> >> > messages
> >> > with Synapse?
> >> >
> >> >
> >>
> >>
> >> --
> >> Davanum Srinivas : http://wso2.com/blogs/
> >>
> >
> >
> >
> > --
> > Paul Fremantle
> > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> >
> > http://bloglines.com/blog/paulfremantle
> > paul@wso2.com
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/ServiceMix-website-explaination-for-difference-with-Synapse-tp2704121p18085308.html
> Sent from the Synapse - User mailing list archive at Nabble.com.
>
>


-- 
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/