-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy,
Andy Moller wrote:
>> 1. You are using the array "val2" here instead of "value2". Is that
>> intentional? Or, were you somewhat obfuscating your code for publication
>> on the list?
>
>
> [Chris]: It is a mistake while changing the variable na
On 1/22/07, Caldarale, Charles R <[EMAIL PROTECTED]> wrote:
> From: Andy Moller [mailto:[EMAIL PROTECTED]
> Subject: Re: Tomcat 4.x (Major Problem)
> String[] value1 = (request.getParameterValues("value_1") != null)
> ? request.getParameterValues("v
On 1/22/07, Christopher Schultz <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy,
Andy Moller wrote:
> String commonName = (String)session.getAttribute("commonName");
> String[] value1 = (request.getParameterValues("value_1") != null)
>? request.getParamete
> From: Andy Moller [mailto:[EMAIL PROTECTED]
> Subject: Re: Tomcat 4.x (Major Problem)
> String[] value1 = (request.getParameterValues("value_1") != null)
> ? request.getParameterValues("value_1")
> : new String[0];
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy,
Andy Moller wrote:
> String commonName = (String)session.getAttribute("commonName");
> String[] value1 = (request.getParameterValues("value_1") != null)
>? request.getParameterValues("value_1")
>: new String[0];
>
> String[] val
This is the current environment:
JVM: Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode)
OS: Windows 2003 server (Version 5.2.3790)
Database: Oracle 9i (Release 9.2.0.1.0)
JDBC Driver: Netdirect JDataServer Version 2.20.1
Web/application server: Tomcat-Standalone (Apache Tomcat/4.0.3) / h
> From: Andy Moller [mailto:[EMAIL PROTECTED]
> Subject: Tomcat 4.x (Major Problem)
>
> I have a strange problem that I think Tomcat is causing it,
> and I need to confirm if my assumptions are correct.
We obviously don't have access to all the data you have available, but
from what's been stat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy,
Andy Moller wrote:
> While debugging the database query logs, the reason was that the
> field type is integer, while the passed value was a "string", we went
> and inspected the code design and semantics and it was an impossible
> case that the
