You could test this with simple axis server and debug the same on Linux
with gdb.
I have written a small help file to let you know how to get simple axis
server up and running on Windows. I hope you could adopt this to Linux.
I have it http://people.apache.org/~samisa/SimpleAxisServer_HOWTO.txt
I have added this how to content for windows into the win install guide
and commited this into cvs.
Please see
http://cvs.apache.org/viewcvs.cgi/*checkout*/ws-axis/c/docs/wininstall-guide.html#simpleaxis
Plan to update the Linux guide as well.
Thanks,
Samisa...
On Thu, 2005-05-05 at 14:05,
Would appreciate thoughts on this.
Please see the mail tail below.
Thanks,
Samisa...
-Forwarded Message-
From: John Hawkins [EMAIL PROTECTED]
To: Apache AXIS C Developers List axis-c-dev@ws.apache.org
Subject: Re: Apache 2.0 vs Apache 1.3
Date: Thu, 05 May 2005 11:17:27 +0100
I've
I also think that it would be better to support only for Apache 2.
Regds
Rangika
On Thu, 2005-05-05 at 16:25 +, Samisa Abeysinghe wrote:
Would appreciate thoughts on this.
Please see the mail tail below.
Thanks,
Samisa...
-Forwarded Message-
From: John Hawkins [EMAIL
I've lots of users who still use Apache 1.3, though personally I use 2.0. It
isn't just a question of the systems we developers use: we have in turn to
support users hosting our developed services who are running pretty
unsophisticated systems. Given that it works nicely now and is not too hard
Good day all,
Right now I am using Apache 1.3, because when I started to read
documentation and user postings, I got the sense that Axis is more
stable with Apache 1.3. I'd like to see the support for that version of
Apache stay for now, unless I am wrong about the stability issue.
Thanks,
Will have a look at you wsdl and see if I could get it working. Please
try simple axis server in the mean time.
Thanks,
Samisa...
Thanks. I tried simple axis server with gdb, and was able to debug my
server. It now is able to log its inputs and outputs, and they look
basically right.
Linux Mandrake 10.0
I've got a web service that needs to send a fault back under some
conditions.
It appears that the sample files for version 1.5 don't work, and neither
does my app (undeclared namespace prefix in the fault message). I suspect
this may be a bug, since the sample doclitfault
This seems to be a bug. SOAP faults on the server side are not well
tested. On client side, there has been some testing. I also have come
across in the past, where the server sends faults in invalid formats.
Hence, this needs be fixed.
Samisa...
On Thu, 2005-05-05 at 20:35, Ian Harder wrote:
Looks to me as if there are serialization problems on the server side.
I guess this is something to do with errors in the manipulation of the
pointer data members of the class being serialized by server for
response.
One thing to figure out is to know whether the error is in generated
code or in
OK, Looks like the responses are more biased towards keeping both.
One of the main reasons that I raised this was to cut down on
maintenance efforts, not only the code, but also the docs.
In some situations, such as in case of supporting attachments Rangika
seem to have to update both modules.
Hi,
I know this is off topic, but I think it may help you.
There is a much cleaner way to setup LogFactory on Websphere, without
doing the PARENT-LAST trick. See
http://www-1.ibm.com/support/docview.wss?uid=swg27004610 for details
[EMAIL PROTECTED] wrote:
I also had to specify a name-value pair
Good Afternoon to all,
I'm happy about joining the group, looking forward for
some help from you all.
I've the following queries when i need to expose a
java component into web service.
I use axis for the task[using java2wsdl and wsdl2java]
The following are my queries:
1. If i obtain a wsdl
Hi,
thanks for your help. I'll try to regenerate and rebuild my service with the
WRAPPED style.
I think i write my experiences to a little quick start and post it to the
subject [CO] writing a tutorial.
Best Regards
Harri
axis-user@ws.apache.org schrieb am 04.05.05 06:14:58:
When using
Hello Everybody,
I have the same Lyndon's problem, because I deploy a java webservice
that incapsulate response data into a Hashmap (whose name is dati,
please see below) using a wsdd file.
The kind of response data into the Hashmap is of type Costruttore and
doesn't appear in wsdl file, so the
Hi; why don't you use document instead of Hashmaps? In this way you can pass an
XML rapresentation of your dati and then from the XML you can create your
Java-structure.
-- Initial Header ---
From : Claudia Mavilio [EMAIL PROTECTED]
To : axis-user@ws.apache.org
Cc
Hi all
I've created a method that adds a soap header
I'm not sure what to put here - new SOAPHeaderElement (http://)
Also i'm testing this using eclipse and the wtp tool. But can't see the
header being created
Can anyone suggest how i test this to see the header?
Do i have to use
I've generated stub functions from a wsdl file and most of the time
invoking those methods runs correctly however when I pass a long
string as one parameter I get the traceback at the foot of this
message.
The generated method is as follows
public int sendMessage(java.lang.String username,
Hi all
I've created a method that creats a soap header and i want to test it to
make sure the header is being created. Please can someone help me ahieve
this.
My method
public static String addSOAPHeader(String token) throws Exception
{
Service service = new Service();
I get this error when creating a web service using eclipse wtp tools
Can anyone enlighten me to what this means and how i fix it
I've had no response from eclipse forums
Many thanks for your help
IWAB0489E Error when deploying Web service to Axis runtime
axis-admin failed with
Clint,
hm, I have no Axis specific code in my web service. I just wrote a
JAX-RPC compliant web service and added Axis to my web app and then let
Axis generate the WSDL and all for me in the deploy (wsdd) step. I think
I even did not try to write a client utilizing Axis, I just have
But, maybe
Dear list,
I'm new to Axis, but not to web-services development. I've developed
web services clients for the Mac, which communicate to .NET based
services. Now, I'm involved in ditching the .NET work, in favor of Axis.
Anyway, we have a few Mac clients, which send some data Base64
encoded.
Somebody should upgrade the http://ws.apache.org/axis/ main page:
doesnt show the 1.2 release yet.
Christian Faucher
On 5/4/05, Glen Daniels [EMAIL PROTECTED] wrote:
Hi folks:
After *much* too long, the Axis team would like to announce the release
of Axis 1.2 final. You can get it at:
Merten,
we are interested in fixing this...but there just so many things to do
and so few hours in a day :)
-- dims
On 5/5/05, Merten Schumann [EMAIL PROTECTED] wrote:
Clint,
hm, I have no Axis specific code in my web service. I just wrote a
JAX-RPC compliant web service and added Axis to
I have a web application with an embedded instance of Axis 1.2 final in
it. We were using JDK 1.4.2, but in preparation for JDK 5, I started
running some tests. One of those tests was to create a JDK5 enumeration
and have my web service run/use it. Just a note, my web service now has
both JDK
The fault string that I get back is this:
org.xml.sax.SAXException: Deserializing parameter 'inPassword':
could not find deserializer for type {http://www.w3.org/2001/
XMLSchema}base64
Don't know if that will help. Thanks for your help so far.
-Dan.
On May 5, 2005, at 12:56 PM, Jeff Greif
26 matches
Mail list logo
