Deprecated API

Deprecated Methods

mandala.rami.InvocationObserver.getCalleeThread()

The usability of the callee thread depends on the asynchronous policy used by the AsynchronousReference implementation. For example, if a thread-pool is used, the callee thread returned may be running a completely different method than the one called. Hence, callee thread use is error prone. No replacement. Current implementations always return null. This method will be removed in the next light release.

mandala.jacob.remote.RemoteExceptionInfo.getThrowable()
As of Mandala 2.3, replaced by RemoteExceptionInfo.getTransportException()

mandala.rami.InvocationObserver.isCalleeAvailable()

The usability of the callee thread depends on the asynchronous policy used by the AsynchronousReference implementation. For example, if a thread-pool is used, the callee thread returned may be running a completely different method than the one called. Hence, callee thread use is error prone. No replacement. Current implementations always return null. This method will be removed in the next light release.

mandala.rami.ResultUpdater.setCalleeThread(ThreadOp)

The usability of the callee thread depends on the asynchronous policy used by the AsynchronousReference implementation. For example, if a thread-pool is used, the callee thread returned may be running a completely different method than the one called. Hence, callee thread use is error prone. No replacement. Current implementations always give null. This method will be removed in the next light release.

mandala.rami.InvocationEventsWaiter.waitForCalleeThread()

The usability of the callee thread depends on the asynchronous policy used by the AsynchronousReference implementation. For example, if a thread-pool is used, the callee thread returned may be running a completely different method than the one called. Hence, callee thread use is error prone. No replacement. Current implementations return null immediatly. This method will be removed in the next light release.

mandala.rami.InvocationEventsWaiter.waitForCalleeThread(long)

The usability of the callee thread depends on the asynchronous policy used by the AsynchronousReference implementation. For example, if a thread-pool is used, the callee thread returned may be running a completely different method than the one called. Hence, callee thread use is error prone. No replacement. Current implementations return null immediatly. This method will be removed in the next light release.

mandala.rami.InvocationEventsWaiter.waitUntilCalleeAvailable()

The usability of the callee thread depends on the asynchronous policy used by the AsynchronousReference implementation. For example, if a thread-pool is used, the callee thread returned may be running a completely different method than the one called. Hence, callee thread use is error prone. No replacement. Current implementations return immediatly. This method will be removed in the next light release.

mandala.rami.InvocationEventsWaiter.waitUntilCalleeAvailable(long)

The usability of the callee thread depends on the asynchronous policy used by the AsynchronousReference implementation. For example, if a thread-pool is used, the callee thread returned may be running a completely different method than the one called. Hence, callee thread use is error prone. No replacement. Current implementations return false immediatly. This method will be removed in the next light release.