axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nell, Roger " <>
Subject [axis2] JMS transport - temporary destinations
Date Tue, 18 Apr 2006 15:23:17 GMT
I've been mulling around the idea that a client sends a request on a well known JMS queue to
execute a service.  The reply should come back on a temporary queue that the client has created.
 Axis2 doesn't seem to be set up for this as the client names a transport/queue by setting
an option:
    options.setTransportInProtocol( "jms" );
which references a transportReceiver in the axis2.xml config file with a hard-coded queue

I can't figure out how to make that a temporary queue without hacking up axis2.  
  1. Create a new transportReceiver entry in axis2, call it TemporaryJMSListener
  2. Hackup the JNDIVendorAdapter and JMSVendorAdapter to create a temporary queue if the
destination name is blank.
  3. Extract the name of the created temporary queue name and set it as the reply-to in the
soap header.

I'm I doing something wrong?  Is there an easier way?

This e-mail contains privileged attorney-client communications and/or confidential information,
and is only for the use by the intended recipient. Receipt by an unintended recipient does
not constitute a waiver of any applicable privilege.

Reading, disclosure, discussion, dissemination, distribution or copying of this information
by anyone other than the intended recipient or his or her employees or agents is strictly
prohibited.  If you have received this communication in error, please immediately notify us
and delete the original material from your computer.

Sempra Energy Trading Corp. (SET) is not the same company as SDG&E or SoCalGas, the utilities
owned by SET's parent company.  SET is not regulated by the California Public Utilities Commission
and you do not have to buy SET's products and services to continue to receive quality regulated
service from the utilities.

View raw message