Thanks Martin,

It's quite posible JAI wasn't installed with the dlls ... I'm fine with either solution. I wouldn't be opposed to including you comments below in the test case code too (some form of comment).

Cheers,

DZ

On 1/3/06, Martin Desruisseaux <[EMAIL PROTECTED]> wrote:
David Zwiers a écrit :
> I ran into a failure, [...snip...] the code). Can you confirm?
>
> [junit] [ERROR] TEST org.geotools.coverage.grid.OperationsTest FAILED
>
> ------------- Standard Error -----------------
> Could not load mediaLib accelerator wrapper classes. Continuing in pure Java mode.
> ------------- ---------------- ---------------
> Testcase: testSubtract(org.geotools.coverage.grid.OperationsTest):    FAILED

Tested with Maven 1.0.2 on J2SE 1.4.2 (Windows XP). I have been able to
reproduce the bug when the mediaLib accelerator classes are not present.
Just dropping the 'mlib_jai.dll' and 'mlib_jai_mmx.dll' files in jre/bin
fix the bug (make sure that the 'mlibwrapper_jai.jar' file is also in
jre/lib/ext).

The .dll files should be there if JAI has been installed with the Sun
standard installation program (jai-1_1_2_01-lib-windows-i586-jdk.exe ).
With such installation, everything should run fine. The .dll files are
probably missing if JAI has been put in the classpath by Maven, like our
attempt on the 2.1 branch.

This behavior looks like a JAI bug to me. In theory, the pure Java mode
is supposed to produce exactly the same result than the mediaLib native
mode; just slower. This test failure suggests that it is not always the
case. The mediaLib native code seems right in this case (the bug would
be in the pure Java code).

What should we do? Possibilities are:

   - Do nothing. Geotools developpers would need a "real" JAI
     installation on their machine if they want to build with
     Maven. Other users or developpers (anyone who don't run
     the test suite) can continue with pure Java JAR file (from
     Maven repository of anywhere else) if they wish. The bug is
     probably in a deep corner that will not affect a majority of
     developpers.

   - Comment out the test that fails, or print a warning instead.

        Martin.

Reply via email to