Steven van Beelen

To be honest with you @mgimenoroman, prioritization from AxonIQ's part on this is relatively low due to the fact that the Axon Server Standard Edition works perfectly as a `DistributedQueryBus`....

Thanks for the interest @billy93, but as you can see the labels, the prioritization or set milestone have not been adjusted since the 15th of January. As soon as they...

Hi @nils-christian, thanks for opening this issue with us! It shares an interesting solution that might just be valuable for others too. I have a question before I go about...

Awesome, thanks for the insight here, @nils-christian. So, the context name is used in conjunction with a default query name, merging the two, right? And, the name is just used...

Thanks for that, @nils-christian. My main predicament with this, is that I can't conceive of use case for this outside your description. Moreover, I would ideally expect a specific message...

> To be honest: No. I admit that our use case is very specific. I still hoped that we could find some more cases which would justify to add this...

Thanks for the clarification, @sandjelkovic. Based on what you've shared, I think it's fair we change the priority to a 4 right now and keep the on-hold status effective.

Removed the milestone for now, as we will not be able to resolve this issue within release 4.6.0. We will adjust this ticket accordingly once we pick it up again.

There are definitely plans to support JDK 16. Moving that direction will, however, have quite some impact on the framework. As such, it is not a decision we can take...

Much appreciated @zcglisp. We'll be certain to be vocal about it as soon as we support JDK 16; don't worry :-)