On 19 oct. 08, at 23:31, Senaka Fernando wrote:
Hi all,
I'm working on the implementation of the MapMessage support in the JMS
Transport. I would like to know a few things regarding the existing
JMS
Transport implementation.
1. What's the purpose of
org.apache.axis2.transport.base.MetricsCollector's
metrics.incrementBytesSent() in the JMS Transport? Is this an
essential
thing?
2. As far as I understand, when a JMS BytesMessage or a JMS
TextMessage
arrives, the incoming payload's binary representation is extracted
and then
converted into an Axiom representation within the JMS layer. Did I
get this
right?
That is correct, but the strategy implemented in this part of the code
(around BaseUtils#setSOAPEnvelope) is invalid. The JMS transport
(together with the AMQP transport) is the only transport that still
relies on this code. It will be removed in the future and the
transport will rely on message builders to do the job. See SYNAPSE-304
for more details.
3. What does jmsPayloadType == null in JMSSender.java:395 mean?
Many Thanks,
Senaka
