> One more change I want to do in jk2 is better error handling. > Most of us > spent enough time with java that using an 'int' is very > uncomfortable :-) >
error handling good :) whether this is done by return codes, exceptions, etc., personally, i don't care. what i do care about is consistency -- the same error-handling techniques used throughout jk. > My proposal is to use jk_env in the same 'style' as in JNI > programming. > Each jk method will have as the first parameter a jk_env *env ( that > requires just a bit of regexp ). > > Before the first call to a jk method, we'll use a jk_getEnv, > which will > return a (pooled) jk_env. > > env will have "errorString", "errorFile", eventually a method > throw() that > will set the things. This would allow mod_jk to report the > exact problem. > yes! an error string to explain exactly what went wrong would be great. > Exactly the same method is used in jni - a jni worker could actually > wrap JNIEnv. > > I also believe the code will be easier to read this way. > > This is obviously not 'required' - we can live without it. > Please let me > know what you think - I implement it pretty quickly. > it all sounds pretty reasonable to me. -kevin. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
