SOAP webservices can be accessed through HTTP as well as JMS .
SOAP over JMS gives message delivery guarantee and is preferred where message critical application are deployed.
JMS provide two types of message communication
1) point to point
(A) once message is received it is removed from Q
(B) only one receiver can receive the message
2) publish / subscribe
(A) message stays on topic even after one receiver reads it
(B) multiple receivers can subscribe to same topic
JMS webservices can be developed with two approaches
1) 1 way request
- web client will get unblock once the request is gone to destination (Q/Topic)
- Q/Topic both can implement it
2) request - response
- web client will get unblock only after response gets back to the client
-Only Q can implement this type of web service
SOAP over JMS gives message delivery guarantee and is preferred where message critical application are deployed.
JMS provide two types of message communication
1) point to point
(A) once message is received it is removed from Q
(B) only one receiver can receive the message
2) publish / subscribe
(A) message stays on topic even after one receiver reads it
(B) multiple receivers can subscribe to same topic
JMS webservices can be developed with two approaches
1) 1 way request
- web client will get unblock once the request is gone to destination (Q/Topic)
- Q/Topic both can implement it
2) request - response
- web client will get unblock only after response gets back to the client
-Only Q can implement this type of web service