791: [1] In HTTPUtil:post, start...
Jul 27, 2001 11:40:07:871: [3] In HTTPUtils:post, call doPost with HTTP 1.0.
Jul 27, 2001 11:40:07:921: [1] In HTTPUtil:post, end...
Ouch, the call failed:
Fault Code = SOAP-ENV:Server.Exception:
Fault String = java.lang.NoSuchMethodError
.
Thanks,
Richard
_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>From the FAQ in the docs for soap 2.2:
1.5 Help! The Samples won't work. Every time I run a sample client I get
this response: "Fault String = java.lang.NoSuchMethodError"
Ensure that:
(a) You have deployed the sample service you want to use.
(b) Xerces.jar is the very first entry in your clas
Yes, it is possible, but a bit painful. Which is very ironic since the point
of SOAP is interop. Apache SOAP does not need or use WSDL. But that does not
mean that you can't have a WSDL file describing your services for clients
that can make use of WSDL. With MS you can also use the low level api
If you are just looking for a debugging tool check out the TCPTunnel in the
docs.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 07, 2001 1:48 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Problem with getting Response
>
>
>
Apache SOAP 2.1 and 2.2 do require xs:type attributes. You can get around
this by adding QNames for your parameters in the type mapping registry. This
is covered in the docs for Apache SOAP 2.1
Rick Hansen
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent:
This is a SOAP response I captured recently.
http://schemas.xmlsoap.org/soap/encoding/";
xsi:type="ns3:Array" ns3:arrayType="xsd:string[3]">
MN-CS
WI-CS
IA-CS
> Can someone please send me an example of how an array is
> represented in the
> XML?
> I want to write a small C client the send
I tried the 7-29 nightly build. My simple test showed that running locally
in Tomcat, the average time to make 100 SOAP calls dropped from 3.1 to 2.9
seconds. Not huge but measurable.
Rick Hansen
> -Original Message-
> From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED]]
> Sent: Thursday
"Unable to resolve target" normally means the service class can not be
found. Normally, the class name would follow. I got "null" when my service
class was found but could not be constructed.
Rick Hansen
> -Original Message-
> From: Brett McLaughlin [mailto:[EMAIL PROTECTED]]
> Sent: Wed
://xml.org/sax/features/namespaces",true );
saxParser.setFeature(
"http://apache.org/xml/features/validation/schema",true );
saxParser.parse(inputSource);
Thanks!
Richard Wu
My own code caused the problem. Sorry for the spam. Now I have a lot of
faith in xerces parser now. BTW: anyone knows when xerces-j-2 is available
for a big time?
-Original Message-
From: Richard Wu [mailto:[EMAIL PROTECTED]]
Sent: July 23, 2001 2:55 PM
To: '[EMAIL PROTECTED]
If you would pay closer attention to the post it does not say you have a
classpath problem. It say you might have a Tomcat problem. Have you done
what was suggested? This is a well known and well documented problem with
tomcat startup. It makes no difference where you have xerces in your system
cl
>
> set CP=I:\Misc\dev\xerces-1_3_1\xerces.jar;%TOMCAT_HOME%\classes
As I recall xerces 1.31 does not work. Try an earlier or later version.
> But still i am getting the same error.
>
Is "test_AddThemResult" the correct name of the XML element the response is
comming back in? Have you used the TCPTunnelGui to verify the XML that is
comming back? That's all I can think of.
Rick Hansen
did you look into crimson?
-Original Message-
From: Alfred [mailto:[EMAIL PROTECTED]]
Sent: July 24, 2001 12:49 PM
To: [EMAIL PROTECTED]
Subject: RE: soap and xerces jars
Hi Matt,
Thanks for the tip. Do you or anyone else know where I can find smaller
JAXP compliant parsers. Thanks
> enough about XML
> to understand why the Apache libraries are generating this XML.
>
> Does anyone know of a fix for this? If someone knows how to
> use the Apache
> SOAP libraries to not add that "ns1" that would be great. If
> there are any
> other solu
y(String id) throws SOAPException ;
search through DeploymentDescriptors to find the service
}
--Richard
On Mon, 6 Aug 2001, Anvita Johri wrote:
> I am trying to figure out if it is possible to use multiple
> DeployedServices.ds files in a soap client-server call.
>
> I
If you are running Tomcat, undeploy the service, restart Tomcat, and
redeploy it. The changes should then be visible. Tomcat doesn't refresh
it's copy of the classes, even if you undeploy and redeploy the service
without restarting Tomcat.
--Richard
On Wed, 15 Aug 2001, Ravi Natar
Don't
know for sure, but I thought there were some issues between MS SOAP and Apache
SOAP. You may want to double check the Apach SOAP docs I think I remember
something in there about this.
Regards,
Richard
-Original Message-From: chihongkim
[mailto:[EMAIL PROTECTED]
When I try to deploy SOAP using Tomcat 4.0, I can sometimes bring up the
SOAP admin client (http://localhost:8080/soap), but when I try to list,
deploy, undeploy, etc. services using the ServiceManagerClient, it says
that the RPCRouterServlet isn't a servlet. I'm currently running SOAP 2.2
under L
Before I dive into any code changes, has anyone else had problems with the
DateSerialzier? I have a SOAP method that has a Date as one of the params.
When it gets two simultaneous calls the dates seem to be wrong, not the same
as what was passed to call.invoke(). As far as I can tell good dates ar
It appears that the DateSerializer does need some synchronized blocks. I
verified that the Date output from unmarshall() is not always equivalent to
the string value input to unmarshall(). So, I placed synchronized blocks
around the SimpleDateFormat.format() calls. This seems to have fixed the
pro
d
with the soap.jar in my classpath, with the same results as I indicated
below. This is really puzzling, as I would figure if it was a change in
the servlet.jar that did it, then Tomcat 3.2.2 wouldn't like it either,
but it's fine.
Thanks.
--Richard
On Thu, 16 Aug 2001, Scott Nic
No, it means that SOAP server calls the service methods of the single
instance as many times as it needs to handle the number of client requests.
Your service code must be thread safe.
Rick Hansen
> -Original Message-
> From: Naresh Agarwal [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, Se
ibute =
targetDocument.createAttribute(sourceAttribute.getNodeName());
targetAttribute.setNodeValue(sourceAattribute.getNodeValue());
targetNode.appendChild(targetAttribute);
Any idea of what's happening here?
Thanks for any hint or suggestion!
Richard Wu
Hi, we can convert an XML document text string to an XML dom via
StingReader/InputStream but can we convert an XML dom to an XML document
text string via StringWriter/OutputStream?
I tried to figure this out but not sure where to start.
Really any suggestion or idea!
Richard Wu
I must say that I am enjoying this thread immensely. :-) But I have an odd
sense of humor and love a friendly and spirited argument.
Rick Hansen
> -Original Message-
> From: Sam Ruby [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 28, 2001 2:51 PM
> To: [EMAIL PROTECTED]
> Subject:
What is the upper limit for connections with a non-server version of the microsoft OS?
I'm having some performance problems as well and I'm testing on Win2K workstation.
How is this connection limit enforced? At the TCP/IP stack level or the socket level
(or some other way)?
Rich
-Orig
catch".
*******
Richard A. Sitze
[EMAIL
Greetings!
After much trouble shooting, I have successfully used the Apache SOAP Toolkit under
the Java Plugin 1.3.1_02. To do so, you need to add the following to your client
applet jar: activation.jar, soap.jar, mail.jar and crimson.jar. Then you will need to
sign your jar. The use of crim
I recently tried upgrading to the latest nightly build of SOAP (June 20,
2003) from 2.2. I needed this to support HTTPS over a proxy server.
The problem I had was that it suddenly started using a different SOAP
serializer type for byte[] content (Base64Serializer instead of Base64).
I had to chan
4 type?
-Original Message-
From: Richard Bolen
Sent: Monday, June 23, 2003 9:46 AM
To: [EMAIL PROTECTED]
Subject: Base64 --> Base64Serializer - Why?
I recently tried upgrading to the latest nightly build of SOAP (June 20,
2003) from 2.2. I needed this to support HTTPS over a proxy serv
SOAP
could sense older clients (specifically, ones using the 1999 schema)
and use older the older schema for serialization, but the current
code does not do that.
On 23 Jun 2003 at 10:38, Richard Bolen wrote:
> Perhaps more to the point is what the xsi:type attribute is set to for
>
is it possible to make the return type Upper case?
123456789A
..where I would like 'OrderID' to reflect the return object type as well as
the runtime value? Like so:
123456789A
I'm using BeanSerializer and mapping:
...Constants.NS_URI_SOAP_ENC, new QName("[snip]","OrderID")...
It's worki
33 matches
Mail list logo
