Re: Why does sfTerminateWith only throwRemoteException?

The problem you will have is that there is no-one listening for that
exception... termination does not assume that it is being called from
"above" as this may have already been terminated or indeed may have
caused the termination by failing.  Indeed, we do not even need to have
the Remote exception as the method is never called remotely. It is a
known issue of the interface and is only there because this method was
included into the Prim interface which is remotable.
 
If you need to track problems with termination you will need to do this
some other way - reporting to some function in the system during
termination, for example, or adding another method to terminate VMs
which return exceptions to the caller and make this independant of the
component termination. Most system lifecycles we use are not necessarily
tightly bound to that of the components which implement it.
 
Patrick
 

________________________________

From: smartfrog-developer-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:smartfrog-developer-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of
Xavier Grehant
Sent: 20 June 2006 16:05
To: smartfrog-developer
Subject: [Smartfrog-developer] Why does sfTerminateWith only
throwRemoteException?


We want to have a correspondance between the lifecycle of our SmartFrog
component representing a Xen virtual machine, and the virtual machine
itself. So we put into sfTerminateWith the call to the script that
terminates the virtual machine, which throws a SmartFrog exception. But
sfTerminateWith cannot forward the SmartFrog exception because it only
throws RemoteException. Why? 

Thanks in advance,
Olivier and Xavier

_______________________________________________
Smartfrog-developer mailing list
Smartfrog-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/smartfrog-developer