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

List:       activemq-dev
Subject:    Re: [DISCUSS] Removing Rest from ActiveMQ Artemis
From:       Clebert Suconic <clebert.suconic () gmail ! com>
Date:       2022-09-22 20:07:09
Message-ID: CAKF+bspaG7pDJdjhDGuy+_wmEF3irvuy-8ohPD3ieOCq+e3X+A () mail ! gmail ! com
[Download RAW message or body]

As I said on the Voting Thread. Rest is an independent maven
component. Users have to consume it from maven on their own Rest
application.


So, they can still keep doing it from a previous release until they
decide to not use it any more:

https://github.com/apache/activemq-artemis/pull/4229


That's a good deprecating strategy I think.


The component is not part of the release distribution as far as I can tell.



On Thu, Sep 22, 2022 at 2:45 PM Clebert Suconic
<clebert.suconic@gmail.com> wrote:
>
> >>  Although I don't
> think anybody wants to invest the resources to bring all the dependencies
> up-to-date. <<
>
>
> until someone does that, I think it should be out.
>
>
> this is pretty much abandonware.
>
> On Thu, Sep 22, 2022 at 2:04 PM Justin Bertram <jbertram@apache.org> wrote:
> >
> > I've been meaning to get to this for awhile. Better late than never, right?
> >
> > Generally speaking, I agree that REST is not a great fit for messaging.
> > Whenever folks ask about it on the mailing lists, Slack, Stack Overflow,
> > etc. I strongly encourage them for two main reasons:
> >
> >  - The STOMP protocol is ubiquitous, simple, standardized, and can be used
> > in almost every circumstance and environment where REST might be used.
> >  - REST is not portable because there's no standard messaging interface for
> > REST. This is generally bad for users as it locks them in to a specific
> > broker.
> >
> > Here are a few additional reasons:
> >
> >  - For simple use-cases (e.g. basic send & receive) it's easy these days to
> > create your own REST interface and then implement messaging behind that.
> > Since the REST interface is in the user's control portability isn't an
> > issue.
> >  - It's a bit of a pain to setup as it requires manually building a WAR
> > file.
> >
> > That said, it **is functional**. All the REST tests in the test-suite are
> > passing, and I just ran through the documentation and tested it on a fresh
> > install of 2.25.0. Everything works as far as I can tell. Although I don't
> > think anybody wants to invest the resources to bring all the dependencies
> > up-to-date.
> >
> > Also, I think we should deprecate it and update the documentation with an
> > explanation before we completely remove it.
> >
> >
> > Justin
> >
> >
> > On Thu, Sep 8, 2022 at 9:04 AM Clebert Suconic <clebert.suconic@gmail.com>
> > wrote:
> >
> > > I'm not sure if there's much to discuss here. Rest in Artemis has been
> > > abandonware for a while (like 5 years)... The jboss-rest interface is
> > > a few major releases behind, the module compiles but it's not
> > > functional, and any time someone ask questions we just mention don't
> > > use it... (favoring stomp instead).
> > >
> > >
> > > https://github.com/apache/activemq-artemis/tree/main/artemis-rest
> > >
> > >
> > > As part of new logging changes, we are moving activemq-artemis into 3.0...
> > >
> > > At this point I see no other choice than remove the module.
> > >
> > > Any objections?
> > >
> > > --
> > > Clebert Suconic
> > >
> > >
>
>
>
> --
> Clebert Suconic



-- 
Clebert Suconic
[prev in list] [next in list] [prev in thread] [next in thread]