|
From: Leif M. <le...@ta...> - 2003-06-19 05:56:54
|
Belo,
You are absolutely correct. The Java process was not correctly
receiving
the CTRL-C signals when running under the Wrapper. I had known about
this for quite a while, but it had never been a problem so I put it out
of my
mind :-/ Sorry about that.
Your mail prompted me to dig into in and I got it fixed. Rereading the
MS C++ docs on the related APIs, it still looks like it should have been
working as it was.... Excuses, excuses.
Anyway, this is fixed in CVS and will be in the next release.
What is it that you are trying to do. The Wrapper was correctly
shutting
down the JVM when CTRL-C was pressed. The only problem was that
the WrapperListener.controlEvent method was not being called within
the JVM.
Cheers,
Leif
Voigt, Bela M. wrote:
>Hi there!
>
>I'm using the wrapper to exceute some java class, that has public void
>controlEvent(int event) implemented.
>I started the wrapper in a shell (cmd.exe).
>My problem is, that the function is never reached when I press CTRL-C. When
>I close the shell by clicking on the "x", log the user off or shutdown the
>computer
>everything works as expected.
>In the WrapperManager class a native windows function for the windows event
>is called. If the native function returns some non-zero value the
>controlEvent function in my class gets called.
>For CTRL-C there's a zero return value, so nothing happens.Am I doing
>something wrong or ist the native function messing up?
>
>Wrapper version 2.8.2 & 3.0.3 behave the same.
>I'm using windows 2000 and jdk1.4.1.
>
>TIA
>Belo
>
>
|