Java
The Java™ API is provided as a JAR file. It can be used with Java 8 (8u131-b11 GA or later) or Java 11 (11.0.3 GA or later).
Get the Java client libraries using Maven™ :
<repositories> <repository> <id>push-repository</id> <url>https://download.diffusiondata.com/maven/</url> </repository> </repositories>
<dependency> <groupId>com.pushtechnology.diffusion</groupId> <artifactId>diffusion-client</artifactId> <version>
Get the Java client libraries using Gradle:
repositories { maven { url "http://download.diffusiondata.com/maven/" } }
compile 'com.pushtechnology.diffusion:diffusion-client:6.11.2'
Get the Java client libraries:
https://download.diffusiondata.com/clients/6.11.2/java/diffusion-client-6.11.2.jar
Capabilities
To see the full list of capabilities supported by the Java API, see Feature support in the Diffusion API.
Support
Platform | Minimum supported versions | Supported transport protocols |
---|---|---|
Java |
Java 8 (8u131-b11 GA or later) or Java 11 (11.0.3 GA or later)
Note: The JVM must be
HotSpot™
based.
Note: The JVM must either have passed the Java TCK or be an official AdoptOpenJDK build.
|
WebSocket HTTP (Polling) |
Resources
Using
- Certificates
-
Diffusion™ Cloud Java clients use certificates to validate the security of their connection to Diffusion Cloud . The client validates the certificate sent by Diffusion Cloud against the set of certificates trusted by the Java Development Kit (JDK).
If the certificate sent by Diffusion Cloud cannot be validated against any certificates in the set trusted by the JDK, you receive an exception that contains the following message: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.
Diffusion Cloud uses certificates provided by the certificate authority Startcom. By default, Startcom is not a trusted Certificate Authority (CA) for the Java client.
To ensure that the certificate is validated, set up a trust store for the client and add the appropriate certificates to that trust store:- Obtain the appropriate intermediate certificate from the certificate authority.
You can get the Startcom certificate from the following location: https://www.startssl.com/certs/. The appropriate intermediate certificate is sub.class2.server.ca.pem
- Use keytool to create a trust store for your client that includes this
certificate.
For more information, see https://docs.oracle.com/cd/E19509-01/820-3503/ggfka/index.html
- Use system properties to add the trust store to your client. For example:
System.setProperty("javax.net.ssl.trustStore", "truststore_name");
Or at the command line:-Djavax.net.ssl.keyStore=path_to_truststore
- Obtain the appropriate intermediate certificate from the certificate authority.
- Writing good callbacks
-
The Java client library invokes callbacks using a thread from Diffusion Cloud thread pool. Callbacks for a particular session are called in order, one at a time. Consider the following when writing callbacks:
- Do not sleep or call blocking operations in a callback. If you do so, other pending callbacks for the session are delayed. If you must call a blocking operation, schedule it in a separate application thread.
- You can use the full Diffusion Cloud API to make other requests to the server. If you want to make many requests based on a single callback notification, be aware that Diffusion Cloud client flow control is managed differently in callback threads. Less throttling is applied and it is easier to overflow the servers by issuing many thousands of requests. If you have a lot of requests to make, it is better to schedule the work in an application thread.
- Regular expressions
-
The Java client uses the same regular expression engine to Diffusion Cloud . Some regular expressions in topic selectors are evaluated on the client and others on Diffusion Cloud . There is no difference in how these regular expressions are evaluated in the Java client.