Java Messaging Service is an asynchronous point-to-point and sent-to-list messaging API. It appears to be quite flexible with regards to payload (allows to send raw data, serialized Java objects, XML or other string data, and sets of attribute-value pairs), and is quite a fair bit simpler then SOAP. It does not force us to send every bit of data as XML, and seems to be more suitable for an application that does not involve talking to 25 different suppliers and mandatory top-to-bottom buzzword compliance.
Here is a quick FAQ on it: http://java.sun.com/products/jms/faq.html
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It sounds nice. If it can take XML as input, then there's no problem. It may need some extra coding on the client side, but that's ok. I've made some tests with web services that output standard XML instead of SOAP, and they keep everything smaller.
Have you guys read the XSDs I posted? We really have to agree on how will we call each label and such, since it will be the base of our communications.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Java Messaging Service is an asynchronous point-to-point and sent-to-list messaging API. It appears to be quite flexible with regards to payload (allows to send raw data, serialized Java objects, XML or other string data, and sets of attribute-value pairs), and is quite a fair bit simpler then SOAP. It does not force us to send every bit of data as XML, and seems to be more suitable for an application that does not involve talking to 25 different suppliers and mandatory top-to-bottom buzzword compliance.
Here is a quick FAQ on it: http://java.sun.com/products/jms/faq.html
what do you think alankor?
It sounds nice. If it can take XML as input, then there's no problem. It may need some extra coding on the client side, but that's ok. I've made some tests with web services that output standard XML instead of SOAP, and they keep everything smaller.
Have you guys read the XSDs I posted? We really have to agree on how will we call each label and such, since it will be the base of our communications.