Re: Seeking interested parties for a messaging components podling

I believe from the POV of Camel, the Messaging provider should provide such components... we thought during the process to have these compnents living in Camel, that's where this thread started. The thing is.. starting an incubator project just to store the JMS Pool sounds like building a war

Re: Seeking interested parties for a messaging components podling

Sounds interesting. I wonder if the Camel community would be interested in this as well? Phil This message optimized for indexing by NSA PRISM On Wed, Aug 2, 2017 at 2:15 PM, Clebert Suconic wrote: > Just coming back into this.. I want to be realistic here... I'm

Re: Seeking interested parties for a messaging components podling

Just coming back into this.. I want to be realistic here... I'm kind of pushing back on my side. If there's anyone with time to push this forward.. i will support them... but I won't have time on my hands to push this myself. I don't have the time to manage a new project now... my demand on

Re: Seeking interested parties for a messaging components podling

Hi, RocketMQ community have discussed the common messaging components endeavor[1], we are glad to join this podling :-) As for OpenMessaging spec, we have launched this spec. project under Linux foundation(May be CNCF later), If guys have interest about it, welcome join and discuss at

Re: Seeking interested parties for a messaging components podling

With the number of message brokers out there (call it message solution, server.. whatever you want to call it).. This new project could represent a nice opportunity.. it was a simple idea that's starting to grow I think @Von Gosling: would you be able to bring OpenMessaging as part of this?

Re: Seeking interested parties for a messaging components podling

You've been added. On Wed, Jun 28, 2017 at 8:06 AM Michael André Pearce < michael.andre.pea...@me.com> wrote: > @John, > > I have created username: MichaelAndrePearce (so original) > > Could I be enabled to edit the wiki > > Cheers > Mike > > Sent from my iPhone > > > On 26 Jun 2017, at 21:47,

Re: Seeking interested parties for a messaging components podling

@John, I have created username: MichaelAndrePearce (so original) Could I be enabled to edit the wiki Cheers Mike Sent from my iPhone > On 26 Jun 2017, at 21:47, Clebert Suconic wrote: > > @John: do I need special auth to change the WIKI you created? I can't >

Re: Seeking interested parties for a messaging components podling

@John: do I need special auth to change the WIKI you created? I can't figure out how to make a change. On Mon, Jun 26, 2017 at 6:16 AM, John D. Ament wrote: > All, > > I've dropped in the proposal template to > https://wiki.apache.org/incubator/MessagingComponentsProposal

Re: Seeking interested parties for a messaging components podling

All, I've dropped in the proposal template to https://wiki.apache.org/incubator/MessagingComponentsProposal - we can rename it later if we come up with a better name. I'd encourage those interested in the project to start to form out this proposal so we can start to shape the who, the why and

Re: Seeking interested parties for a messaging components podling

Hi john, I am very interested in participate in such a podling personally. as for RocketMQ community, imo, we will start a thread to discussion this idea :-) Best Regards, Von Gosling > 在 2017年6月24日，22:17，John D. Ament 写道： > > Hi Von Gosling, > > So I just want to

Re: Seeking interested parties for a messaging components podling

Hi Von Gosling, So I just want to check, is this an indication that there may be interest from the RocketMQ community to participate in such a podling? John On Fri, Jun 23, 2017 at 9:35 PM Von Gosling wrote: > > Hi, > > > I am not sure your mention is Apache RocketMQ.

Re: Seeking interested parties for a messaging components podling

I think its already agreed it makes sense. We just need to make a proposal and a scope then. On Fri, Jun 23, 2017 at 9:35 PM Von Gosling wrote: > > Hi, > > > I am not sure your mention is Apache RocketMQ. In RocketMQ, jms > integration is just a adaptor, while not fully

Re: Seeking interested parties for a messaging components podling

Hi, I am not sure your mention is Apache RocketMQ. In RocketMQ, jms integration is just a adaptor, while not fully support JMS 1.1 and JMS 2.0 specification. IMO, that’s a good idea. if we messaging engines can collaborate to some common components, such as benchmark, common api

Re: Seeking interested parties for a messaging components podling

Hi, As already been discussing in the Artemis mailing lists have some areas we would like to contribute/commit in particular already looking at: JMSObject Custom serdes wrapper (with and avro serdes as initial provided) Generic JMS Client side persistence Cheers Mike On 2017-06-22 04:39

Re: Seeking interested parties for a messaging components podling

This would be totally from a Messaging Point of View.. not just JMS BTW. Right now there are 2 JMS components that would be cross used from qpid-jms, artemis.. and who knows… Rocket… - Serders/Serialization integration for Object messages - JMS Connection pool… There’s also the idea of using

Re: Seeking interested parties for a messaging components podling

I would love to contribute. On Jun 22, 2017 8:05 AM, "John D. Ament" wrote: > All, > > There's an ongoing discussion on the ActiveMQ dev list [1] to spin up a > project focused on core, reusable messaging components. The feeling is > that this is outside the realm of

Seeking interested parties for a messaging components podling

All, There's an ongoing discussion on the ActiveMQ dev list [1] to spin up a project focused on core, reusable messaging components. The feeling is that this is outside the realm of ActiveMQ for various reasons and could be leveraged by various messaging platforms, potentially even building out