[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    Re: Why the push to deprecate NMS-openwire?
From:       Clebert Suconic <clebert.suconic () gmail ! com>
Date:       2018-08-31 20:42:52
Message-ID: CAKF+bsok5x0FQLu5pxxLx87KoRw98N=fuToAcGnuKFCZ1SMv7w () mail ! gmail ! com
[Download RAW message or body]


You should probably raise an example on where it fails.  Someone may take a
look.

Why don't you start over with a question on user forums.  With an example.
If confirmed a bug open a JIRA.

Open source projects are maintained by the community.  As of now I have
seen most of the NMS contributions along AMQP. I haven't seen much activity
around open wire. But you can be part of the community and change that.


On Fri, Aug 31, 2018 at 1:08 PM dbeavon <dbeavon@ufpi.com> wrote:

> Thanks for all the helpful information.  I'm fairly new to using
> open-source
> projects so it was hard for me to phrase the right questions (ie questions
> without all the subtle and unintentional references to specific vendors,
> and
> the jboss issue-tracking site).
>
> I guess that the thing which I was most surprised by was that a vendor
> would
> independently claim to "deprecate" NMS even if that wasn't the direction of
> the community.  Furthermore it sounds like the behavior of the openwire
> protocol is actually more important than the NMS api which I interface with
> (at least where client-broker compatibility is concerned).  Since redhat
> continues to fully support the openwire protocol, then NMS really just
> comes
> along for the ride, whatever they may say about its deprecation.
>
> I suspect if I ran into a bug with NMS-openwire-on-artemis they would first
> make me reproduce it on JMS-openwire before offering full technical
> support.
>
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
>
-- 
Clebert Suconic


[prev in list] [next in list] [prev in thread] [next in thread]