Re: Artemis: AMQP create queue based on FQQN

[Krzysztof <h4...@gmail.com>]

I've look at the source code, and it seems to be doable to implement auto
creation of queues based on FQQN? If you don't mind I would like to give it
a try.

On Sun, Dec 29, 2019 at 10:46 PM Krzysztof <h4...@gmail.com> wrote:

> I'm just wondering if it should be possible to create queue based on the
> value specified via FQQN. Currently you cannot attach to the queue if it is
> not pre-configured.
>
> I'm working on POC of .NET ActiveMQ client and I am trying to give the
> potential user as flexible API as possible.
>
> The draft API assumes that it should be feasible to specify address,
> routing type (Multicast, Anycast), queue name, durability, and whether the
> queue should be shared or not.
>
> This way user would be able to leverage most of the Artemis Address Model
> configuration options directly from the code without pre-configuration
> anything on the broker side.
>
> What do you think?
>

Re: Artemis: AMQP create queue based on FQQN

[Clebert Suconic <cl...@gmail.com>]

I'm still a bit slow after my vacations :)


What this means? an expression to create the queue names on DLQs? I
guess I'm very slow still :)

I've tried something similar in the past but I couldn't find a way
without breaking the APi too much. If you found a way.. perhaps we can
review how you would implement it?

On Wed, Jan 8, 2020 at 5:36 PM Krzysztof <h4...@gmail.com> wrote:
>
> I've look at the source code, and it seems to be doable to implement auto
> creation of queues based on FQQN? If you don't mind I would like to give it
> a try.
>
> On Sun, Dec 29, 2019 at 10:46 PM Krzysztof <h4...@gmail.com> wrote:
>
> > I'm just wondering if it should be possible to create queue based on the
> > value specified via FQQN. Currently you cannot attach to the queue if it is
> > not pre-configured.
> >
> > I'm working on POC of .NET ActiveMQ client and I am trying to give the
> > potential user as flexible API as possible.
> >
> > The draft API assumes that it should be feasible to specify address,
> > routing type (Multicast, Anycast), queue name, durability, and whether the
> > queue should be shared or not.
> >
> > This way user would be able to leverage most of the Artemis Address Model
> > configuration options directly from the code without pre-configuration
> > anything on the broker side.
> >
> > What do you think?
> >



-- 
Clebert Suconic