I'm pretty sure we added an additional sample in to demonstrate the
functionality (although the doc may not be). I would say that the JMS URL
stuff is pretty stable although any bugs you find would be appreciated.
Thanks,
Jaime
-Original Message-
From: Celia Berry [mailto:[EMAIL PROTECTE
Chris,
Have you tried the latest from cvs? A couple of weeks ago we added in JMS
URL support and the bindings should be correctly generated now and no longer
require modification. Let me know if I can be of further assistance.
-Jaime
Sonic Software
-Original Message-
From: Celia Berry [
Piero,
I am unaware of any JMS transport support in the C++ Axis client. Granted,
I am unfamiliar with the C++ implementation so I cannot say that decisively.
However, if you are interested in testing out a C++ JMS client for inclusion
with Axis, we provide one at Sonic Software. I would be mo
This functionality is not implemented
yet. The main thing holding us back is the implementation of a JMS URL syntax.
We have a proposal that we submitted awhile back that we intend to implement.
However other priorities have taken precedence for some time now. When we are
able to resum
Nagesh,
The JMS example does not rely on the WSDL
of the service to make the call. It uses the dynamic JAX-RPC style to call the
service and sets up everything manually before invoking.
Thanks,
Jaime
-Original Message-
From: nageshr
[mailto:[EMAIL PROTECTED]
Sent:
et my current proof of concept
> project working. I will be happy to contribute these
> when I have some time at the end of the project to
> apply them properly.
> How do I contribute the patches ?.
>
> Thanks
> James
>
> - Original Message -
> From: Jaime
James,
The reason that the JMS Connector creates and accepts BytesMessage is for
attachments support. The rationale is that the attachment encoding may not
map well into a TextMessage. However, there is nothing that says that a
simple soap message without attachments could/should not be sent as
Sola,
The first thing that I would recommend
doing is to work through the Axis JMS sample. That will give you an idea of
how to interact over Queues or Topics with web services. The next thing that I
would recommend is writing an MDB that receives messages and invokes the Axis
Server
Inline...
Thanks,
Jaime
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 31, 2003 9:31 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Antw: Asynchronous interface
>
> There's a difference between an asynchronous API and an asynchronous
> trans
Ludwig,
Which version of Axis are you using? The 1.1 beta binary distribution
doesn't contain the JMS transport (an unfortunate oversight). To build
the JMS transport you should compile it from the source dist.
A few other questions:
Have you modified the jndi-connection-factory.properties t
The sample documentation gives a pretty good walkthrough of how to
create the administered objects for SonicMQ using the Sun FSContext
implementation. These must be created before running the sample. You
should also be able to see the entries in Sonic Explorer that you have
created. Are you able
Krishnakumar,
The ClassCastException is common when the jndi administered objects are
not set up correctly. Have you followed the sample documentation for
setting up these elements? Which JMS server are you using?
If you are using SonicMQ the sample documentation describes the steps
necessary
Jon,
There is no HTTP call involved when using the Axis transport. The JMS
message contains the SOAP request. The AxisServer (or any other server
with JMS support) that is listening on the other end gets the request,
invokes a service and sends the response back over JMS. Since there is
no HTTP
Inline...
Thanks,
Jaime
-Original Message-
From: Kevin Wang [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 21, 2002 3:47 PM
To: [EMAIL PROTECTED]
Subject: RE: JMS sample
Hi Jaime,
Can I archieve this using AXIS API:
VM1 --(request)--> VM2 --(forward request)--> VM3 --(response)-
SimpleJMSListener.java (just for testing), wrap a Axis
engine,deploy a service to the engine and in the onMessage method I use
the
invoke method of the AXIS engine to call the service, it works fine.
Thanks,
Kevin
-Original Message-
From: Jaime Meritt [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 20
Kevin,
The stock sample is both a web service and a proxy to another web
service. If you pass in XXX as the symbol it returns the hard coded
value. If it is any other ticker symbol it goes to another web service
to get the actual value. The proxy behavior is just an implementation
detail. It i
erent connections, they can not access
the
same Temporary queue.
Thanks,
kevin
-Original Message-
From: Jaime Meritt [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 19, 2002 2:02 PM
To: [EMAIL PROTECTED]
Subject: RE: JMS sample can not run
Kevin,
Most of what I am referring to is located i
Wang [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 19, 2002 1:55 PM
To: [EMAIL PROTECTED]
Subject: RE: JMS sample can not run
Hi Jaime,
Are you using axis 1.0? I cannot find
sonic-connection-factory.properties.
Thanks,
Kevin
-Original Message-
From: Jaime Meritt [mailto:[EMAIL PROT
y what you are trying to do in
this use case. With a little more information we may be able to find a
solution that works out for you.
Thanks again,
Kevin
-----Original Message-
From: Jaime Meritt [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 18, 2002 5:24 PM
To: [EMAIL PROTECTED]
Kevin,
It looks like the Connection Factory you are pulling out of JNDI is not
configured correctly. Did you follow the steps in the document to setup
your connection factory in the JNDI repository? Which JNDI
implementation are you using?
Since you are using SonicMQ, another option exists in
20 matches
Mail list logo
