Re: [Smartfrog-developer] Managing components deployed on several hosts

[Olivier P. <o.p...@gm...>]

On 7/19/06, Goldsack, Patrick <pat...@hp...> wrote:
[...]
> As for notification of attribute change - the way we implement that in
> our own applications is to overwrite the sfReplaceAttribute and/or
> sfAddAttribute method and hook our logic on there, or to poll the
> attributes on a regular basis, depending on what we want. Overwriting
> the method means that we can reject the  update if we want, whereas with
> a simple notification of change this would be too late.

I'm trying to implement that right now, and the Javadoc doesn't make
it very clear what you should do to reject an update. And the
exception thrown is a SmartFrogRuntimeException, not a
SmartFrogException, so I'm not too sure about just throwing an
instance of this.
How do you do that usually ? Do you have to allow modifications before
deployment, so that the Prim can be initialized ?

Cheers,
-- 
Olivier Pernet
Summer Student - CERN Openlab

We are the knights who say
echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq'|dc