Possible JNI bug

[Jesus 0]

JET vm and Sun vm are differents in this JNI situation:

extern "C" {

 JNIEXPORT jXXX JNICALL classname_Test(JNIEnv * env, jobject jobj,...)

 {

 int length=0;

 jbyteArray  mArrayHandle = env->NewByteArray( length );

 jbyte * mBuffer = env->GetByteArrayElements( mArrayHandle, NULL );

 if( mBuffer == NULL )

    printf("mBuffer nulo en JET vm");

 else

    print("mBuffer no nulo en Sun vm");

 .......

 return ...;

 }

}

The question is that in third party librarys, this real situation cant be controled.

The real situation is jaybird.dll, that is part of the open source proyect firebird.sourceforge.net

[zztop 0]

That is a difference between Java Platform Specification and Java Reference Implementation (HotSpot).

It will be fixed in JET 3.7 (March 2005)