Dear Scott,
I don't do anything special as far as I know. I think the fault is generated
by the apache tool kit.
Let me send you the complete method again. May be its easy to understand
when u look at the full method. If you look at the arguments of my client
method, sourceBytes are never null but
To provide more information, could you please add a line of code:
Fault fault = resp.getFault();
System.err.println("Generated fault: ");
System.out.println(" Fault Code = " + fault.getFaultCode());
System.out.println(" Fault String = " + fault.getFaultString());
+++ System.ou
Hi,
I am using SOAP for last 2 weeks .I am able to run the simple sample
examples.
I also went thro' the SOAP documentation.Now i want to explore SOAP and
WSDL.
I was refering Java and SOAP book by oreilly .Could any one guide some
better resources for this?.
Thanx & Regards,
Vijay
--
This comm
Even though I have a deployment descriptor and the line
org.apache.soap.server.DOMFaultListener is in a separate line, I deployed the services using the soap admin
client that apache provided. I got NoClassDefFound errors when I tried to
deploy using deployment descriptor.
Here is the trace after
Forgot to mention one thing in my last email.
The admin client for deploying soap services does not have any provision for
specifying the faultListener. Probably thats the reason I don't see any
extra info even with fault.toString().
Should I deploy the services using deployment services. I used th
There is a wsdl tool that you can use to create the .wsdl.
http://www.alphaworks.ibm.com/tech/webservicestoolkit
http://xml.apache.org/axis/
I did .NET and J2EE integration using wsdl. It is very helpful.
Hongfan
-Original Message-
From: Vijay Shinde [mailto:[EMAIL PROTECTED]]
Sent: Wedne
Hello Johannes,
You may want to consider a product called XAware, which is a
set of data integration components which can do exactly what you are talking
about. XAware uses XML as the core technology for information exchange, and
easily allows connection to and mapping to and from rela
Ugh. I never noticed that the admin GUI does not allow one to specify a
fault listener.
To get to the bottom of this, I wrote my own sample client and service.
I got the "no signature match" error when I passed a null DataHandler,
because the Apache SOAP code serializes a DataHandler as xsd:anyTy
Thanks a lot Scott.
If nothing works out, I will pass in some dummy bytes and work around.
Once again I really appreciate your help.
Do you think its better to migrate to Axis, since we are using attachments
extensively. Whats your suggestion?
Thanks
Praveen
- Original Message -
From: "
If your attachments will be several megabytes, you might benefit from
using Axis. Apache SOAP still creates an image of the whole payload in
memory, which gets to be a problem with large attachments. While
improving this is on the to-do list for SOAP, I do not know when it will
be done.
I person
Hi Tony,
The main issue is, that we want to have
multiple tomcat servers (=SOAP clients) running, which should be able to
connect to the backend, an Apache SOAP Tomcat Server. The SOAP clients
will issue SELECT/UPDATE SQL calls to the SOAP Tomcat Server, which executes
and returns the resultsets.
Even though we may not be using large files for attachments, this service
will be called many times by the same or many clients to import content into
the system. For example, one of clients uploads 5000 contents which means it
calls the methods 5000 times. Ofcourse client uses session pooling, so
Vijay,
If you are just starting out with SOAP, I suggest you use Apache Axis rather
than Apache SOAP (http://xml.apache.org/axis).
Axis is the follow-on/replacement project to SOAP.
SOAP doesn't support WSDL. Axis does support WSDL.
SOAP uses a proprietary API. Axis uses the standard JAX-RPC API.
13 matches
Mail list logo
