has been submitted to address this (see
/proposals/async_sonic/AxisAsyncClientAPI.htm).
Thanks,
Ray Chun
Sonic Software
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2003 3:09 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE
WSDD' section of the user guide:
http://ws.apache.org/axis/java/user-guide.html. Please let me know
if the docs are insufficient.
Thanks,
Ray Chun
Sonic Software
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2003 10:52 AM
To: [EMAIL
Title: Using JMS
Hi Peter,
Were in the process of enhancing
the JMS transport layer to support a JMS URL syntax,
which will allow you to use the wsdl2java-generated stub classes without
modification.
With JMS URL support, Axis will recognize
a JMS endpoint address and automatically
Hi Arul,
Yes, that's likely a problem with the actual/remote quote service (we've seen this
before).
If you are receiving the 55.25 for ticker 'XXX,' then the Axis samples.stock service
is being invoked successfully, which means your JMS transport is working.
Ray Chun
Sonic Software
Hi Satya,
You can find an example test client which uses the
JMS transport in package samples.jms.
The AxisJMSSample.pdf doc (also in samples.jms)
should cover everything you need to
get up and running.
Thanks,
Ray Chun
Sonic Software
- Original Message -
From
is for JMS. Is this something that you would like to see implemented, or will
the SimpleSessionHandler solution suffice?
Thanks,
Ray Chun
Sonic Software
Example --
1. client wsdd
deployment ...
handler type=java:org.apache.axis.handlers.SimpleSessionHandler
name