Unlike the HTTP protocol there's no stable default JMS listener for invoking
the Web Services exposed in Apache Axis 1.x using JMS (Java Message Service)
as the transport protocol - other than the one provided merely for demo
purposes.
This article describes a fully working generic JMS listener that can act as a
JMS transport receiver handler for Axis and allow service clients to uniquely
address individual Web Services in a JMS way and invoke them over JMS.
Apache Axis is a popular Java-based Open Source platform for exposing Web
Services. It has native support for handling invocations into Web Services
based on the SOAP (Simple Object Access Protocol) application protocol. By
default, the Axis server supports HTTP as the protocol for transporting the
SOAP payload and ... (more)
Applications that have high performance as a quality goal would motivate a
programmer to design and build them as multithreaded apps. The Java
programming environment provides for parallel execution of logic by using
threads. However, this is at a lower level and provides limited capability.
To make multithreading work successfully in an application, programmers have
to handle higher-leve... (more)