You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Emmanuel Hugonnet <eh...@redhat.com> on 2019/05/15 15:14:35 UTC
JMS compatibility issue
Hello,
When integrating Apache Artemis 2.8.0 with prefixes activated we can see a change in behavior on the JMSDestination header as it now returns
a value with "jms.queue." or "jms.topic." prefix.
This is no longer compliant with JMS :( Could we have a quick release with this fix as it is currently blocking our own release ?
Thanks
Emmanuel
Re: [HEADS-UP] ActiveMQ 1.8.1 release WAS: JMS compatibility issue
Posted by Clebert Suconic <cl...@gmail.com>.
yes... 2.8.1... thanks!
On Wed, May 15, 2019 at 2:06 PM Justin Bertram <jb...@apache.org> wrote:
>
> You mean 2.8.1 rather than 1.8.1, right?
>
>
> Justin
>
> On Wed, May 15, 2019 at 12:50 PM Clebert Suconic <cl...@gmail.com>
> wrote:
>
> > I would like to do a release tomorrow, to help with Wildfly release.
> >
> > I would really like to have Wildfly using an official release. In the
> > past they had forked and created their own release.
> >
> > so, for that I will release it tomorrow, which will include
> > https://github.com/apache/activemq-artemis/pull/2669
> >
> > Any objections?
> >
> > if anyone have any pending changes on their workspaces, we can always
> > have another release later. the more the merrier as they say in
> > English.
> >
> > On Wed, May 15, 2019 at 11:38 AM Clebert Suconic
> > <cl...@gmail.com> wrote:
> > >
> > > Sorry, wrong link:
> > >
> > > https://github.com/apache/activemq-artemis/pull/2669
> > >
> > > On Wed, May 15, 2019 at 11:17 AM Clebert Suconic
> > > <cl...@gmail.com> wrote:
> > > >
> > > > This is pretty much this PR here:
> > > > https://github.com/apache/activemq-artemis/pulls
> > > >
> > > > On Wed, May 15, 2019 at 11:14 AM Emmanuel Hugonnet <
> > ehugonne@redhat.com> wrote:
> > > > >
> > > > > Hello,
> > > > >
> > > > > When integrating Apache Artemis 2.8.0 with prefixes activated we can
> > see a change in behavior on the JMSDestination header as it now returns
> > > > > a value with "jms.queue." or "jms.topic." prefix.
> > > > >
> > > > > This is no longer compliant with JMS :( Could we have a quick
> > release with this fix as it is currently blocking our own release ?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Emmanuel
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Clebert Suconic
> > >
> > >
> > >
> > > --
> > > Clebert Suconic
> >
> >
> >
> > --
> > Clebert Suconic
> >
--
Clebert Suconic
Re: [HEADS-UP] ActiveMQ 1.8.1 release WAS: JMS compatibility issue
Posted by Justin Bertram <jb...@apache.org>.
You mean 2.8.1 rather than 1.8.1, right?
Justin
On Wed, May 15, 2019 at 12:50 PM Clebert Suconic <cl...@gmail.com>
wrote:
> I would like to do a release tomorrow, to help with Wildfly release.
>
> I would really like to have Wildfly using an official release. In the
> past they had forked and created their own release.
>
> so, for that I will release it tomorrow, which will include
> https://github.com/apache/activemq-artemis/pull/2669
>
> Any objections?
>
> if anyone have any pending changes on their workspaces, we can always
> have another release later. the more the merrier as they say in
> English.
>
> On Wed, May 15, 2019 at 11:38 AM Clebert Suconic
> <cl...@gmail.com> wrote:
> >
> > Sorry, wrong link:
> >
> > https://github.com/apache/activemq-artemis/pull/2669
> >
> > On Wed, May 15, 2019 at 11:17 AM Clebert Suconic
> > <cl...@gmail.com> wrote:
> > >
> > > This is pretty much this PR here:
> > > https://github.com/apache/activemq-artemis/pulls
> > >
> > > On Wed, May 15, 2019 at 11:14 AM Emmanuel Hugonnet <
> ehugonne@redhat.com> wrote:
> > > >
> > > > Hello,
> > > >
> > > > When integrating Apache Artemis 2.8.0 with prefixes activated we can
> see a change in behavior on the JMSDestination header as it now returns
> > > > a value with "jms.queue." or "jms.topic." prefix.
> > > >
> > > > This is no longer compliant with JMS :( Could we have a quick
> release with this fix as it is currently blocking our own release ?
> > > >
> > > > Thanks
> > > >
> > > > Emmanuel
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Clebert Suconic
> >
> >
> >
> > --
> > Clebert Suconic
>
>
>
> --
> Clebert Suconic
>
[HEADS-UP] ActiveMQ 1.8.1 release WAS: JMS compatibility issue
Posted by Clebert Suconic <cl...@gmail.com>.
I would like to do a release tomorrow, to help with Wildfly release.
I would really like to have Wildfly using an official release. In the
past they had forked and created their own release.
so, for that I will release it tomorrow, which will include
https://github.com/apache/activemq-artemis/pull/2669
Any objections?
if anyone have any pending changes on their workspaces, we can always
have another release later. the more the merrier as they say in
English.
On Wed, May 15, 2019 at 11:38 AM Clebert Suconic
<cl...@gmail.com> wrote:
>
> Sorry, wrong link:
>
> https://github.com/apache/activemq-artemis/pull/2669
>
> On Wed, May 15, 2019 at 11:17 AM Clebert Suconic
> <cl...@gmail.com> wrote:
> >
> > This is pretty much this PR here:
> > https://github.com/apache/activemq-artemis/pulls
> >
> > On Wed, May 15, 2019 at 11:14 AM Emmanuel Hugonnet <eh...@redhat.com> wrote:
> > >
> > > Hello,
> > >
> > > When integrating Apache Artemis 2.8.0 with prefixes activated we can see a change in behavior on the JMSDestination header as it now returns
> > > a value with "jms.queue." or "jms.topic." prefix.
> > >
> > > This is no longer compliant with JMS :( Could we have a quick release with this fix as it is currently blocking our own release ?
> > >
> > > Thanks
> > >
> > > Emmanuel
> > >
> > >
> > >
> >
> >
> > --
> > Clebert Suconic
>
>
>
> --
> Clebert Suconic
--
Clebert Suconic
Re: JMS compatibility issue
Posted by Clebert Suconic <cl...@gmail.com>.
Sorry, wrong link:
https://github.com/apache/activemq-artemis/pull/2669
On Wed, May 15, 2019 at 11:17 AM Clebert Suconic
<cl...@gmail.com> wrote:
>
> This is pretty much this PR here:
> https://github.com/apache/activemq-artemis/pulls
>
> On Wed, May 15, 2019 at 11:14 AM Emmanuel Hugonnet <eh...@redhat.com> wrote:
> >
> > Hello,
> >
> > When integrating Apache Artemis 2.8.0 with prefixes activated we can see a change in behavior on the JMSDestination header as it now returns
> > a value with "jms.queue." or "jms.topic." prefix.
> >
> > This is no longer compliant with JMS :( Could we have a quick release with this fix as it is currently blocking our own release ?
> >
> > Thanks
> >
> > Emmanuel
> >
> >
> >
>
>
> --
> Clebert Suconic
--
Clebert Suconic
Re: JMS compatibility issue
Posted by Clebert Suconic <cl...@gmail.com>.
This is pretty much this PR here:
https://github.com/apache/activemq-artemis/pulls
On Wed, May 15, 2019 at 11:14 AM Emmanuel Hugonnet <eh...@redhat.com> wrote:
>
> Hello,
>
> When integrating Apache Artemis 2.8.0 with prefixes activated we can see a change in behavior on the JMSDestination header as it now returns
> a value with "jms.queue." or "jms.topic." prefix.
>
> This is no longer compliant with JMS :( Could we have a quick release with this fix as it is currently blocking our own release ?
>
> Thanks
>
> Emmanuel
>
>
>
--
Clebert Suconic