test posts – march 3 – 1
System
Posts: 71
Last month Solace released version 1.0 of a new messaging API for Java. Why is it version 1.0 when we already have a Java API, you might ask? I’ll break that down first, then introduce the new one and explain why it’s such a big deal. A Tale of Two Java APIs “What’s in a name? That which we call a rose by any other name would smell as sweet.” – Juliet While I myself called this new API “a new Java Messaging API” in the title of this post, and its official name is “Solace PubSub+ Messaging API for Java”, in the public documentation and product information, it will henceforth be known as the “Java API”. For this post, I’ll err on the side of ensuring clarity by calling it the new Java API. So in deference to Juliet above, going forward the old/existing Java API, which was named “Solace PubSub+ Messaging API for Java” is being renamed “PubSub+ Messaging API for Java (JCSMP)” and will generally be referred to as the JCSMP API, but sometimes you may see it called just “JCSMP” or the “classic” Java API. (JCSMP, if you’re interested, stands for “Java Solace content subscription management protocol.”) While it might take a minute to get used to the naming, I assure you this is not a case of what British rockers The Who famously worried about when they sang “the new boss is same as the old boss.” Why a Second “New Approach” Java API was Needed The JCSMP API is our oldest and most popular API, but as PubSub+ Platform evolves and is implemented by more customers across more use cases, we decided JCSMP needed a more modern API, and this new Java API is the result. The new Java API is implemented as an API layer that wraps functionality in JCSMP. The JCSMP API will not be deprecated or removed from Solace’s supported products – all existing and future JCSMP applications will continue to work, and are fully supported by Solace. In the JCSMP API there are many references to Solace’s legacy of XML content routing. One of the most confusing aspects of this is the XMLMessage interface. This is how you handle messages in JCSMP and refers to the internal representation of the message, but to an application developer using binary attachments or text messages, this is not actually limited to XML payloads....
0