Mario Kapusta

Hi @haukec , sure thing but unfortunately I just tried to debug the use case you are mentioning and cannot reproduce this. Your use case is even covered in automated...

Hello @haukec , I just tried my gRPC example project and all works fine - please try to have a look at this project and make sure you have everything...

Ok, so I checked your example and found 2 issues. One is configuration error and then there is a bug in the library for this special case as well and...

Just saving here some resources for implementation and other discussions I found during short research: Apache docs: https://pulsar.apache.org/docs/v1.22.0-incubating/getting-started/ConceptsAndArchitecture/ http://pulsar.apache.org/docs/en/concepts-multi-tenancy/ Apache java client issue: https://github.com/apache/pulsar/issues/3906 Stackoverflow producer example: https://stackoverflow.com/questions/59966588/can-i-publish-consume-to-from-multiple-namespaces-and-topic-of-apache-pulsar-usi

Thanks, @shodo, this is a great point!

Actually, there is a use case where the exception is not the type of `InvocationTarget` - for example, when you set a wrong type for your incoming parameter, the cause...

Hey @zehuiHuang - These parameters are not exposed but this will change this week when multiple optional parameters using some sort of builder will be added to producers and consumers...

Hi @Wanxp , I still didn't design the way how the transaction will work. This PR is just about to make the configuration work and so people can use raw...

Hey @dsj017112, there is a way to subscribe to multiple namespaces using the `PulsarConsumer` annotation: ```java @PulsarConsumer( topic = "my-topic", clazz = MyMsg.class, subscriptionType = SubscriptionType.JSON, namespace = "my-namespace") public...

Hey @xieJingHua, we should support all connections available in the native Pulsar Library. For instance, there is support for multiple advertised listeners if you mean this. https://pulsar.apache.org/docs/concepts-multiple-advertised-listeners/ Check the documentation...