CallbackProxy
, Carbon.EventHandlerProcPtr
, Ddeml.DdeCallback
, DispatchVTable.AddRefCallback
, DispatchVTable.GetIDsOfNamesCallback
, DispatchVTable.GetTypeInfoCallback
, DispatchVTable.GetTypeInfoCountCallback
, DispatchVTable.InvokeCallback
, DispatchVTable.QueryInterfaceCallback
, DispatchVTable.ReleaseCallback
, DLLCallback
, StdCallLibrary.StdCallCallback
, UnknownVTable.AddRefCallback
, UnknownVTable.QueryInterfaceCallback
, UnknownVTable.ReleaseCallback
, WinBase.EnumResNameProc
, WinBase.EnumResTypeProc
, WinBase.FE_EXPORT_FUNC
, WinBase.FE_IMPORT_FUNC
, WinBase.THREAD_START_ROUTINE
, WinNT.OVERLAPPED_COMPLETION_ROUTINE
, WinRas.RasDialFunc2
, Winsvc.Handler
, Winsvc.HandlerEx
, Winsvc.SERVICE_MAIN_FUNCTION
, WinUser.HOOKPROC
, WinUser.LowLevelKeyboardProc
, WinUser.MONITORENUMPROC
, WinUser.WindowProc
, WinUser.WinEventProc
, WinUser.WNDENUMPROC
, X11.XErrorHandler
DdemlUtil.DdeAdapter
public interface Callback
Object.finalize()
method. If native code attempts to call
a callback which has been GC'd, you will likely crash the VM. If
there is no method to deregister the callback (e.g. atexit
in the C library), you must ensure that you always keep a live reference
to the callback object.A callback should generally never throw an exception, since it doesn't necessarily have an encompassing Java environment to catch it. Any exceptions thrown will be passed to the default callback exception handler.
Modifier and Type | Interface | Description |
---|---|---|
static interface |
Callback.UncaughtExceptionHandler |
Modifier and Type | Field | Description |
---|---|---|
static List<String> |
FORBIDDEN_NAMES |
These method names may not be used for a callback method.
|
static String |
METHOD_NAME |
You must this method name if your callback interface has multiple
public methods.
|
static final String METHOD_NAME
FORBIDDEN_NAMES
.