Given that the point of soap is client/language-independence...it
returns an extremely unfriendly return type. Not that intuitive how to
pick out the pieces (at least in Perl via SOAP::Lite). Then again I find
perl (as a beginner) a little difficult in general...too many ways to do
the same
My guess is that this was the first Provider implemented and was hence
the default... You could quite easily write another provider ;)
Axis is language-independent (jargon: heterogeneous) but you need the
appropriate Provider to call the back-end service. There's a lot of
scope for people to
For example, ant java2wsdl task seems to be missing --outputWsdlMode
parameter.
I'm sure there are others missing and probably for wsdl2java task as well.
Has anybody else seen this?
Plus...I'd like to see a list task for axis admin task...ala tomcat's
manager list. Just for
feel free to code these up yourself :)
If you submit a patch with the list task I would be surprised if it
doesn't get committed immediately since this wouldn't really interfere
with much.
stephen
Mike Klein wrote:
For example, ant java2wsdl task seems to be missing --outputWsdlMode
Nobody there who knows this? The Axis Dev Team perhaps...?!?
Hi!
using the property attachments.implementation an alternative implementation for the
attachment support can be configured. What is this good for? Are there alternative
implementations already?
Thanks!
Thilo
There are at least two potential implementations, DIME and MIME.
Nobody there who knows this? The Axis Dev Team perhaps...?!?
Hi!
using the property attachments.implementation an alternative
implementation for the attachment support can be configured. What is
this good for? Are there
How can we use Axis enginewithout a servlet
container?
Why can't we use Axis in standalone
mode?
In a near future we want to enable small devices
with web services, due to it's interoperability, Axis could be ower tool, maybe
integrated with jetty. why not?
Best regards,
Bruno Basílio
Sharmin Choksey [comcast] wrote:
In reference to the message posted, I am specifically interested in
knowing if there has been any development done in addressing the issue
around parsing of the XML payload sent in the SOAP body by the AXIS
runtime. I see a design issue here with respect to
here is the original wsdl fiel:
--
?xml version=1.0 encoding=utf-8?
definitions xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
Greetings,
The soap:header definition in WSDL shouldn't be mandatory? I want to fix
it in my web service in a specific operation. But, I made a post without
that header and the web service worked just fine. So, what is the
purpose of the soap:header?
About the soap:headerfault, axis is giving an
Hi!
I need to instantiate some server side WS interfaces with axis using EAR and JBoss.
Using .jws files AXIS try to compile the classes in the EAR directory
structure, and with .wsdd we have the need using the deploy tool.
For the first issue, EAR is not readable has an directory, has axis
Figured this out yesterday.
The server piece is fine. On the server in order to attach documents
with axis you just do the following:
DataSource ds = new FileDataSource(/tmp/msg.pdf);
AttachmentPart att = new AttachmentPart(new DataHandler(ds));
Message msg =
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
Title: Message
I
found these pages useful:
http://www.nsdev.org/jboss/stories/jboss-net.html
http://www.csd.abdn.ac.uk/~bscharla/teaching/mtp_software/jboss/jboss-net-HelloWorld.shtml
Hope
you do also,
-Original Message-From:
José Fortunato H. Tomás [mailto:[EMAIL PROTECTED]
Because the body element and its contents are inside the envelope's
root element. That is, this is a SOAP/XML issue, not an Axis issue.
And if you're sending XML, you should parse it to ensure
well-formedness or you'll break your receiver.
I understand that it is part of the SOAP XML
We were working on AXIS but changed the direction
towards xml-rpc after realizing that SOAP is almost 10
times slower than xml-rpc.Then i started exploring the
differences between JAX-RPC and XML-RPC(obviously
deployed some web services on APache XML-RPC).
So just wanted to know that what are the
Hi All,
I am trying to build a C++ Client for Apaches
Sample EchoAttachment Service.
1.I am not able togenerate dynamic WSDL
using
the EchoAttachmentService http://localhost:8080/axis/services/urn:EchoAttachmentsService?wsdl
This gives me
WSDLException: faultCode=OTHER_ERROR:
Canapos;t
17 matches
Mail list logo
