Early Access Now Available for the New Java Messaging API!

@marc I'm looking to setup my pom file to try out the new API. Do I need both the JCSMP dependency and the solace-messaging-client? If so, why do I need both. Thanks!

I tested our use cases (those are allot), here what i found for the moment.

Problem 1:

        final PersistentMessageReceiver receiver = service
                .createPersistentMessageReceiverBuilder()
                .withMissingResourcesCreationStrategy(MissingResourcesCreationStrategy.CREATE_ON_START)
                .withSubscriptions(
                        TopicSubscription.of("demo/foo/>"),
                        TopicSubscription.of("demo/baa/g*/alpha")
                )
                .withActivationPassivationSupport(stateChangeListener)
                .withMessageAutoAcknowledgement()
                .build(Queue.durableExclusiveQueue("demo_queue_name"))
                .start();

com.solacesystems.jcsmp.JCSMPErrorResponseException: 400: Subscription Already Exists - Queue 'demo_queue_name' - Topic 'demo/foo/>'

Dint found the option to ignore subscription that are already assigned to the queue.

Problem 2:

        final PersistentMessageReceiver receiver = service
                .createPersistentMessageReceiverBuilder()
                .withMissingResourcesCreationStrategy(MissingResourcesCreationStrategy.CREATE_ON_START)
                .withSubscriptions(
                        TopicSubscription.of("demo/foo/>"),
                        TopicSubscription.of("demo/baa/g*/alpha")
                )
                .withMessageAutoAcknowledgement()
                .withActivationPassivationSupport(stateChangeListener)
                .build(Queue.durableExclusiveQueue("demo_queue_name"))
                .start();

When switching withMessageAutoAcknowledgement and withActivationPassivationSupport
i get an not helping exception:
Exception in thread "main" java.lang.UnsupportedOperationException: Unsupported property value type com.solace.samples.java.ConsumeQueue$$Lambda$110/0x00000008002d6440
When using the builder/fluent setter pattern, the order how the calling the methods should be irrelevant.

Reproducer: https://gist.github.com/GreenRover/b5d1ceee1bafef1b48dd439a88c522ac#file-consumequeue-java

Problem 3:

The handling of to big messages is still broken (Ticket RT-55160).
If i send a 31MB message to the broker:

• I get in log: ERROR com.solac.messa.publi.PersistentMessagePublisherImpl - DefaultProducer should not be log:null
  com.solacesystems.jcsmp.JCSMPErrorResponseException: 400: Document Is Too Large

• Broker close connection

• Client lib reconnects
• Client lib try to resend the same message again
• Endless loop

Reproducer: https://gist.github.com/GreenRover/b5d1ceee1bafef1b48dd439a88c522ac#file-publishbigmessages-java

There could be better documentation for:
OutboundMessageBuilder.withProperty
https://docs.solace.com/API-Developer-Online-Ref-Documentation/pubsubplus-java/
Are there constants for thinks like "dmq eligible" , "correlation id"?

Why is messageId included but here (https://docs.solace.com/API-Developer-Online-Ref-Documentation/java/index.html?com/solacesystems/jcsmp/JCSMPProperties.html) deprecated?

@amackenzie Please have your developers to read this. I currently not interested to use the new lib.
I like the new concepts but the current jcsmp looks much more stable.
Just wanted to give a a try an made short testing. I have no official task to evaluate this lib. Just using some spare time and be unable to spend more time for this.