https://issues.apache.org/bugzilla/show_bug.cgi?id=54395
Filip Hanik fha...@apache.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.apache.org/bugzilla/show_bug.cgi?id=54395
--- Comment #1 from Glen Taylor inetdev...@gmail.com ---
Created attachment 29833
-- https://issues.apache.org/bugzilla/attachment.cgi?id=29833action=edit
Patch for PoolProperties.java
--
You are receiving this mail because:
You are the
https://issues.apache.org/bugzilla/show_bug.cgi?id=54395
--- Comment #2 from Glen Taylor inetdev...@gmail.com ---
Created attachment 29835
-- https://issues.apache.org/bugzilla/attachment.cgi?id=29835action=edit
New unit test for parser
--
You are receiving this mail because:
You are the
https://issues.apache.org/bugzilla/show_bug.cgi?id=54395
--- Comment #3 from Christopher Schultz ch...@christopherschultz.net ---
FWIW, test cases using the following idiom:
caught = null;
try {
props.getJdbcInterceptorsAsArray();
} catch
https://issues.apache.org/bugzilla/show_bug.cgi?id=54395
Glen Taylor inetdevboy+apa...@gmail.com changed:
What|Removed |Added
Attachment #29835|0 |1
https://issues.apache.org/bugzilla/show_bug.cgi?id=54395
Glen Taylor inetdevboy+apa...@gmail.com changed:
What|Removed |Added
Attachment #29836|application/octet-stream
https://issues.apache.org/bugzilla/show_bug.cgi?id=54395
--- Comment #5 from Konstantin Kolinko knst.koli...@gmail.com ---
(In reply to comment #3)
FWIW, test cases using the following idiom:
(..)
can be written somewhat more simply like this:
try {
https://issues.apache.org/bugzilla/show_bug.cgi?id=54395
--- Comment #6 from Christopher Schultz ch...@christopherschultz.net ---
Sorry, yes, I meant fail().
As for throws Exception doesn't that change a failure into an error when
JUnit runs?
--
You are receiving this mail because:
You are the
