axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Fontanel <stefano.fonta...@gmail.com>
Subject Is the Axis 2 runtime compliant to soap over jms specification?
Date Mon, 25 Aug 2014 09:26:09 GMT
Hi all,
I'm evaluating Axis 2 as a client to a service that is exposed  following
the w3c specification http://www.w3.org/TR/soapjms/. The service follows
the Request-Response pattern over soap 1.1 on jms so, making it simple:

1- there ìs a persistent queue in a jms broker.
2- the client is expected to push request messages on that queue
3- the client, for every request, is expected to create a temporary queue
and to register a consumer listener on the temporary queue to wait for the
response message
4- a server component listen for request messages in the queue, processes
the messages and send in the corresponding temporary queue the response
message

I was not able to find a sample on this topic in the bundle of axis 2 so I
have tried to generate a client (using axis2-wsdl2code-maven-plugin) from a
wsdl that includes a binding with "document" style and "
http://www.w3.org/2010/soapjms/" transport. Moreover I have configured a
trasportSender for "jms" with the class:
org.apache.axis2.transport.jms.JMSSender. I have not found an alternative
implementation for the transportSender: for example a  soapoverjms one.

When I run the client the message is sent to the persistent queue but is
not compliant to the specification. For example the server component that
consumes the persistent queue (the queue with the response messages)
complains that the message is missing "SOAPJMS_contentType" property in the
header (only the content type header is present).

So the question is: I'm doing something wrong? If yes, could someone kindly
give me a reference to a sample of an Axis 2 client to take a look at its
configuration?

Thank you very much.
Stefano.

Mime
View raw message