[ http://issues.apache.org/jira/browse/GERONIMO-1336?page=all ]
Joe Bohn updated GERONIMO-1336:
---
Attachment: DBPoolValidate2.patch
Aaron, I've updated the patch to ensure that min max. The patch already
prevented submit for the deploy and plan but not
[ http://issues.apache.org/jira/browse/GERONIMO-1336?page=all ]
Donald Woods updated GERONIMO-1336:
---
Fix Version: 1.1
Priority: Minor (was: Major)
Validated patch against latest 1.0 branch.
Setting the Max PoolSize on a DataBase pool with
[ http://issues.apache.org/jira/browse/GERONIMO-1336?page=all ]
Donald Woods updated GERONIMO-1336:
---
Fix Version: 1.0.1
(was: 1.1)
Setting the Max PoolSize on a DataBase pool with invalid information does not
yield an error
[ http://issues.apache.org/jira/browse/GERONIMO-1336?page=all ]
Joe Bohn updated GERONIMO-1336:
---
Attachment: DBPoolValidate.patch
Updated the JSP to validate that the min pool is = 0 and the max pool is 0
prior to submit.
This patch was created from
[ http://issues.apache.org/jira/browse/GERONIMO-1336?page=all ]
Joe Bohn updated GERONIMO-1336:
---
Geronimo Info: [Patch Available]
Setting the Max PoolSize on a DataBase pool with invalid information does not
yield an error message and silently fails
[ http://issues.apache.org/jira/browse/GERONIMO-1336?page=all ]
Matt Hogstrom updated GERONIMO-1336:
Fix Version: 1.1
(was: 1.0)
Setting the Max PoolSize on a DataBase pool with invalid information does not
yield an error
