RE: [Smartfrog-developer] difference sfStart & sfRun

[Julio G. <ju...@us...>]

Hi Andrea,=20



- sfStart is intended to deploy a description into a running daemon. =
This daemon can be either local or remote.



- sfRun is similar to sfDaemon except that the daemon created ins not a =
root daemon. This means that  it does not start the RMI registry and =
therefore is only used to deploy applications localy or that do not =
requiere requiere other systems to locate them.





The parametes for sfRun are:

- c SFREF: to deploy a description with a random name

-n name SREF: to deploy a description named name.



I have noticed that thes sfRun batch files in cvs don't allow the use of =
-n option and this needs to be fixed.



I you want the daemon to terminate once all the applications terminate =
you could add "-e" to your sfRun command line.



Note that the batch scripts for sfRun don't automatically deploy =
sfDefault.sf.



About the wrong error message that you get, this message is caused by a =
bug in CompoundImpl, to be precise in the method =
sfDeployComponentDescription(). You would also get the same wrong error =
message if you try to use sfStart to deploy a component without class in =
a remote sfDaemon.



This bug was fixed in CVS four weeks ago and therefore you should get =
the right error message when using the next release.



If want to fix it in you distribution you can replacle  =
org/smartfrog/sfcore/compound/compoundImpl.java with the latest file =
form CVS.



Thanks your message. This is a very complex system to test and any help =
is welcomed.



Regards,=20

                Julio Guijarro



> -----Original Message-----

> From: sma...@li... =
[mailto:smartfrog-

> dev...@li...] On Behalf Of Andreas =
Unterkircher

> Sent: 27 February 2004 12:57

> To: sma...@li...

> Subject: [Smartfrog-developer] difference sfStart & sfRun

>=20

>=20

> Hello,

>=20

> I wonder what is the difference between sfStart and sfRun... To be =
more

> specific, here is a small test component with a reference to a non

> existing class:

>=20

> #include "org/smartfrog/components.sf";

>=20

> tester extends {

>  sfClass "foo.bar";

> }

> sfConfig extends Compound {

>  foo extends tester;

> }

>=20

> If I start this with "sfRun" I get:

>=20

> Error during deployment of URL:eventTest.sf, for component: null

> SmartFrogDeploymentException: unnamed component

>    cause: java.lang.NullPointerException

>=20

> If I start this (after having started the SF daemon) with "sfStart" I =
get

>=20

> Error during deployment of URL:eventTest.sf, for component: test

> SmartFrogDeploymentException: HOST oplabox03.cern.ch:rootProcess:test

> failed to deploy 'foo' component

>    cause: java.lang.ClassNotFoundException: forName: Cannot find =
foo.bar

>    reference: sfClass

>    deployedContext: included

>=20

> I was wondering about the different error messages. Especially if you =
try

> to debug components resp. .sf files the error message produced by =
sfRun

> does not give such a clear hint to the problem as the one provided by

> sfStart. Thanks for any comments !

>=20

> Best regards,

> Andreas

>=20

>=20

> --

> http://cern.ch/openlab

>=20

>=20