PROTECTED] wrote:
Yes, I'm trying to call 2 different webservices using one application and
one
client-config.wsdd file.
Mike Krell-4 wrote:
What is it that you are trying to accomplish by having 2 HTTP
transports?
Is it just a matter of calling 2 different webservices? The reason why
I
Try changing this in the wsdd file
parameter name=disablePrettyXML value=false /
to true.
On 9/28/07, yangguo2020 [EMAIL PROTECTED] wrote:
Hi all,
I am using Axis 1.1 to publish my webservice; however I realize the soap
response generated by the Axis will be autoformated (eg with
protocol? I
want to use 2 different handlers for an http request.
So in reality I want to do this however, I don't know how to do it
programmatically.
transport name=http pivot=java:
org.apache.axis.transport.http.HTTPSender/
transport name=http pivot=java:myownHandler/
Mike Krell-4 wrote
What is it that you are trying to accomplish by having 2 HTTP transports?
Is it just a matter of calling 2 different webservices? The reason why I
ask is the solution may not be in the transport itself but in a handler.
On 9/27/07, Yolanda Ward [EMAIL PROTECTED] wrote:
You are right, you can
I have a couple of questions. Are X, Y, and Z in different JVMs or separate
machines? The webservice that you are call, does it ever receive the soap
message and do work on it or does it just modify the soap to a different
XML? Is it the modified xml that is sent to Z where all the magic
I do something similar. I grab the SOAPMessage and parse a couple of
attributes of the message. The whole thing then gets stored into a
database. I had to create a custom handler to do this work and then insert
the handler into the handler chain.
Once the handler gets the message you will have
Does anyone know how to Java2WSDL to generate a wsdl which has a JMS url as
the endpoint?
I'm using Axis 1.4. I have a Stateless EJB deployed in JBoss as a
webservice. My webservice has a custom handler that intercepts the soap
message and persists it into a database. The soap message then continues on
its way to the EJB. This all works great.
I'm trying to write a client that
Does anyone know how to configure JMS with Axis? I'm using 1.4 and can't
seem to get it going. I've looked at the docs and samples but still
struggling. Thanks
Does anyone know how to configure JMS to be used with Axis? I've read the
docs and samples and I'm still struggling. Thanks
/parameter
/service
4. I'm moving over to WebSphere MQ as the MOM provider, but haven't got
that far yet - but I assume its only a change to the JNDI properties in
axis2.xml as is the case with other JMS stuff.
cheers,
Ants.
Mike Krell wrote:
Does anyone know how to configure JMS to be used
HellobrbrI#39;m currently using Axis 1.3 with JBoss 4.x and web servic=
es.nbsp; My web service endpoint is an EJB and the transport is HTTP.nbsp=
; I have everything working in this set up.nbsp; I would like to change th=
e transport to use JMS.nbsp; I#39;ve configured a JMS queue using JBossMQ=
12 matches
Mail list logo
