SOAP over JMS not a standard

SOAP over JMS not a standard

I was really convinced it was a standard. Apparently not. The best I can find is a W3C recommendation (http://www.w3.org/Submission/SOAPJMS/). It seems it never made it to be a standard. Also in the JMS spec (http://jcp.org/en/jsr/detail?id=914), there is only mention of HTTP as transport for a SOAP binding.
A bit strange, WSIF has had this possibility for years (http://ws.apache.org/wsif/providers/wsdl_extensions/jms_extension.html).

Maybe creating standards is becoming more difficult? Too many parties involved? Too much at stake?

I have to admit that JMS remains limited to the java space. Maybe one day we will have SOAP/AMQP (http://www.amqp.org). I’m hoping on it.

Authored by: Jeroen



Working at i8c

i8c is a system integrator that strives for an informal atmosphere between its employees, who have an average age of approx 30 years old. We invest a lot of effort in the professional development of each individual, through a direct connection between the consultants and the management (no multiple layers of middle management). We are based in Kontich, near Antwerp, but our customers are mainly located in the triangle Ghent-Antwerp-Brussels and belong to the top 500 companies in Belgium (Securex, Electrabel, UCB, etc…).

Quality Assurance

i8c is committed to delivering quality services and providing customer satisfaction. That’s why we invested in the introduction of a Quality Management System, which resulted in our ISO9001:2000 certification. This guarantees that we will meet your expectations, as a reliable, efficient and mature partner for your SOA & integration projects.

i8c - ISO9001-2015