Hi!
If anyone is still reading this thread, I just thought I would tell you
that I have figured
out why I get the Bad Types exception. It turns out that even if the
WSDL says
soap:body use=literal/ Axis still tries to interpret any type
information present
in the soap body.
My soap response
Hi,
I have a client side handler that implements onFault.
HTTPSender throws an exception (connection refused) which
appers in the client stub. This is normal behaviour. But
my handler's onFault doesn't get invoked. Why is that ?
Shouldn't Axis iterate over the completed handlers and
cal
I am trying to return a bean as a result of a web-service call. Using
TCP-monitor, I see that the XML
response on the wire is correct. However, the client bombs out with the
following stack-trace. To me it appears it cannot convert a String to a
String ?
Any ideas ?
Could not convert
Hi,
I don't exactly know if this is supposed to work this way:
when a handler throws a fault, the onFault method only gets invoked
for the handlers in the same chain. For example if the fault is in
transport chain, the global chain handlers' onFault won't be invoked.
Is this a bug ?
Perfect example and just what I was looking for.. This helps me collect metrics for
roundtirp delay in response.. Many thanks.
What I was asking earlier was a way to configure the client handler such that the
scope of the handler is like per-request-response-pair, meaning that I want the
Can anyone point me to an example of deserializing a two dimensional array?
It looks like Axis has no problem serializing it (juging from the wsdl).
Hi
I m sure this is something thats been asked before but is there
any official/spec doc that addresses how SOAP is bound to SMTP ?
The SOAP specs only address HTTP right ?
/s
Hello,
I found a bug where it is possible for the on-the-fly generation of
the wsdl to be wrong, as it can generate two methods that are the same
(duplicate methods).
Thought I would mention it as it is causing me problems, but I don't
have time to wander through the code to fix it.
Hi,
I'm new to Axis webservices and ran into some problem trying to consume
the dailyDilbert webservice advertised at
http://esynaps.com/eSynaps_home.aspx
I generated the stubs etc. classes using the WSDL2Java util provided by axis
and used those classes to talk to the webservices.
It
Actually I am using Soap implementation 2.3.1.
I just want to try my luck here with AXIS.
I need to resolve the problem as soon as possible, so please
accept my apology for sending this email to axis user list.
I got the following error message from the server:
Hi all,
has anyone had trouble using char properties with Apache SOAP?
TIA,
Alphonsus.
I am also interested in sending soap messages via smtp, so if any one
can point me in a direction that would help . . .
I am certainly not above writing code to implement this feature, but I
just don't know where to begin.
-jason
On Thursday, October 3, 2002, at 12:22 PM, Sam wrote:
Hi
I just submitted a paper to IBM DeveloperWorks about an implementation
I've done, doing both raw SMTP as well as polling a POP server, and
passing the emails on to Axis. Contact me directly if you need to move
fast on this.
Ken
Jason Essington wrote:
I am also interested in sending soap
Can anyone explain (or point to documentation) that tells me how I can
change the axis environment's default socket factory (and default secure
socket factory).
My goal is to have the class
org.apache.axis.components.net.SocketFactoryFactory return a custome socket
factory that I've written for
there is no char in XML Schema. You could add a hack into Axis to send
chars, but nothing at the far end will map it to a char again.
This will take consensus among Soap platform builders. Till then, send a
short string.
- Original Message -
From: Jianliang Zhao [EMAIL PROTECTED]
To:
Steve,
Thanks a lot for your reply. If I wrote a custom serializer and deserializer for
char.class, will it work? Will I get cast exception at deserialization time if I
return a Char object?
Thanks,
Jianliang
-Original Message-
From: Steve Loughran [mailto:[EMAIL PROTECTED]]
Sent:
Problem solved.
Stupid mistake: Service constructor takes the wsdl doc NOT the endpoint URL!
Kell
From: Kell Ng [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Problem with consuming DailyDilbert webservices.
Date: Thu, 03 Oct 2002 12:08:38 -0700
Hi,
I'm new to
Hi,
It's not SOAP, but I have been able to send test XMLRPC messages via SMTP
with the XML
as a Mime attachment, check out http://switchrmi.sf.net
I used the Apache James Mailet API to test receipt of the email and
processing of the XMLRPC message.
All of the source code is browsable in HTML
Hi,
I'm a new user to Axis, just downloaded it and playing around with it (Axis
RC1)
I was under the impression that when you invoke an Axis webservice, you
need to specify the correct namespace for the Service and/or operation
name.
But it seems to be working even if you provide the incorrect
Jianliang Zhao wrote:
I got the same problem and didn't find anything in the documentation to deal with it.
Could someone give us a solution?
I believe byte is a possible data type, and as long as the datatype is
8 bits it shouldn't matter, you can convert back and forth.
Trying the Admin Servlet in RC2 and I continue
to get 404.
I am able to validate that I have the correct
jar installed per step5 on install.html.
I can see that axis/WEB-INF/lib/axis.jar has an
org.apache.axis.Transport.AdminServlet.class.
Does there need to be a web.xml that does a mapping
to
I've just put my slides on a talk I'm giving this evening on interop (*) up
on the web, plus a demo of .NET /axis interop testing.
http://www.iseran.com/Steve/papers/interop/
I'll pull the tests into the axis framework after the weekend -it deploys a
.aspx file to a local server then builds an
I got the same problem and didn't find anything in the documentation to deal with it.
Could someone give us a solution?
-Original Message-
From: Alphonsus [mailto:[EMAIL PROTECTED]]
Sent: 2002?10?3? 12:21
To: SOAP List
Subject: Char datatypes with SOAP
Hi all,
has anyone had
Hi All,
I was using the auto typing feature in RC1, and it was working fine. After I upgraded
Axis to RC2, the WSDL generation works fine with automatic type mapping for java types
without explicit type mapping, but at the serialization time, I got the error saying
no serializer found for the
24 matches
Mail list logo