JarCasting
JarCasting JarCasting

Soap2JmsClient


License

License
Categories

Categories

CLI User Interface
GroupId

GroupId

com.github.jbricks.soap2jms
ArtifactId

ArtifactId

s2j_client
Last Version

Last Version

0.1.0
Release Date

Release Date
Type

Type

jar
Description

Description

Soap2JmsClient

Download s2j_client

Filename Size
s2j_client-0.1.0.pom
s2j_client-0.1.0.jar 31 KB
s2j_client-0.1.0-sources.jar 17 KB
s2j_client-0.1.0-javadoc.jar 119 KB
Browse

How to add to project

<!-- https://jarcasting.com/artifacts/com.github.jbricks.soap2jms/s2j_client/ -->
<dependency>
    <groupId>com.github.jbricks.soap2jms</groupId>
    <artifactId>s2j_client</artifactId>
    <version>0.1.0</version>
</dependency>
// https://jarcasting.com/artifacts/com.github.jbricks.soap2jms/s2j_client/
implementation 'com.github.jbricks.soap2jms:s2j_client:0.1.0'
// https://jarcasting.com/artifacts/com.github.jbricks.soap2jms/s2j_client/
implementation ("com.github.jbricks.soap2jms:s2j_client:0.1.0")
'com.github.jbricks.soap2jms:s2j_client:jar:0.1.0'
<dependency org="com.github.jbricks.soap2jms" name="s2j_client" rev="0.1.0">
  <artifact name="s2j_client" type="jar" />
</dependency>
@Grapes(
@Grab(group='com.github.jbricks.soap2jms', module='s2j_client', version='0.1.0')
)
libraryDependencies += "com.github.jbricks.soap2jms" % "s2j_client" % "0.1.0"
[com.github.jbricks.soap2jms/s2j_client "0.1.0"]

Dependencies

compile (4)

Group / Artifact Type Version
com.github.jbricks.soap2jms : s2j_common jar 0.1.0
org.slf4j : slf4j-api jar 1.7.21
org.apache.commons : commons-collections4 jar 4.1
commons-io : commons-io jar 2.5

provided (1)

Group / Artifact Type Version
javax.jms : javax.jms-api jar 2.0

test (2)

Group / Artifact Type Version
org.slf4j : slf4j-simple jar 1.7.21
junit : junit jar 4.12

Project Modules

There are no modules declared in this project.

Build Status

#Jms Over Soap

This project allows to access a JMS queue through a standard SOAP over HTTP web service. It allows to read and send messages from/to a JMS queue. Clients don't have to depend on any JMS implementation libraries. They are simple JAX-WS web service clients, that can be supported by any JAX-WS implementation (Apache CXF for instance).

It is not to be confused with "Soap over JMS". Soap Over JMS encapsulates a soap message into a JMS envelope. It has the same problems of JMS in terms of interoperability and it requires a JMS client implementation to connect to the server.

Visit the website for more informations.

goals:

  • Simplicity: It is simple to integrate. It has few dependencies. It will be well documented.
  • Reliability: JMS has a plus over SOAP: its reliability. Soap2Jms try to replicate this at the minimum cost: all the operations are idempotent. If clients are coded properly, messages will not be lost or duplicated in case of network or system failure.
  • Interoperability: It is independent from the specific JMS provider used. It can work in any application, without any change. Clients can be coded in languages other than java (.NET ...). Web services are WS-I Basic Profile 1 compliant.

Similar projects

Before starting the implementation I've evaluated similar project, each one has it's own strengths.

ActiveMQ REST Interface

ActiveMQ has a separate project that exposes most of the JMS functions through a rest interface. Pros:

  • Well manteined, it has a large community.
  • Well documented.
  • Well tested, security is ensured.

Cons:

  • The protocol is over complicated. It mimic JMS. It requires to open a session, and later to close it.
  • It's ActiveMQ specific.
  • It's JSON over HTTP. It doesn't have a WSDL to conform to (only a very lengthly description of the protocol).

OpenMQ UMS Interface

ActiveSoap

Hosted on codehaus, the site seems dead (10/11/2016).

com.github.jbricks.soap2jms

Java Bricks

The missing bricks in the java stack

Versions

Version
0.1.0