From: Goldsack, Patrick <patrick.goldsack@hp...> - 2005-08-30 08:14:47
You should RMIC everything which does not have the attribute "sfExport
false" otherwise you will have problems. If you set it to false you
accept two things: any reference to it remotely will fail, and the
remote management tool will mis-represent the component and not deal
with it correctly.
If you ever want remote access, ie "sfexport true" you will need the
stub/skeleton created, so in general we create the classes as part of
the build no matter what and then selectively decide in the description
whether we export or not.
We will bemoving to a model using dynamic proxies which will obviate the
need for the RMIC compiler, but right now this is needed.
[mailto:smartfrog-developer-admin@...] On Behalf Of
Sent: 26 August 2005 14:57
Subject: [Smartfrog-developer] question RMI
reading the SF Reference Manual Ch. 6.3.3 on RMI it is not clear to me
whether I should invoke "rmic" on newly developed component classes or
not. I understand that this is in general not necessary if the component
is not the first in the hierarchy (e.g. if it is deployed within some
compound). But I need the RMI endpoint if there is some LAZY reference
to the component. So for the distribution of some components, what would
be the best way to do it regarding RMI (and the fact that I don't want
every component to be a RMI server) ? Provide the stub/skeleton files in
the jar but set "sfExport false" per default in all the components ?
Thanks for clarifying this. =20
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Agile & Plan-Driven Development * Managing Projects & Teams * Testing &
Security * Process Improvement & Measurement *
Smartfrog-developer mailing list