Anne Thomas Manes wrote:
There are two problems with this fault message:
1- The SOAP-ENV:Fault element must be the first and only child element in
the SOAP-ENV:Body element. It cannot be a child of the ns1:SomeFunction
element. If you want to return the ns1:SomeFunction information in the
I need to deploy a SOAP application that behaves like the JMS publish-subscribe
model. The sender will broadcast the same SOAP message to multiple subscribers.
A subscriber will deploy a callback service and includes a callback URL in its
initial subscription request. Update messages will be
/style=rpc/style=document/g' -e 's/.../.../g' service.wsdl
Just wrap that in an exec in your build.xml.
Mike
Its a shame because DOC/LIT is the now and the future.
Michael Woinoski wrote:
Stuart,
I ran into the same problem yesterday. It seemed to happen when a
service implement method declares
Hi, Dimuthu.
No it's not less sleep, or more coffee, or anything else :-).
Correct me if I am wrong, but I am under the impression that axis does not
use SOAP action at all when invoking a service.
If someone wants to use doc\literal service to have multiple operations he
has to explicity map
an axis client for this.
Hope this helps(Not a complete answer, but partial).
Cheers,
Ranjith Pillai.
-Original Message-
From: Michael Woinoski [mailto:[EMAIL PROTECTED]
Sent:
Thursday, November 13, 2003 1:47 PM
To: Axis User mailing list
Subject: How to define document/literal service
Thompson, Eugene wrote:
Is it that Axis provides a communication style (message) that isn't part of
the specs?
Yes, the Axis Message style is not part of JAX-RPC. However, there is a lot of
confusion about exactly what message-style means.
The WSDL spec defines document-style operations as
Chris,
I've been trying to find a way to specified explicit headers in a WSDD.
I want these headers to appear in the WSDL document axis generates for
my web service.
Is there any way to do this? Can someone point me to an example?
I haven't found a Java2WSDL option for this, so what I do is
How can I define a document/literal service with multiple operations? Because
there's no wrapper element around the input message parts, Axis seems to have a
problem invoking the correct service method.
If I add a value for SOAPAction in the service's binding, the client stubs set
SOAPAction
tcpmon.
This way you can invoke any method in your webservice. Unfortunately I don't
know to write an axis client for this.
Hope this helps(Not a complete answer, but partial).
Cheers,
Ranjith Pillai.
-Original Message-
From: Michael Woinoski [mailto:[EMAIL PROTECTED]
Sent: Thursday
., Message-style
services.)
Read the axis users guide about service styles
specifically the message, document and wrapped service styles.
I did. I didn't find anything in the user's guide about the details of routing
document-style services.
Regards,
Mike
-Original Message-
From: Michael
methods.
Thanks,
Ranjith Pillai.
-Original Message-
From: Michael Woinoski [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 2:35 PM
To: [EMAIL PROTECTED]
Subject: Re: How to define document/literal service with multiple operatio
ns
Hi, Ranjith. What you are suggesting is basically
of SOAPAction aren't defined anywhere.
Regards,
Mike
I guess one way to avoid all of this is to have one document/literal web
service per operation but I dont think anyone recommends that.
Keith
-Original Message-
From: Michael Woinoski [mailto:[EMAIL PROTECTED]
Sent: Thursday, November
as a Web service without modification.
Regards,
Mike
Thanks,
Ranjith Pillai.
-Original Message-
From: Michael Woinoski [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 2:48 PM
To: [EMAIL PROTECTED]
Subject: Re: How to define document/literal service with multiple operations
, that bursting skull sensation...
Mike
Keith
-Original Message-
From: Michael Woinoski [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 5:48 PM
To: [EMAIL PROTECTED]
Subject: Re: How to define document/literal service with multiple
operations
Keith,
With document/literal web
= serviceDesc.getOperationByElementQName(qname);
}
}
Bug, or works-as-designed? I'll take a closer look next week when I have more
time (or less sleep, or more coffee, or...)
Mike
Michael Woinoski wrote:
Keith,
I agree with all of your points.
I dont understand web services well enough
I have written a Handler that implements javax.xml.rpc.handler.Handler. When I
try to deploy it on a client using client-config.wsdd, Axis throws a fault. The
same client-config.wsdd works fine if I replace the class with a class that
extends org.apache.axis.handlers.BasicHandler, and I can
I'm trying to implement an rpc/literal web service with Axis. I generated a WSDL
description from the Java source using Java2WSDL with --style=RPC and
--use=LITERAL. The generated WSDL binding looks fine. Then I generated
deploy.wsdd with WSDL2Java --server-side, and deployed and tested the
Most of the interesting questions on the Sun web services forum never get
answered.
I assume you're talking about the JAX-RPC forum.
I'm taking about http://forum.java.sun.com/forum.jsp?forum=331. The description
says This Forum covers JAX-RPC, JAXR, JAXM and related APIs.
The JAXB
Peter,
I must completely agree. I don't think it is intended for use beyond a
reference. We encountered problems with the WSDL generation tool, and were
unable to gain any support or ideas.
That's what I thought too. But just today I read the following on
http://jax-rpc.dev.java.net/:
The
-
From: Michael Woinoski [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2003 12:55 PM
To: Axis User mailing list
Subject: Problem installing Axis 1.1 on Tomcat 5
I'm having a problem migrating Axis from Tomcat 4 to Tomcat 5 (the
version bundled with JWSDP 1.2). I tried the same Axis
For a JAX-RPC call in Axis 1.1, what MIME type should I use for a DataHandler
that is wrapping a javax.xml.transform.Source? text/xml causes an exception.
Or should I be using a type other than Source for handling xml?
My goal is to use stubs generated by WSDL2Java to pass an XML document to a
Add a parameter to the service element:
parameter name=serviceElementName value=DocumentUpload /
You can also define parameters for wsdlServicePort and wsdlPortType for the
port and portType element names.
Cheers,
Mike
Salama, Roberto wrote:
I'm really struggling with a problem where
I've been using the Java2WSDL's -i option, and it retains the parameter names
in the WSDL. -i takes the fully-qualified implementation class name as an
argument (you still need to pass the interface as an argument to Java2WSDL). No
need to hand edit the WSDL.
-i, --implClass
optional class
SOAPMonitor works fine if I deploy a service by copying the class files to
axis's WEB-INF/classes dir. But if I copy the Axis libs into my application's
war file and deploy my application on Tomcat, I get a server error when using
the service's endpoint URL. Is it possible to use SOAPMonitor if
;-)
Thanks,
Mike
Take care,
Rick Kellogg
-Original Message-
From: Michael Woinoski [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 19, 2003 3:03 PM
To: Axis User mailing list
Subject: enabling SOAPMonitor with Axis embedded in a web app
SOAPMonitor works fine if I deploy a service
I haven't found a schema for the wsdd file yet, but here's one that works for
me:
deployment xmlns=http://xml.apache.org/axis/wsdd/;
xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
service name=StringOpsService provider=java:RPC
parameter name=className
There is an overview of the wsdd file contents at
AXIS_HOME/docs/reference.html#Deployment.
Mike
--
Mike Woinoski Pine Needle Consulting
mailto:[EMAIL PROTECTED]
The axis-wsdl2java task in Axis 1.1 is throwing an exception. axis-admin works
fine (although I had to set the classpath externally via antrc_pre.bat) and I
can run WSDL2Java from the command line. Any idea what the problem is with
axis-wsdl2java?
Here's the element in build.xml:
axis-wsdl2java
(This seems like a very basic question, but I can't find the answer in the docs
or mailing list archives.) I'm able to deploy an Axis service by copying the
class directory structure under Axis's WEB-INF/classes directory. But where do I
deploy my web service's web.xml file so I can set things
How do I set the classpath for the Ant axis-java2wsdl task so it will find my
service class? I added the directory that contains the service class to
CLASSPATH before running Ant but axis-java2wsdl still can't find the class.
Running Java2WSDL from the command line works fine.
Thanks,
Mike
--
30 matches
Mail list logo
