The method you state is indeed the basic deploy method for smartfrog users
to use - the others (such as create child or create app) wrap up various
additional aspects such as driving the components through the remainder of
the lifecycle (sfDeploy() and sfStart()). Unless there is purpose in doing
so, we recommend using these "higher-level" methods - simpler and less error
It works by handing off to a local "deployer" - a class that decides where a
component should be created. In most cases (and certainly in yours unless
you have explicitly over-ridden it) this is an instance of
PrimProcessDeployer. This will decide exactly "on which host/in which
process" the component should be run, and hand off to an instance of a
deployer (via the process compound) in that process to handle the remainder
of the creation task.
Hope this helps,
----- Original Message -----
From: "rana dabbu" <ranabahadur@...>
Sent: Monday, May 02, 2005 5:49 AM
Subject: [Smartfrog-developer] transport method
Good Morning Everybody,
'sfDeployComponentDescription' in 'CompoundImpl.java' is stated to
be the basic smartfrog inner method to deploy any component. But it
doesn't seem to use any transportation function(s) to depoy the
component over the network.. Is there any other method which actually
does the task of deployment?
Since sfDeployComponentDeacription returns a Prim component, i doubt
for the existance of any other function that exports the component to
the remote machine..
As it was previously told that there are several deploy functions,
each being used at different scenarios, but there must be some primary
method that performs the actual exporting of the components..
Waiting For the reply,.
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r
Smartfrog-developer mailing list