[jira] Commented: (DBCP-152) [DBCP] add a socketFactory attribute to BasicDataSource (to allow SSL thread-safe)

[ https://issues.apache.org/jira/browse/DBCP-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514474 ] Ralf Hauser commented on DBCP-152: -- Dain, thx for your explanations. Unfortunately, it appears that JSR 221:

[jira] Commented: (DBCP-155) [dbcp] allow to set = 6 parameters to do non-global SSL

[ https://issues.apache.org/jira/browse/DBCP-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514125 ] Ralf Hauser commented on DBCP-155: -- I certainly agree that you should not break the standards. However, if you can

[jira] Commented: (DBCP-152) [DBCP] add a socketFactory attribute to BasicDataSource (to allow SSL thread-safe)

[ https://issues.apache.org/jira/browse/DBCP-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514130 ] Ralf Hauser commented on DBCP-152: -- Allowing for a non-global SSL socket factory has nothing to do with mysql. Even

[jira] Created: (VALIDATOR-228) allow to cite the offending value if a validation fails as argument (Trusted-Input vs. Filter Concept)

allow to cite the offending value if a validation fails as argument (Trusted-Input vs. Filter Concept) -- Key: VALIDATOR-228 URL:

[jira] Commented: (VALIDATOR-134) [validator] create 5 or more password-policy validators

[ https://issues.apache.org/jira/browse/VALIDATOR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488431 ] Ralf Hauser commented on VALIDATOR-134: --- I thought that one advantage of open source is that you could

[jira] Commented: (FILEUPLOAD-88) [fileupload] Add a new property maxFileSize to control a size of separate uploaded file but not a whole request

[ https://issues.apache.org/jira/browse/FILEUPLOAD-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480755 ] Ralf Hauser commented on FILEUPLOAD-88: --- see also https://issues.apache.org/struts/browse/STR-1955,

[jira] Created: (VALIDATOR-227) document how to use validator in a fail-safe way

document how to use validator in a fail-safe way Key: VALIDATOR-227 URL: https://issues.apache.org/jira/browse/VALIDATOR-227 Project: Commons Validator Issue Type: Improvement

[jira] Commented: (VALIDATOR-155) [validator] Distinguish between no validation errors found and not validated

[ https://issues.apache.org/jira/browse/VALIDATOR-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480774 ] Ralf Hauser commented on VALIDATOR-155: --- see also https://issues.apache.org/struts/browse/STR-2347 and

[jira] Commented: (VALIDATOR-227) document how to use validator in a fail-safe way

[ https://issues.apache.org/jira/browse/VALIDATOR-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480775 ] Ralf Hauser commented on VALIDATOR-227: --- see also VALIDATOR-155 and

[jira] Commented: (VALIDATOR-160) [validator] Request of additional validators

[ https://issues.apache.org/jira/browse/VALIDATOR-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478759 ] Ralf Hauser commented on VALIDATOR-160: ---

[jira] Commented: (LANG-259) ValuedEnum.compareTo(Object other) not typesafe - it easily could be...

[ http://issues.apache.org/jira/browse/LANG-259?page=comments#action_12412909 ] Ralf Hauser commented on LANG-259: -- see also http://issues.apache.org/struts/browse/SB-20 SB-20 and LANG-258 ValuedEnum.compareTo(Object other) not typesafe - it easily could

[jira] Created: (LANG-259) ValuedEnum.compareTo(Object other) not typesafe - it easily could be...

ValuedEnum.compareTo(Object other) not typesafe - it easily could be... --- Key: LANG-259 URL: http://issues.apache.org/jira/browse/LANG-259 Project: Commons Lang Type: Bug Versions: 2.1

[jira] Commented: (LANG-259) ValuedEnum.compareTo(Object other) not typesafe - it easily could be...

[ http://issues.apache.org/jira/browse/LANG-259?page=comments#action_12412798 ] Ralf Hauser commented on LANG-259: -- Before just comparing the iValue - ((ValuedEnum) other).iValue it should be checked that the classes are the same! Enum

[jira] Commented: (LANG-259) ValuedEnum.compareTo(Object other) not typesafe - it easily could be...

[ http://issues.apache.org/jira/browse/LANG-259?page=comments#action_12412801 ] Ralf Hauser commented on LANG-259: -- furthermore, it would be great if the classe's init would also detect if multiple int values are the same: e.g. public static final

[jira] Commented: (LANG-259) ValuedEnum.compareTo(Object other) not typesafe - it easily could be...

[ http://issues.apache.org/jira/browse/LANG-259?page=comments#action_12412802 ] Ralf Hauser commented on LANG-259: -- similarly, it should detect double entries of this kind... public static final int JAVA1_0_VALUE = 100; public static final int

[jira] Created: (LANG-258) Enum JavaDoc: 1) outline 5.0 native Enum migration 2) warn not to use the switch() , 3) point out approaches for persistence and gui

Enum JavaDoc: 1) outline 5.0 native Enum migration 2) warn not to use the switch() , 3) point out approaches for persistence and gui Key: LANG-258

[jira] Commented: (LANG-258) Enum JavaDoc: 1) outline 5.0 native Enum migration 2) warn not to use the switch() , 3) point out approaches for persistence and gui

[ http://issues.apache.org/jira/browse/LANG-258?page=comments#action_12412643 ] Ralf Hauser commented on LANG-258: -- oops, referencing attempt 2: http://issues.apache.org/struts/browse/SB-20 Enum JavaDoc: 1) outline 5.0 native Enum migration 2) warn not