Took me a few weeks, but I finally got around to installing a free
instance of Oracle (Express Edition 10.2) and testing the null handling
code we introduced in DbUtils 1.2 (DBUTILS-31).
Sure enough, there's a bug, DBUTILS-55, but I don't think it's very
important, since it's not a regression;
Luc Maisonobe wrote:
Phil Steitz a écrit :
MATH-136 introduces rank correlation, with pluggable ranking algorithm.
The RankingAlgorithm interface and associated implementations are likely
to be reused elsewhere in the stat package. The question is where to
put RankingAlgorithm and its imple
I don't think so.
Moreover, I doubt seriously that more than one in a hundred users will
really need to replace the standard algorithms.
On Sun, Apr 12, 2009 at 9:02 AM, Luc Maisonobe wrote:
> Are ranking algorithms used
> outside of stat ?
>
Phil Steitz a écrit :
> MATH-136 introduces rank correlation, with pluggable ranking algorithm.
> The RankingAlgorithm interface and associated implementations are likely
> to be reused elsewhere in the stat package. The question is where to
> put RankingAlgorithm and its implementations. I woul
MATH-136 introduces rank correlation, with pluggable ranking algorithm.
The RankingAlgorithm interface and associated implementations are likely
to be reused elsewhere in the stat package. The question is where to
put RankingAlgorithm and its implementations. I would appreciate
feedback on t
Hi Matt,
I believe the problem can be solved this way:
// uses a handler mapping, instead of fixed handler
@ExceptionHandler(mapper=MyMapper.class)
public void test() {
try {
}
catch (IllegalArgumentException e) {
// now the correct handler comes from the mapper
HandlerUt
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-configuration-test has an issue affecting its community
integrati
