You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Clebert Suconic <cl...@gmail.com> on 2016/12/20 00:33:20 UTC
Artemis Switch status
Hello guys,
I'm a dev at Artemis, and there was a hack-a-ton at some apache con,
some time ago about installing Artemis on Tomee. What's the status of
that?
Anything I can help with? or it's all taken care of?
Re: Artemis Switch status
Posted by Romain Manni-Bucau <rm...@gmail.com>.
2016-12-20 17:22 GMT+01:00 Clebert Suconic <cl...@gmail.com>:
> > You forget one very important point which is the lib stack, last time I
> > checked - can be irrelevant now - Artemis needed a lot of libraries and
> > moreover not much overlapping with tomee libraries which concretely
> means a
> > lot of potential conflicts with user libs is not deployed as a RAR.
> > Think/Hope it changed since it was early times but this is an important
> > point at out level.
>
>
> Artemis itself have a lot of libraries... beyond some
> commons-libraries and geronimo libraries, these are the libraries we
> use:
>
> airline (could be removed on an integrated version with tomee)
> jboss-loggins
> jboss-logmanager
> johzon (it's an apache project)
> jetty (could be removed on an integrated version)
> jgroups (optional on the integrated)
> tomcat-servlet (I bet you have something similar)
> slf4j (i bet you have something similar).
>
>
>
would be great to remove airline (not a strict blocker but I don't think we
need it), jboss-log* (avoid issue for hibernate users mainly + better to
avoid yet another logging framework), jetty (we don't provide AMQ ws:// to
not provide OOTB jetty for quite obvious reasons ;)) and jgroups (think
transitively it brings jboss-log* and 2.4M is too big to be added by
default in tomee which tries to stay light OOTB).
Also spotted guava in the distrib which is a big deal by itself if needed
transitively (but seems it is not from your answer).
Excepted jboss-loging usage I'm not sure about, all others can be made
optional I think. No problem to have a tomee-artemis even if I'm not yet
sure what we can needed (strictly speaking old AMQ doesn't need glue code,
the one we have is just for convenience).
>
>
> So.. these libraries are just regular libraries...
>
> you need some work done to integrate artemis well.. but I don't see
> any issues...
>
>
Let's work on it next year even if I'm not sure what it is about as
mentionned.
> It's a different product and the libraries are different.. and that
> will never be fixed.
>
>
>
Don't see it that way. From tomee point of view, less we add better we are.
3M of jetty + 1M of jboss logging + 3.5M of netty + 2.4M of jgroups + 0.6k
of commons-config2 and you already add more than 10M where old AMQ is < 5M.
>
>
> Anyways, all I am looking for now is a way to give users an option to
> run on tomee if possible. lets talk again next year :) probably around
> feb.
>
+1 for that (the only "?" I have is really about the default ;))
Re: Artemis Switch status
Posted by Clebert Suconic <cl...@gmail.com>.
> You forget one very important point which is the lib stack, last time I
> checked - can be irrelevant now - Artemis needed a lot of libraries and
> moreover not much overlapping with tomee libraries which concretely means a
> lot of potential conflicts with user libs is not deployed as a RAR.
> Think/Hope it changed since it was early times but this is an important
> point at out level.
Artemis itself have a lot of libraries... beyond some
commons-libraries and geronimo libraries, these are the libraries we
use:
airline (could be removed on an integrated version with tomee)
jboss-loggins
jboss-logmanager
johzon (it's an apache project)
jetty (could be removed on an integrated version)
jgroups (optional on the integrated)
tomcat-servlet (I bet you have something similar)
slf4j (i bet you have something similar).
So.. these libraries are just regular libraries...
you need some work done to integrate artemis well.. but I don't see
any issues...
It's a different product and the libraries are different.. and that
will never be fixed.
Anyways, all I am looking for now is a way to give users an option to
run on tomee if possible. lets talk again next year :) probably around
feb.
Re: Artemis Switch status
Posted by Romain Manni-Bucau <rm...@gmail.com>.
2016-12-20 16:44 GMT+01:00 Clebert Suconic <cl...@gmail.com>:
> On Tue, Dec 20, 2016 at 10:21 AM, Romain Manni-Bucau
> <rm...@gmail.com> wrote:
> > 2016-12-20 16:18 GMT+01:00 Clebert Suconic <cl...@gmail.com>:
> >
> >> On Tue, Dec 20, 2016 at 2:36 AM, Romain Manni-Bucau
> >> <rm...@gmail.com> wrote:
> >> > Hi Clebert
> >> >
> >> > Since tomee support custom resource instantiation and resource
> adapters,
> >> it
> >> > is just a matter of configuring it normally.
> >>
> >> Is it? I couldn't make it work last time..
> >>
> >>
> > Where are you blocked, can help on that
> >
> >
> >> >
> >> > Didnt check lately but AMQ (4/5) being more than widely abused
> switching
> >> > without having a compatibility in term of feature (openwire, network
> of
> >> > broker, auto creation of resources, ....) and stack (almost no
> external
> >> > dependencies) would be a real challenge.
> >>
> >> We have those. Although I don't foresee every single feature
> >> implemented between AMQ5 and Artemis for two reasons:
> >>
> >> - some won't make sense
> >> - some have different demands these days.
> >>
> >>
> > well, a lot are so widely used than compat there is not (yet?) an option
> > for us I fear
>
> - We already have Openwire compatibility.
> - The thing that will hang most users is the lack of virtual topics.
> that you can replace by Diverts... and you don't really need it with
> JMS2. I don't really think it's an issue... you can safely use Artemis
> without ever needing these features. Especially on cases for J2EE
> usecases. (see wildfly is using Artemis wildly already).
>
>
You forget one very important point which is the lib stack, last time I
checked - can be irrelevant now - Artemis needed a lot of libraries and
moreover not much overlapping with tomee libraries which concretely means a
lot of potential conflicts with user libs is not deployed as a RAR.
Think/Hope it changed since it was early times but this is an important
point at out level.
> You have a lot more to gain on using Artemis, than you would miss from
> certain features. I think it would be a wise move on the next major
> release.
>
> Look at the whole progress we have made this past year with Artemis.
> You can send thousands messages / second without much effort. Paging
> could be totally based on disk.. and throughput a lot faster... it's
> getting really mature.
>
> This should be a community decision. I can help you on discussions
> whenever they happen. I don't follow this thread closely, so please
> ping me somehow you can whenever you need my attention here?
>
>
I'd rather say this needs to be a user decision almost only. We didn't get
any request yet on that and a few only on JMS 2 - that's why it is not
urgent ;).
> But at least you already have an options now.. I will play with that next
> year.
>
Happy to help you ensuring it works next year and package a tomee plus
"bis" version (we can discuss once done who hosts it). If artemis adapter
is more advanced than (old) AMQ one it can mean no tomee specific code and
therefore just one maven plugin to define :).
>
> >
> >
> >> >
> >> > Note however it only affects plus version and not tomee embedded or
> tomee
> >> > webprofile which can be customized by the user.
> >>
> >> I agree a wide switch would need to be done on a major bump.
> >> >
> >> > An idea could be to use in Artemis tomee maven plugin to
> "tomee:build" an
> >> > Artemis distribution with a default config and dependencies.
> >> >
> >> > Wdyt?
> >>
> >> I don't understand what that means. Do you have a pointer?
> >>
> >>
> > http://tomee.apache.org/developer/tools/maven/tomee.html tomee:build
> will
> > allow you to build a tomee zip/tar.gz with artemis pre setup if you pass
> > the first point and distribute it as a
> > "tomee-artemis" distro.
> >
> >
> >>
> >> I won't be able to work on this this year anyways... I was just
> >> checking the status and making my new years resolution to what I will
> >> have to work on :) I will soon be on holidays break.
> >>
> >>
> >>
> >>
> >> Have nice holidays.
> >>
> >
> > you too!
>
>
>
> --
> Clebert Suconic
>
Re: Artemis Switch status
Posted by Clebert Suconic <cl...@gmail.com>.
On Tue, Dec 20, 2016 at 10:21 AM, Romain Manni-Bucau
<rm...@gmail.com> wrote:
> 2016-12-20 16:18 GMT+01:00 Clebert Suconic <cl...@gmail.com>:
>
>> On Tue, Dec 20, 2016 at 2:36 AM, Romain Manni-Bucau
>> <rm...@gmail.com> wrote:
>> > Hi Clebert
>> >
>> > Since tomee support custom resource instantiation and resource adapters,
>> it
>> > is just a matter of configuring it normally.
>>
>> Is it? I couldn't make it work last time..
>>
>>
> Where are you blocked, can help on that
>
>
>> >
>> > Didnt check lately but AMQ (4/5) being more than widely abused switching
>> > without having a compatibility in term of feature (openwire, network of
>> > broker, auto creation of resources, ....) and stack (almost no external
>> > dependencies) would be a real challenge.
>>
>> We have those. Although I don't foresee every single feature
>> implemented between AMQ5 and Artemis for two reasons:
>>
>> - some won't make sense
>> - some have different demands these days.
>>
>>
> well, a lot are so widely used than compat there is not (yet?) an option
> for us I fear
- We already have Openwire compatibility.
- The thing that will hang most users is the lack of virtual topics.
that you can replace by Diverts... and you don't really need it with
JMS2. I don't really think it's an issue... you can safely use Artemis
without ever needing these features. Especially on cases for J2EE
usecases. (see wildfly is using Artemis wildly already).
You have a lot more to gain on using Artemis, than you would miss from
certain features. I think it would be a wise move on the next major
release.
Look at the whole progress we have made this past year with Artemis.
You can send thousands messages / second without much effort. Paging
could be totally based on disk.. and throughput a lot faster... it's
getting really mature.
This should be a community decision. I can help you on discussions
whenever they happen. I don't follow this thread closely, so please
ping me somehow you can whenever you need my attention here?
But at least you already have an options now.. I will play with that next year.
>
>
>> >
>> > Note however it only affects plus version and not tomee embedded or tomee
>> > webprofile which can be customized by the user.
>>
>> I agree a wide switch would need to be done on a major bump.
>> >
>> > An idea could be to use in Artemis tomee maven plugin to "tomee:build" an
>> > Artemis distribution with a default config and dependencies.
>> >
>> > Wdyt?
>>
>> I don't understand what that means. Do you have a pointer?
>>
>>
> http://tomee.apache.org/developer/tools/maven/tomee.html tomee:build will
> allow you to build a tomee zip/tar.gz with artemis pre setup if you pass
> the first point and distribute it as a
> "tomee-artemis" distro.
>
>
>>
>> I won't be able to work on this this year anyways... I was just
>> checking the status and making my new years resolution to what I will
>> have to work on :) I will soon be on holidays break.
>>
>>
>>
>>
>> Have nice holidays.
>>
>
> you too!
--
Clebert Suconic
Re: Artemis Switch status
Posted by Romain Manni-Bucau <rm...@gmail.com>.
2016-12-20 16:18 GMT+01:00 Clebert Suconic <cl...@gmail.com>:
> On Tue, Dec 20, 2016 at 2:36 AM, Romain Manni-Bucau
> <rm...@gmail.com> wrote:
> > Hi Clebert
> >
> > Since tomee support custom resource instantiation and resource adapters,
> it
> > is just a matter of configuring it normally.
>
> Is it? I couldn't make it work last time..
>
>
Where are you blocked, can help on that
> >
> > Didnt check lately but AMQ (4/5) being more than widely abused switching
> > without having a compatibility in term of feature (openwire, network of
> > broker, auto creation of resources, ....) and stack (almost no external
> > dependencies) would be a real challenge.
>
> We have those. Although I don't foresee every single feature
> implemented between AMQ5 and Artemis for two reasons:
>
> - some won't make sense
> - some have different demands these days.
>
>
well, a lot are so widely used than compat there is not (yet?) an option
for us I fear
> >
> > Note however it only affects plus version and not tomee embedded or tomee
> > webprofile which can be customized by the user.
>
> I agree a wide switch would need to be done on a major bump.
> >
> > An idea could be to use in Artemis tomee maven plugin to "tomee:build" an
> > Artemis distribution with a default config and dependencies.
> >
> > Wdyt?
>
> I don't understand what that means. Do you have a pointer?
>
>
http://tomee.apache.org/developer/tools/maven/tomee.html tomee:build will
allow you to build a tomee zip/tar.gz with artemis pre setup if you pass
the first point and distribute it as a
"tomee-artemis" distro.
>
> I won't be able to work on this this year anyways... I was just
> checking the status and making my new years resolution to what I will
> have to work on :) I will soon be on holidays break.
>
>
>
>
> Have nice holidays.
>
you too!
Re: Artemis Switch status
Posted by Clebert Suconic <cl...@gmail.com>.
On Tue, Dec 20, 2016 at 2:36 AM, Romain Manni-Bucau
<rm...@gmail.com> wrote:
> Hi Clebert
>
> Since tomee support custom resource instantiation and resource adapters, it
> is just a matter of configuring it normally.
Is it? I couldn't make it work last time..
>
> Didnt check lately but AMQ (4/5) being more than widely abused switching
> without having a compatibility in term of feature (openwire, network of
> broker, auto creation of resources, ....) and stack (almost no external
> dependencies) would be a real challenge.
We have those. Although I don't foresee every single feature
implemented between AMQ5 and Artemis for two reasons:
- some won't make sense
- some have different demands these days.
>
> Note however it only affects plus version and not tomee embedded or tomee
> webprofile which can be customized by the user.
I agree a wide switch would need to be done on a major bump.
>
> An idea could be to use in Artemis tomee maven plugin to "tomee:build" an
> Artemis distribution with a default config and dependencies.
>
> Wdyt?
I don't understand what that means. Do you have a pointer?
I won't be able to work on this this year anyways... I was just
checking the status and making my new years resolution to what I will
have to work on :) I will soon be on holidays break.
Have nice holidays.
Re: Artemis Switch status
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi Clebert
Since tomee support custom resource instantiation and resource adapters, it
is just a matter of configuring it normally.
Didnt check lately but AMQ (4/5) being more than widely abused switching
without having a compatibility in term of feature (openwire, network of
broker, auto creation of resources, ....) and stack (almost no external
dependencies) would be a real challenge.
Note however it only affects plus version and not tomee embedded or tomee
webprofile which can be customized by the user.
An idea could be to use in Artemis tomee maven plugin to "tomee:build" an
Artemis distribution with a default config and dependencies.
Wdyt?
Le 20 déc. 2016 01:34, "Clebert Suconic" <cl...@gmail.com> a
écrit :
Hello guys,
I'm a dev at Artemis, and there was a hack-a-ton at some apache con,
some time ago about installing Artemis on Tomee. What's the status of
that?
Anything I can help with? or it's all taken care of?