Richard,
I believe these exceptions should NOT be logged as 'info' but rather 'debug'.
This produces noisy output during our functional tests, which means users
will see noisy output for their programs.
--
Tom Jordahl
Macromedia
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
1) The user-guide had a section that instructed the user to add an
addParameter call to example1. I tried this, and of course it blew up
because now setReturnType must be called if addParameter is called. So I
changed the user-guide text to indicate that both calls need to be added...
2) Didn't
Two things:
- addParameter example fails because now setReturnType is necessary.
Updated the discussion to ensure setReturnType is used.
I'm not sure I understand. Do you mean the
samples/userguide/example2/TestClient.java failed? Or just the code in
the user's guide? They S
I can certainly optimize this code, do ONE check for startsWith("javax")
before doing all the other checks. But if we change to use the JAX-RPC
properties in place of our own, then we'll go down the full verification
path anyway.
I don't think you're being paranoid. I think JAX-RPC is being par
Hm. I'm getting very concerned about performance as more and more string compares on
strings like "javax.xml.rpc..." need to be done during critical-path code. Am I being
paranoid about this?
--G
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wedne
> Should we keep setMaintainSession?
I vote to keep it.
--
Tom Jordahl
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 06, 2002 10:17 AM
To: [EMAIL PROTECTED]
Subject: cvs commit: xml-axis/java/src/org/apache/axis/utils
resources.properti
