You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by clymbon <cl...@gmail.com> on 2007/12/14 17:27:27 UTC
Re: Servicemix WSN SE deployed to OpenESB
MowPed wrote:
> We've for the most part successfully deployed the Servicemix-wsn service
> engine to OpenESB.
My questions:
1) Have you succeeded in getting servicemix-wsn2005 working in OpenESB?
2) If so can you provide tips on what must be done to get this to work?
3) I understand this is a Service Engine, not a Binding Component. I want
to publish my notification
messages outside the JBI engine, to subscribers on other machines. I want
to do this using JMS
and a MoM implementation (e.g. ActiveMQ) - in the hopes of getting better
performance. Since
this is an SE not a BC, how do I do this? Do I have to write or use another
BC? If so, how do I
configure it? (The ServiceMix documentation provides some information on
exposing the
pub/sub service using SOAP/HTTP, but nothing on exposing it via JMS/MQ)
Any information on your experience would be much appreciated before I launch
into this!
Oh, one last question:
4) Anybody aware of any other implementations of WS-Notification (or any
other standards-based
publish/subscribe technology suitable for use in a WS-based SOA
environment)?
Background to my questions:
We have an existing WS-Notification based application implemented
using Muse. We would like to try a different implementation to see if we
get better performance.
(We are pushing the performance limits of this technology with our
application.) It
appears that servicemix-wsn2005 is about the only other open source
implementation there is.
I started trying to get it running in ServiceMix, but the documentation is
bad and even the "basic"
examples don't build and run. Realizing it's an open-source project, I
could bite the bullet and try
to get it working, but we already have begun another project in OpenESB, so
I'd rather just use that.
Thanks,
Duncan
--
View this message in context: http://www.nabble.com/Servicemix-WSN-SE-deployed-to-OpenESB-tp13283404s12049p14339070.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Servicemix WSN SE deployed to OpenESB
Posted by Guillaume Nodet <gn...@gmail.com>.
The WS-Notification engine only use the JMS api, but it still leverage some
activemq specific features, mainly for the "on demand" publishing.
So in effect, when you publish a message or create a subscriber, the
WS-Notification broker will send a jms message to the given topic or create
topic subscriber. So the link is the topic name. If you publish a message
using the WSN broker, you can directly receive it by subscribing to the same
topic using jms. The opposite is true too. So this is really a bridge
between the WS-Notification spec and JMS.
I also the use case for using WS-Notification and JMS at the same time, but
using WS-Notification over soap, over jms sounds a bit weird to me. It
would be the same as using WS-ReliableMessaging over JMS: it just does not
bring any value.
On Dec 14, 2007 6:21 PM, clymbon <cl...@gmail.com> wrote:
>
>
> gnodet wrote:
> >
> > Is there a real need for you to use WS-Notification on top of JMS ?
> > WS-Notification brings to the http layer the semantics of JMS, but
> there's
> > no real added value compared to just using JMS imho.
> > The ServiceMix WS-Notification SE uses ActiveMQ underneath, and fwiw,
> you
> > can communicate from one to the other directly without going through JBI
> > for
> > that.
> >
>
> You're right - I don't really care about JMS at all. But let me see if
> I've
> go this straight...
>
> What I care about is using a MoM rather than HTTP for the publication of
> messages to my subscribers, in the hope (yet to be proven) that it will
> perform better for distributing my notifications to subscribers.
>
> When I wrote that I wanted to use WS-Notification over JMS over MoM, this
> was based on the understanding that the SericeMix WS-Notification SE used
> JMS as an API to ActiveMQ. But I'm unclear as to how things are put
> together. I guess from your response that my assumption was wrong, and
> that
> the ServiceMix WS-Notification SE uses a "native" API to ActiveMQ. Am I
> understanding you correctly? If so, that's fine with me, I want to use
> ActiveMQ, I don't really care about JMS.
>
> Or were you asking why I would use WS-Notification at all, rather than
> just
> writing my application to go straight to JMS or some underlying MoM API
> for
> my publish/subscribe application? That's a different question, and the
> answer has to do with trying to stick to WS-* standards. Frankly, the
> case
> for using WS-Notification, or WS-anyghing for that matter, is still rather
> weak. But that's another whole debate - for various reasons I'm trying to
> stick to web service standards for this project. (For now, anyway!)
>
> Just trying to figure out all my options here...
>
> Thanks,
>
> Duncan
>
>
> --
> View this message in context:
> http://www.nabble.com/Servicemix-WSN-SE-deployed-to-OpenESB-tp13283404s12049p14339703.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Servicemix WSN SE deployed to OpenESB
Posted by clymbon <cl...@gmail.com>.
gnodet wrote:
>
> Is there a real need for you to use WS-Notification on top of JMS ?
> WS-Notification brings to the http layer the semantics of JMS, but there's
> no real added value compared to just using JMS imho.
> The ServiceMix WS-Notification SE uses ActiveMQ underneath, and fwiw, you
> can communicate from one to the other directly without going through JBI
> for
> that.
>
You're right - I don't really care about JMS at all. But let me see if I've
go this straight...
What I care about is using a MoM rather than HTTP for the publication of
messages to my subscribers, in the hope (yet to be proven) that it will
perform better for distributing my notifications to subscribers.
When I wrote that I wanted to use WS-Notification over JMS over MoM, this
was based on the understanding that the SericeMix WS-Notification SE used
JMS as an API to ActiveMQ. But I'm unclear as to how things are put
together. I guess from your response that my assumption was wrong, and that
the ServiceMix WS-Notification SE uses a "native" API to ActiveMQ. Am I
understanding you correctly? If so, that's fine with me, I want to use
ActiveMQ, I don't really care about JMS.
Or were you asking why I would use WS-Notification at all, rather than just
writing my application to go straight to JMS or some underlying MoM API for
my publish/subscribe application? That's a different question, and the
answer has to do with trying to stick to WS-* standards. Frankly, the case
for using WS-Notification, or WS-anyghing for that matter, is still rather
weak. But that's another whole debate - for various reasons I'm trying to
stick to web service standards for this project. (For now, anyway!)
Just trying to figure out all my options here...
Thanks,
Duncan
--
View this message in context: http://www.nabble.com/Servicemix-WSN-SE-deployed-to-OpenESB-tp13283404s12049p14339703.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Servicemix WSN SE deployed to OpenESB
Posted by Guillaume Nodet <gn...@gmail.com>.
Is there a real need for you to use WS-Notification on top of JMS ?
WS-Notification brings to the http layer the semantics of JMS, but there's
no real added value compared to just using JMS imho.
The ServiceMix WS-Notification SE uses ActiveMQ underneath, and fwiw, you
can communicate from one to the other directly without going through JBI for
that.
Anyway, you'd need to create a SU for the JMS BC (either the OpenESB one or
the servicemix one) and wire it with the WS-NotificationBroker.
On Dec 14, 2007 5:27 PM, clymbon <cl...@gmail.com> wrote:
>
> MowPed wrote:
> > We've for the most part successfully deployed the Servicemix-wsn
> service
> > engine to OpenESB.
>
> My questions:
>
> 1) Have you succeeded in getting servicemix-wsn2005 working in OpenESB?
>
> 2) If so can you provide tips on what must be done to get this to work?
>
> 3) I understand this is a Service Engine, not a Binding Component. I want
> to publish my notification
> messages outside the JBI engine, to subscribers on other machines. I want
> to do this using JMS
> and a MoM implementation (e.g. ActiveMQ) - in the hopes of getting better
> performance. Since
> this is an SE not a BC, how do I do this? Do I have to write or use
> another
> BC? If so, how do I
> configure it? (The ServiceMix documentation provides some information on
> exposing the
> pub/sub service using SOAP/HTTP, but nothing on exposing it via JMS/MQ)
>
> Any information on your experience would be much appreciated before I
> launch
> into this!
>
> Oh, one last question:
>
> 4) Anybody aware of any other implementations of WS-Notification (or any
> other standards-based
> publish/subscribe technology suitable for use in a WS-based SOA
> environment)?
>
> Background to my questions:
>
> We have an existing WS-Notification based application implemented
> using Muse. We would like to try a different implementation to see if we
> get better performance.
> (We are pushing the performance limits of this technology with our
> application.) It
> appears that servicemix-wsn2005 is about the only other open source
> implementation there is.
>
> I started trying to get it running in ServiceMix, but the documentation is
> bad and even the "basic"
> examples don't build and run. Realizing it's an open-source project, I
> could bite the bullet and try
> to get it working, but we already have begun another project in OpenESB,
> so
> I'd rather just use that.
>
>
> Thanks,
>
> Duncan
>
>
> --
> View this message in context:
> http://www.nabble.com/Servicemix-WSN-SE-deployed-to-OpenESB-tp13283404s12049p14339070.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/