[jira] Commented: (DBCP-329) SQLException: Already closed.

[ https://issues.apache.org/jira/browse/DBCP-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12851355#action_12851355 ] James Carman commented on DBCP-329: --- Wouldn't a lot of this be solved by using a validation

[jira] Commented: (DBCP-329) SQLException: Already closed.

[ https://issues.apache.org/jira/browse/DBCP-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12851356#action_12851356 ] Phil Steitz commented on DBCP-329: -- Honestly, I am ambivalent on this. I can see the

[jira] Commented: (DBCP-329) SQLException: Already closed.

[ https://issues.apache.org/jira/browse/DBCP-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12851360#action_12851360 ] Phil Steitz commented on DBCP-329: -- James: good point, but the answer is not exactly. The

[jira] Commented: (DBCP-329) SQLException: Already closed.

[ https://issues.apache.org/jira/browse/DBCP-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12851384#action_12851384 ] Hontvari Jozsef commented on DBCP-329: -- If the driver returns false, something bad has

[jira] Commented: (DBCP-329) SQLException: Already closed.

[ https://issues.apache.org/jira/browse/DBCP-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12851386#action_12851386 ] Paul Benedict commented on DBCP-329: My employer does high-transaction processing --

[jira] Updated: (SCXML-114) Support for JEXL2

[ https://issues.apache.org/jira/browse/SCXML-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Biestro updated SCXML-114: Attachment: SCXML-114.patch Updated to allow jexl-1.1 in parallel with jexl-2.0 (used as default

[jira] Updated: (SCXML-114) Support for JEXL2

[ https://issues.apache.org/jira/browse/SCXML-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Biestro updated SCXML-114: Attachment: SCXML-114.patch Support for JEXL2 - Key: SCXML-114

[jira] Updated: (SCXML-114) Support for JEXL2

[ https://issues.apache.org/jira/browse/SCXML-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Biestro updated SCXML-114: Attachment: (was: SCXML-114.patch) Support for JEXL2 - Key:

[jira] Resolved: (LANG-609) Support lazy initialization using atomic variables

[ https://issues.apache.org/jira/browse/LANG-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Heger resolved LANG-609. --- Resolution: Fixed Patch applied in revision 929189. Support lazy initialization using atomic

[jira] Updated: (CODEC-96) Base64 encode() method is no longer thread-safe, breaking clients using it as a shared BinaryEncoder

[ https://issues.apache.org/jira/browse/CODEC-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julius Davies updated CODEC-96: --- Attachment: (was: codec-96-2nd-attempt.patch) Base64 encode() method is no longer thread-safe,

[jira] Updated: (CODEC-96) Base64 encode() method is no longer thread-safe, breaking clients using it as a shared BinaryEncoder

[ https://issues.apache.org/jira/browse/CODEC-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julius Davies updated CODEC-96: --- Attachment: codec-96-3rd-attempt.patch I've attached a 3rd attempt at a codec-96 patch

[jira] Created: (CLI-197) boolean option in documentation is woorking oposite way documented

boolean option in documentation is woorking oposite way documented -- Key: CLI-197 URL: https://issues.apache.org/jira/browse/CLI-197 Project: Commons CLI Issue Type: Bug

[jira] Reopened: (NET-252) Get rid of using deprecated API in VMSFTPEntryParser

[ https://issues.apache.org/jira/browse/NET-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened NET-252: -- Deprecated methods are only removed in a major version release: http://commons.apache.org/releases/versioning.html Get rid