MqContextC - protect and restore the service-environment … More...
Functions | |
native void | jvmqmsgque.MqContextC.EnvProtect () |
Java: → C-API protect the service-environment | |
native void | jvmqmsgque.MqContextC.EnvRestore () |
Java: → C-API restore the service-environment | |
JNIEXPORT void JNICALL | Java_jvmqmsgque_MqContextC_EnvProtect (JNIEnv *env, jobject self) |
Java: → C-API protect the service-environment | |
JNIEXPORT void JNICALL | Java_jvmqmsgque_MqContextC_EnvRestore (JNIEnv *env, jobject self) |
Java: → C-API restore the service-environment | |
MqContextC - protect and restore the service-environment …
The "Env" style functions are used to secure the service-environment (defined in MqEnvS)
and is required.. under special conditions... to proper answer the original service call at the
end of the service-processing.
By default jvmqmsgque guarantee the proper management of the environment on behalf of the user.
Under normal conditions the user don't need these functions.
The folllowing design-goals were defined:
come-in == come-out
The two design-goals from above are in conflict and the both functions MqEnvProtect and MqEnvRestore are used to solve this conflict.
Example from server.java
→ protect the environment and import from database
// PROTECT the original service-call EnvProtect(); // OVERWRITE the original service-call with data from the database dump.Import(server.this); MkBufferListC read = ReadALL(); // RESTORE the original service-call EnvRestore(); // ANSWER the original service-call Send("R", "L", read);
The "Env" style functions are used to secure the service-environment (defined in MqEnvS)
and is required.. under special conditions... to proper answer the original service call at the
end of the service-processing.
By default jvmqmsgque guarantee the proper management of the environment on behalf of the user.
Under normal conditions the user don't need these functions.
The folllowing design-goals were defined:
come-in == come-out
The two design-goals from above are in conflict and the both functions MqEnvProtect and MqEnvRestore are used to solve this conflict.
Example from server.java
→ protect the environment and import from database
// PROTECT the original service-call EnvProtect(); // OVERWRITE the original service-call with data from the database dump.Import(server.this); MkBufferListC read = ReadALL(); // RESTORE the original service-call EnvRestore(); // ANSWER the original service-call Send("R", "L", read);
native void jvmqmsgque.MqContextC.EnvProtect | ( | ) |
Java:
→ C-API ctx.EnvProtect()
protect the service-environment
native void jvmqmsgque.MqContextC.EnvRestore | ( | ) |
Java:
→ C-API ctx.EnvRestore()
restore the service-environment
JNIEXPORT void JNICALL Java_jvmqmsgque_MqContextC_EnvProtect | ( | JNIEnv * | env, |
jobject | self ) |
Java:
→ C-API ctx.EnvProtect()
protect the service-environment
Definition at line 800 of file MqContextC_jv.c.
JNIEXPORT void JNICALL Java_jvmqmsgque_MqContextC_EnvRestore | ( | JNIEnv * | env, |
jobject | self ) |
Java:
→ C-API ctx.EnvRestore()
restore the service-environment
Definition at line 810 of file MqContextC_jv.c.