smartfrog-support — Used for SmartFrog support questions

Re: [Smartfrog-support] Virtual Machines and SmartFrog

[Robinson, G. <gar...@sa...>]

Hi Julio,=20
=20
In VMWare Server, my vmnet host , VMNet8, has a gateway mask of
192.168.116.2, are you sure that i do not to change this if i want to
assign IPs on a different subnet, ie 192.168.182...?

Gary


________________________________

From: Guijarro, Julio [mailto:jul...@hp...]=20
Sent: 22 August 2007 09:51
To: Robinson, Gary; sma...@li...
Subject: RE: [Smartfrog-support] Virtual Machines and SmartFrog



Hi Gary,

=20

I don't know what guest os you are using but what you need to do is not
use DHCP and using the configuration tools for your OS, set networking
with the ip and and then reboot. In this way you will always be able to
locate the machines by name or ip.

=20

If you make sfdemohost 127.0.0.1 then when you copy this to all the
guest hosts none of them won't be able to locate back the server code in
your laptop because all of them will try to locate themselves.

=20

No, you don't need to disable your Ethernet adapter for this to work.

=20

You don't need to modify the gateway.=20

=20

Julio

=20

________________________________

From: Robinson, Gary [mailto:gar...@sa...]=20
Sent: 22 August 2007 09:36
To: Guijarro, Julio; sma...@li...
Subject: RE: [Smartfrog-support] Virtual Machines and SmartFrog

=20

Hi Julio,

=20

How do I set the ip/name in every vm os according to the table? Do i set
my adapter up for DHCP or how can i explicity set ip addresses? What
should my Gateway ip address be set as? As for "sfdemohost" should it
not just be my local address, ie 127.0.0.1? Do i need to disable my
physical ethernet adapter for this to work?

=20

Kind Regards,

=20

Gary

=20

________________________________

From: Guijarro, Julio [mailto:jul...@hp...]=20
Sent: 21 August 2007 18:17
To: Robinson, Gary; sma...@li...
Subject: RE: [Smartfrog-support] Virtual Machines and SmartFrog

Hi Gary,

=20

I don't have/use vmware server but I use vmware workstation and this is
what I do to make sure that the vms can locate each other:

=20

1. Configure VMWare

- Set up VMWare networking to use *only* the NAT/DHCP service (VMNet8)

  disable the other network services

=20

2. Configure windows/linux networking  (in host and vms)=20

=20

- Set ip/name in every vm os according to the table bellow.

=20

- Add the following to the Windows HOSTS file

(c:\windows\system32\drivers\etc\hosts)

- Add the following to the linux HOSTS file

(\etc\hosts)

=20

=20

Example:

192.168.182.1  sfdemohost

=20

192.168.182.100  sfdemo00

192.168.182.101  sfdemo01

192.168.182.102  sfdemo02

192.168.182.103  sfdemo03

192.168.182.104  sfdemo04

192.168.182.105  sfdemo05

192.168.182.106  sfdemo06

=20

=20

Once you have finished test with nslookup to see is all the machines can
reach the others.=20

=20

Then everything should work.

=20

Please, let me know if this works for you on VMWServer or if you need
more detailed instructions.

=20

Regards,

=20

Julio Guijarro

=20

=20

________________________________

From: sma...@li...
[mailto:sma...@li...] On Behalf Of
Robinson, Gary
Sent: 17 August 2007 14:57
To: sma...@li...
Subject: [Smartfrog-support] Virtual Machines and SmartFrog

=20

Hey guys,=20

I am using VMWare Server, and I am not allowed to use bridged networking
mode (for virtual machines) in my network. How can I set up VMWare
Server so that I can deploy component descriptions to a sfDaemon running
on a virtual machine, from a physical machine?

I have tried using NAT but when I try deployment it either fails, or
deploys to my physical machine (if its running sfDaemon).=20

Kind Regards,=20
Gary=20

Re: [Smartfrog-support] Virtual Machines and SmartFrog

[Guijarro, J. <jul...@hp...>]

Hi Gary,

=20

I don't know what guest os you are using but what you need to do is not
use DHCP and using the configuration tools for your OS, set networking
with the ip and and then reboot. In this way you will always be able to
locate the machines by name or ip.

=20

If you make sfdemohost 127.0.0.1 then when you copy this to all the
guest hosts none of them won't be able to locate back the server code in
your laptop because all of them will try to locate themselves.

=20

No, you don't need to disable your Ethernet adapter for this to work.

=20

You don't need to modify the gateway.=20

=20

Julio

=20

________________________________

From: Robinson, Gary [mailto:gar...@sa...]=20
Sent: 22 August 2007 09:36
To: Guijarro, Julio; sma...@li...
Subject: RE: [Smartfrog-support] Virtual Machines and SmartFrog

=20

Hi Julio,

=20

How do I set the ip/name in every vm os according to the table? Do i set
my adapter up for DHCP or how can i explicity set ip addresses? What
should my Gateway ip address be set as? As for "sfdemohost" should it
not just be my local address, ie 127.0.0.1? Do i need to disable my
physical ethernet adapter for this to work?

=20

Kind Regards,

=20

Gary

=20

________________________________

From: Guijarro, Julio [mailto:jul...@hp...]=20
Sent: 21 August 2007 18:17
To: Robinson, Gary; sma...@li...
Subject: RE: [Smartfrog-support] Virtual Machines and SmartFrog

Hi Gary,

=20

I don't have/use vmware server but I use vmware workstation and this is
what I do to make sure that the vms can locate each other:

=20

1. Configure VMWare

- Set up VMWare networking to use *only* the NAT/DHCP service (VMNet8)

  disable the other network services

=20

2. Configure windows/linux networking  (in host and vms)=20

=20

- Set ip/name in every vm os according to the table bellow.

=20

- Add the following to the Windows HOSTS file

(c:\windows\system32\drivers\etc\hosts)

- Add the following to the linux HOSTS file

(\etc\hosts)

=20

=20

Example:

192.168.182.1  sfdemohost

=20

192.168.182.100  sfdemo00

192.168.182.101  sfdemo01

192.168.182.102  sfdemo02

192.168.182.103  sfdemo03

192.168.182.104  sfdemo04

192.168.182.105  sfdemo05

192.168.182.106  sfdemo06

=20

=20

Once you have finished test with nslookup to see is all the machines can
reach the others.=20

=20

Then everything should work.

=20

Please, let me know if this works for you on VMWServer or if you need
more detailed instructions.

=20

Regards,

=20

Julio Guijarro

=20

=20

________________________________

From: sma...@li...
[mailto:sma...@li...] On Behalf Of
Robinson, Gary
Sent: 17 August 2007 14:57
To: sma...@li...
Subject: [Smartfrog-support] Virtual Machines and SmartFrog

=20

Hey guys,=20

I am using VMWare Server, and I am not allowed to use bridged networking
mode (for virtual machines) in my network. How can I set up VMWare
Server so that I can deploy component descriptions to a sfDaemon running
on a virtual machine, from a physical machine?

I have tried using NAT but when I try deployment it either fails, or
deploys to my physical machine (if its running sfDaemon).=20

Kind Regards,=20
Gary=20

Re: [Smartfrog-support] Virtual Machines and SmartFrog

[Guijarro, J. <jul...@hp...>]

Hi Gary,

=20

I don't have/use vmware server but I use vmware workstation and this is
what I do to make sure that the vms can locate each other:

=20

1. Configure VMWare

- Set up VMWare networking to use *only* the NAT/DHCP service (VMNet8)

  disable the other network services

=20

2. Configure windows/linux networking  (in host and vms)=20

=20

- Set ip/name in every vm os according to the table bellow.

=20

- Add the following to the Windows HOSTS file

(c:\windows\system32\drivers\etc\hosts)

- Add the following to the linux HOSTS file

(\etc\hosts)

=20

=20

Example:

192.168.182.1  sfdemohost

=20

192.168.182.100  sfdemo00

192.168.182.101  sfdemo01

192.168.182.102  sfdemo02

192.168.182.103  sfdemo03

192.168.182.104  sfdemo04

192.168.182.105  sfdemo05

192.168.182.106  sfdemo06

=20

=20

Once you have finished test with nslookup to see is all the machines can
reach the others.=20

=20

Then everything should work.

=20

Please, let me know if this works for you on VMWServer or if you need
more detailed instructions.

=20

Regards,

=20

Julio Guijarro

=20

=20

________________________________

From: sma...@li...
[mailto:sma...@li...] On Behalf Of
Robinson, Gary
Sent: 17 August 2007 14:57
To: sma...@li...
Subject: [Smartfrog-support] Virtual Machines and SmartFrog

=20

Hey guys,=20

I am using VMWare Server, and I am not allowed to use bridged networking
mode (for virtual machines) in my network. How can I set up VMWare
Server so that I can deploy component descriptions to a sfDaemon running
on a virtual machine, from a physical machine?

I have tried using NAT but when I try deployment it either fails, or
deploys to my physical machine (if its running sfDaemon).=20

Kind Regards,=20
Gary=20

Re: [Smartfrog-support] Specify port in command line?

[Guijarro, J. <jul...@hp...>]

Hi,

=20

At the moment there is no direct way in the shell scripts to select the
port number with sfStart or sfPing. But there are some solutions:

=20

1. set an environment variable with this attribute/value  "export
org.smartfrog.sfcore.processcompound.sfRootLocatorPort=3D3800"  Where =
you
will need to modify 3800 with your port of choice.

=20

2. Modify default.ini with a different port.

=20

3. Modify the scripts to do 1 using a special switch (ex -port)

=20

In any case, because we found that this could be useful we will provide
a permanent solution for this soon. To follow the progress of this
check:

=20

http://jira.smartfrog.org/jira/browse/SFOS-373

=20

Julio

=20

=20

=20

=20

________________________________

From: sma...@li...
[mailto:sma...@li...] On Behalf Of
Robinson, Gary
Sent: 20 August 2007 17:02
To: sma...@li...
Subject: [Smartfrog-support] Specifiy port in command line?

=20

Hey all,=20

How can I specifiy sfStart/sfPing to look for a daemon on a different
port to 3800? The normal notation ( ie  127.0.0.1:1111 ) throws out a
ParserException. Also, how can I get sfDaemon to run on a different
port?

My intention is to have ports forwarded to certain ip addresses for
different virtual machines. In reality the daemons should all be running
on 3800 on different virtual machines.

Kindest Regards=20
Gary=20

Re: [Smartfrog-support] Slow sfPing

[Guijarro, J. <jul...@hp...>]

Hi Gary,=20

=20

sfPing does not use the ICMP protocol. What sfPing does it to start a
daemon and to call the sfPing() method in a selected component (by
default it will do it in the remote daemon). My immediate guess is that
you are having some problems with your network configuration. RMI is
quite sensible to problems with DNS/DHCP. Have you tried to see if
"nslookup" between your machines works properly or if it takes a long
time?=20

=20

Julio

=20

________________________________

From: sma...@li...
[mailto:sma...@li...] On Behalf Of
Robinson, Gary
Sent: 21 August 2007 14:44
To: sma...@li...
Subject: [Smartfrog-support] Slow sfPing

=20

=20

Hey All,=20

When using sfPing to ping a daemon within my local network it takes
approx 1-2 mins to get a response, yet the reply is said to have only
taken <1 second. Any why this is so?

This is also the case with deployment. ICMP ping works properly.=20

Many thanks,
Gary=20

[Smartfrog-support] Slow sfPing

[Robinson, G. <gar...@sa...>]

Hey All,

When using sfPing to ping a daemon within my local network it takes
approx 1-2 mins to get a response, yet the reply is said to have only
taken <1 second. Any why this is so?
This is also the case with deployment. ICMP ping works properly.

Many thanks,=20
Gary

[Smartfrog-support] FW: start sfDaemon help

[Guijarro, J. <jul...@hp...>]

Hi Wayne,

=20

=20

The problem is that you don't have the net components jar file in your
daemon classpath.=20

=20

=20

That example uses #include for the ftp component using a notation to
load the description from a .jar file. In any case, you should get use
to put all your .sf and classes in jar files because it is mandatory to
be able to use security.

=20

Go to components/net and type "ant install". This command will compile
the components, create the needed jar files and then copy them to
$SFHOME/lib.

=20

Now you could start the daemon and everything should work.

=20

Julio

________________________________

From: Yuxiang Wu [mailto:wu...@dc...]=20
Sent: 20 August 2007 15:19
To: Guijarro, Julio
Subject: RE: start sfDaemon help

   When I run smartfrog net component ftpExample, it always displays
this error:

- FAILED when trying DEPLOY of 'TEST1',  [example.sf],  host:localhost
    Result:
      * Exception: 'SmartFrogDeploymentException: unnamed component.
deploying description 'example.sf' for 'TEST1'
        cause: SmartFrogResolutionException::
           Cause: Error creating parser for 'example.sf'. Parser error
[SmartFrogParseException::
org.smartfrog.sfcore.languages.sf.ParseException: Parsing include file
/org/smartfrog/services/trace/ftp.sf : Include file:
/org/smartfrog/services/trace/ftp.sf not found, cause:
org.smartfrog.sfcore.languages.sf.ParseException: Parsing include file
/org/smartfrog/services/trace/ftp.sf : Include file:
/org/smartfrog/services/trace/ftp.sf not found]
        deployedContext: included'


but actually, /org/smartfrog/services/trace/ftp.sf does exist. Also the
CLASSPATH is set to the current directory.=20

=20



Could you give me a hand? Thank you very much

Wayne

_----

From: Yuxiang Wu [mailto:wu...@dc... <mailto:wu...@dc...> ]
Sent: 14 August 2007 15:08
To: Guijarro, Julio
Subject: RE: start sfDaemon help



Hi Julio,



   That's OK. I think it is the CLASSPATH problem. Thank you for your
help.





Wayne

________________________________

From: Guijarro, Julio [mailto:jul...@hp...
<mailto:jul...@hp...> ]
Sent: 2007-8-13 15:35
To: sma...@li...; Yuxiang Wu
Subject: FW: start sfDaemon help

HI Wayne,



How did you intall SmarFrog? Are you using the an svn checkout, a full
distribution or an rpm distribution? What version are you using?



If you are running an RPM-based distribution, start with the RPMS. They
should also work on debian systems, though they don't set up the
environment properly there.



>From the information you provided, I think your problem could be that
SFHOME should be pointing to /usr/local/SmartFrog/dist, but without more
information I cannot be sure.



Regards,



Julio



________________________________

From: sit...@li...
[mailto:sit...@li...
<mailto:sit...@li...> ] On Behalf Of Yuxiang
Wu
Sent: 13 August 2007 12:36
To: sma...@li...
Subject: start sfDaemon help





Hi list,

   I just started to use SF. I start-up sfDaemon in Window successfully.
But when I run sfDaemon in Linux shell command line, there is a
Exception:

Exception in thread "main" java.lang.NoClassDefFoundError:
org/smartfrog/sfcore/logging/LogFactory
        at org.smartfrog.SFSystem.sfLog(Unknown Source)
        at org.smartfrog.SFSystem.initSystem(Unknown Source)
        at org.smartfrog.SFSystem.execute(Unknown Source)
        at org.smartfrog.SFSystem.main(Unknown Source)



My environment is:

$SFHOME=3D/usr/local/SmartFrog
$PATH=3D$SFHOME/bin
$CLASSPATH=3D.:$CLASSPATH

Could you tell me what is wrong? Thanks a lot


Wayne

[Smartfrog-support] Specifiy port in command line?

[Robinson, G. <gar...@sa...>]

Hey all,=20

How can I specifiy sfStart/sfPing to look for a daemon on a different
port to 3800? The normal notation ( ie  127.0.0.1:1111 ) throws out a
ParserException. Also, how can I get sfDaemon to run on a different
port?
My intention is to have ports forwarded to certain ip addresses for
different virtual machines. In reality the daemons should all be running
on 3800 on different virtual machines.

Kindest Regards
Gary

Re: [Smartfrog-support] Smartfrog - too much power?

[James A. <jam...@gm...>]

Sorry, first time on this list and caught out by the Reply-To header.
Keeping it on the list...

Hi Steve,

Thanks for the detailed response.

I definitely think that SmartFrog is the way to go for us, rather than
a bunch of shell scripts. I think it will scale better if the company
grows as we hope it will.

<snip/>

> Hello James
>
> Deploying WAR files and bringing up tomcat/jboss is a reasonable use for
> SmartFrog, especially if you have both test and production systems.
> Because you are going to end up run a lot deployment a lot of during
> that development process.
>
> Now, in theory, WAR files are self-contained packages that can be
> deployed simply by copying them to the app server. But that isnt true.
> There's the setting up of the app server -the GC options, the DNS-lookup
> timeout options, the need to get the JDBC drivers up in the classpath to
> the right place that JDBC doesnt throw class not found exceptions, and
> there is the late-binding configuration of the different servers. The
> JDBC URLs and passwords, the path to the network filestore, etc. There's
> the database itself, be it derby, mysql, mssql or oracle: it needs to be
> installed, set up with the tables, and permissions -and with the users
> and passwords that the WAR file is expecting. Its this app server setup
> and system configuration that is the pain in bringing up a new system.
>
> Right now most of this stuff is done with incomplete instructions -the
> bigger the project, the longer the instructions. This doesnt scale, and
> if something happens in the wrong order, you are in trouble, left with a
> system in an inconsistent state, having to roll back, or, if its a
> virtual machine, deleting the image and starting again. At least with VM
> images you can make one image and share it, but you then need to
> reconfigure the VMs with different JDBC urls, else whenever someone does
> a clean test they end up scrubbing the database. This is particularly
> likely with MSSQL by the way, as the DB is located using a flat
> namesserver across the entire organisation. Just because the production
> DB is in San Jose, doesnt mean that a test machine in Portland wont bind
> to the first database called "AppDB" in the company.

Been there, got the T-Shirt and the furrow in my head from scratching
it so much.

> My recommendation is learn the tool during those pauses in the long
> builds and test runs, and start using it for simple parts of the problem
> (deploy-by-copy, testing) to get happy with it before you go in to
> production with it, where you have to study the security bits of the
> documentation to see how to keep the operations team happy.

But I already have plans for those pauses!

http://xkcd.com/303/

I've got a week's holiday now with the SmartFrog docs for some light
reading (along with the Erlang book, Scala docs and some other fun
stuff). I'll see how I go.

Cheers,

James

Re: [Smartfrog-support] Virtual Machines and SmartFrog

[Steve L. <ste...@hp...>]

Robinson, Gary wrote:
> Hey guys,
> 
> I am using VMWare Server, and I am not allowed to use bridged networking 
> mode (for virtual machines) in my network. How can I set up VMWare 
> Server so that I can deploy component descriptions to a sfDaemon running 
> on a virtual machine, from a physical machine?
> 
> I have tried using NAT but when I try deployment it either fails, or 
> deploys to my physical machine (if its running sfDaemon).
> 
> Kind Regards,
> Gary**

Is there any way to reach the virtual machines from the physical ones?

One of the things we've been exploring is using XMPP messaging to send 
messages to running daemons which are only reachable by way of Jabber 
servers -if your VMs can connect through the NAT to your own jabber 
server, you would be able to deploy stuff by IM-ing it.

this is something we have two students building, part of the project you 
can find in the repository under core/extras/avalanche to have web based 
VM setup and configuration. It is not yet ready for production, but 
maybe there are some things we can work on.

Otherwise, there's something I've been thinking of for linux systems,
http://jira.smartfrog.org/jira/browse/SFOS-149
"Have the unix startup scripts or a component deploy every .sf file in a 
well known directory"

what I want is to have some component that polls a directory (on 
startup, or later), so you can deploy things by copying stuff to a 
directory (one per app), then, when you create/touch a single file, the 
component that polls the directory will deploy the app; when the deploy 
file is deleted/the whole directory unlinked, the deployment will go away.

This is something that could be used for deployment over the network 
mounted local filesystems that vmware gives you: have the default 
components poll some common directory you can use to deploy stuff on demand.

this is all ideaware right now; it is something I wanted to do for Linux 
integration, and now that we've cut the 3.12 release it is something I 
will have a go at in september. I am afraid that I have a couple of 
weeks break before I can start this.

-steve

Re: [Smartfrog-support] Smartfrog - too much power?

[Steve L. <ste...@hp...>]

James Abley wrote:
> Hi,
> 
> I'm currently evaluating smartfrog for use on our internal systems and
> I just wanted to confirm that it's a suitable tool for my purposes.
> 
> We are building WARs using Maven2 and Continuum. As part of the
> Continuum build, the War gets pushed out to our development server.
> 
> Once it has passed testing on this machine, we need to push it out to
> our clustered staging environment for more testing and then a similar
> step for deployment to our production environment.
> 
> The deployment is to Tomcat, so it involves undeploying the existing
> version, deploying the current version and then running a few tests
> (GET and POST / HttpUnit style things) on some resources to ensure
> that the application deployed properly.
> 
> My first question: is using smartfrog for this sort of problem
> overkill, or is this a common first usage that people start with
> before using more of the functionality?
> 

Hello James

Deploying WAR files and bringing up tomcat/jboss is a reasonable use for 
SmartFrog, especially if you have both test and production systems. 
Because you are going to end up run a lot deployment a lot of during 
that development process.

Now, in theory, WAR files are self-contained packages that can be 
deployed simply by copying them to the app server. But that isnt true. 
There's the setting up of the app server -the GC options, the DNS-lookup 
timeout options, the need to get the JDBC drivers up in the classpath to 
the right place that JDBC doesnt throw class not found exceptions, and 
there is the late-binding configuration of the different servers. The 
JDBC URLs and passwords, the path to the network filestore, etc. There's 
the database itself, be it derby, mysql, mssql or oracle: it needs to be 
installed, set up with the tables, and permissions -and with the users 
and passwords that the WAR file is expecting. Its this app server setup 
and system configuration that is the pain in bringing up a new system.

Right now most of this stuff is done with incomplete instructions -the 
bigger the project, the longer the instructions. This doesnt scale, and 
if something happens in the wrong order, you are in trouble, left with a 
system in an inconsistent state, having to roll back, or, if its a 
virtual machine, deleting the image and starting again. At least with VM 
images you can make one image and share it, but you then need to 
reconfigure the VMs with different JDBC urls, else whenever someone does 
a clean test they end up scrubbing the database. This is particularly 
likely with MSSQL by the way, as the DB is located using a flat 
namesserver across the entire organisation. Just because the production 
DB is in San Jose, doesnt mean that a test machine in Portland wont bind 
to the first database called "AppDB" in the company.

If you have automated deployment of your complete system you have
  -the ability to bring up your entire machine from scratch. This is 
worth doing if you plan to bring up a lot of real/virtual machines
  -the ability to install and bring up the application server to your 
settings
  -all of the configuration options under revision control
  -the ability to declare restart/retry policies: what to do if things 
fail.We have workflow components that can catch the failure of their 
children, and apply some action such as retry -to repeat the deployment.
  -you can try out deployments of different system configurations, which 
is very good for testing and performance.
  -you are now in a position to start thinking about dynamically 
allocated servers (like EC2), though this is just an option -it is not
   mandatory.
You also get to have machines doing the dull, repetitive work of getting 
everything deployed, and integrate that with functional testing. Our 
test components can deploy something, wait until a condition is met 
(such as a start page being served up), then run junit tests.



Are there any reasons for not using SmartFrog. I can think of a couple
  -your ship deadline is so tight that all you have is a week of 
firefighting chaos left. Its probably too late to go for SmartFrog at 
that time, but you will have lots of justification for the tool in your 
project post-mortem.

  -you dont want to invest the time learning another tool. That probably 
is the main barrier to using SmartFrog -or any other tool. Open source 
projects cost nothing to download, so there's nothing to stop you 
pulling down the latest release (3.12.000, incidentally). If you buy 
something you've just put money on the table -usually lots of it- so you 
may as well sit down and read the manuals it came with. For SmartFrog 
you have to print those manuals out if you want them on paper, and you 
dont have that initial investment of a few thousand dollars to justify 
the effort.

My recommendation is learn the tool during those pauses in the long 
builds and test runs, and start using it for simple parts of the problem 
(deploy-by-copy, testing) to get happy with it before you go in to 
production with it, where you have to study the security bits of the 
documentation to see how to keep the operations team happy.

The alternative is to look at my post-mortem of how we used to do live 
web services
  http://people.apache.org/~stevel/slides/when_web_services_go_bad.pdf
  http://www.hpl.hp.com/techreports/2002/HPL-2002-274.pdf
and check off every disaster as they happen to you. Because they will, 
if you are not careful.

-Steve

[Smartfrog-support] Virtual Machines and SmartFrog

[Robinson, G. <gar...@sa...>]

Hey guys,

I am using VMWare Server, and I am not allowed to use bridged networking
mode (for virtual machines) in my network. How can I set up VMWare
Server so that I can deploy component descriptions to a sfDaemon running
on a virtual machine, from a physical machine?

I have tried using NAT but when I try deployment it either fails, or
deploys to my physical machine (if its running sfDaemon).=20

Kind Regards,=20
Gary

[Smartfrog-support] Smartfrog - too much power?

[James A. <jam...@gm...>]

Hi,

I'm currently evaluating smartfrog for use on our internal systems and
I just wanted to confirm that it's a suitable tool for my purposes.

We are building WARs using Maven2 and Continuum. As part of the
Continuum build, the War gets pushed out to our development server.

Once it has passed testing on this machine, we need to push it out to
our clustered staging environment for more testing and then a similar
step for deployment to our production environment.

The deployment is to Tomcat, so it involves undeploying the existing
version, deploying the current version and then running a few tests
(GET and POST / HttpUnit style things) on some resources to ensure
that the application deployed properly.

My first question: is using smartfrog for this sort of problem
overkill, or is this a common first usage that people start with
before using more of the functionality?

Cheers,

James

[Smartfrog-support] Announcing SmartFrog 3.12.000 stable release

[Steve L. <ste...@hp...>]

Hello everyone.

I am pleased to announce that we have what we consider to be a stable
SmartFrog release, numbered 3.12.000.

What we are shipping this week is just last week's beta release with
some bug fixes on sideline components.

1. Improvements to the www liveness components -things you deploy to keep
an eye on local/remote web pages, components that report failure when
the web page they are monitoring goes away. They fail, an action you can
catch in a container with some other workflow (e.g rollback and retry
your deployment).

2. Feature creep in the XMPP componentry. Now a single Xmpplistener
supports an unlimited number of handlers, each of which can get
forwarded messages that they are interested in. There aren't many built
in handlers; one to log messages, and another to relay messages to a
list of other recipients. I plan to do full jabberbot functionality
though; regexps for sender and message matching, and custom actions when
a message is received, so you can build a sequence of handlers for
different IM messages. For testing all of this we use talk.google.com
incidentally; someone else's infrastructure is always easier to
maintain.

3. We've also flipped the Java1.5+ only switch. There's no change in the
code, and I think you could get away with rebuilding the core for
Java1.4. Its just we aren't going to support it if you do. Its not just
the cost of testing, its the fact that the concurrency model in Java1.4
is wrong. There are no guarantees about the ordering of volatile data
access, so the JVMs can reorder them, leading to bad, bad things
happening. If you stay in synchronized blocks this doesn't matter, but
you cannot use RMI and stay synchronized; there's too much risk of
re-entrant calls on different threads.

Please grab the release from SourceForge, under
http://sourceforge.net/project/showfiles.php?group_id=87384&package_id=108447

I recommend the .JAR distribution for developers (it now includes the 
whole source tree), and the RPMs for people planning on production 
deployment on Linux systems.

-steve


SmartFrog 3.12.000
======================

This is a new release of SmartFrog, the Java-based, LPGL-licensed
distributed deployment framework developed by HP Laboratories. SmartFrog
enables applications to be deployed across multiple machines,
configuring different aspects of the system so that they are all
consistently configured, and managing the life-cycle of the application
as a whole. The project's home page is http://smartfrog.org/

The release artifacts are available at

http://sourceforge.net/project/showfiles.php?group_id=87384&package_id=108447

This release is 3.12.000; built from revision 5030
of the SVN repository. This release has an extended language
with the ability to tag attributes, and includes the following items:

* Core smartfrog daemon, including services to manage files, start and stop
   Java and native programs.
* Example components and applications.
* Ant support: ant tasks to deploy and terminate applications from a build.
* Ant components: the ability to execute ant tasks in a deployment.
* Anubis: a partition aware tuple-space that can be used to implement fault
   tolerant systems.
* Database: components to issue database commands, and deploy HSLDB and 
MySQL.
* JMX: the ability to configure and manage JMX components, and to manage
   SmartFrog components over JMX.
* Logging: integration with Apache commons-logging and Log4J
* Networking: email, FTP, SSH, DNS support.
* Quartz: scheduled operations using Quartz libraries.
* Scripting: support for BSF-hosted scripting languages
* Testing: Distributed JUnit and component testing with SFUnit.
* WWW: deployment of WAR and EAR files to application servers. 
deploy-by-copy
   is provided for all application servers that support it, and sample 
templates
   are provided to start and stop Tomcat and JBoss. The Jetty component can
   configure and deploy individual servlets, eliminating much of the 
need for WAR
   files and application servers.
* XML: XML support with XOM.
* XMPP: Presence and messaging over Jabber.

Packaging
=========

This release is available as:

* RPM files inside a .tar.gz file.
* a JAR installer.
* the original core smartfrog distribution as .zip and .tar.gz (deprecated)


The RPM installation is for RPM-based Linux systems. It comprises the 
RPM files:

smartfrog:        the core SmartFrog distribution.
smartfrog-daemon: the shell scripts to add the smartfrog distribution to the
                   path, and to run the daemon on start-up.
smartfrog-demo:   example code and documentation.

smartfrog-anubis: "Anubis" partition-aware tuple space.
smartfrog-logging: Enhanced logging


We recommend the RPM files for installation on deployment hosts, and the 
izpack
installation for developers.


All the JAR files are also published to a repository that is compatible with
Apache Maven and Ivy. Add http://smartfrog.sourceforge.net/repository/
to your repository list to pull SmartFrog artifacts into your Ivy- or
Maven- based build.

There are also SmartFrog components to retrieve artifacts from such a 
repository
(the Library components under /org/smartfrog/services/os/java/library.sf ),
which can be used for dynamic download of SmartFrog and other artifacts.


Security warning
================

Unless SmartFrog is configured with security, a running daemon will
listen on its configured port for incoming deployment requests, and
deploy the applications with the rights of the user running the daemon.
When the smartfrog-daemon RPM is installed, that means that a process
running as root will be listening on an open port for incoming
deployment requests. Do not deploy SmartFrog this way on any untrusted
network, not without turning security on and, ideally, recreating the
RPMs with signed JAR files.

Building SmartFrog
==================

SmartFrog requires Java 1.5 and Ant 1.7 to build. The izpack and source 
.zip and
.tar.gz distributions include a source tree adequate to build the
entire system. To build a later release, please follow the instructions at
   http://sourceforge.net/svn/?group_id=87384
to check out smartfrog/trunk/core from our repository.

This release was built with revision 5030 of the repository, which
is available under the SVN branch
https://smartfrog.svn.sourceforge.net/svnroot/smartfrog/tags/release3.12.000

We strongly encourage anyone interested in building or extending
SmartFrog to get involved in the SmartFrog developer mailing list, which
can be found from the sourceforge project page
http://sourceforge.net/projects/smartfrog/

Reporting Bugs
==============

Please file all bug reports at http://jira.smartfrog.org/

Thank you!

The SmartFrog Team        http://smartfrog.org/

Changes since last release
==========================

The 3.12.000 release is a stable release, intended for use in production
systems. All major defects that have been reported have been fixed, and
the RPM and izpack distribution packages are working well as
distribution formats.

This release is Java1.5+ only; it has been tested on Java1.5 and
Java1.6, on Linux, Windows XP, Windows Vista and OS/X systems; the
tested Linux distributions are RHEL4, RHEL5 and Ubuntu 7.04; one of the
RedHat servers is a 4-way 64-bit machine.

Very few changes have been made since the last beta, 3.11.007; apart
from the switch to Java 1.5, the only changes were to the TestCompound
(and tests that use it), and the components in the sf-www package that
test for a remote page being available.

** Bug
     * [SFOS-390] - TestCompound NPEs
     * [SFOS-393] - www waitforpage component doesnt fail abnormally 
when there is a timeout
     * [SFOS-394] - www liveness and waitfor pages uses seconds and not 
milliseconds for sleeps
                    -inconsistent with rest of the system
     * [SFOS-395] - www liveness page tries to read the error text from 
the far end after an
                    - IO exception
     * [SFOS-396] - TestCompoundImpl thinks an expected abnormal 
termination is still a failure

** Improvement
     * [SFOS-133] - stop Cruise Control javadocs from complaining about 
various things in some components
     * [SFOS-317] - Move test cases to the asynchronous event model
     * [SFOS-388] - Move to Java1.5 across the entire project
     * [SFOS-400] - include buildable source trees in the distributions

** Sub-task
     * [SFOS-372] - migrate 
org.smartfrog.services.database.test.system.core.mysql.MysqlTest to 
async tests



-----------------------
Hewlett-Packard Limited
Registered Office: Cain Road, Bracknell, Berks RG12 1HN
Registered No: 690597 England

Re: [Smartfrog-support] sfStart and program arguments

[Guijarro, J. <jul...@hp...>]

Hi Gary,

No problem, we will try to help you. It is the same with every new
system; it takes a while to get used to it.=20

I don't know exactly your use case but SmartFrog is all about
configuration and therefore what I would do is to put these parameters
as SmartFrog configuration attributes that the component then reads and
sets as system properties.

Ex.=20

sfConfig extends MyComponent {
  javaPropertyFile "...file url";

}

Then in the component you can read that information and set the
java.policy.property.

Void readAttriutes() {
  String javaPropFile =3D "defaultValue";
  // true =3D mandatory
  javaPropertiesFile =3D sfResolve ("javaPropertyFile", javaPropFile,
true);
  System.setProperty("java.security.policy", javaPropertiesFile);
 =20
}


Something like this would work. What you cannot do is to set any -D type
of parameters but if that is what you need then you could use
SubProcesses to do that. But I don't want to confuse you with too much
information unless you need it.


Regards,

Julio


> -----Original Message-----
> From: Robinson, Gary [mailto:gar...@sa...]
> Sent: 16 August 2007 15:32
> To: Guijarro, Julio
> Subject: RE: [Smartfrog-support] sfStart and program arguments
>=20
> Hi Julio,
>=20
> Thanks for your prompt reply. As you may have guessed I am quite new
to
> the SmartFrog framework and any help is greatly appreciated. How would
I
> create a component to pass these parameters onto another daemon? Do
you
> have any examples?
>=20
> Kind Regards,
> Gary
>=20
> -----Original Message-----
> From: Guijarro, Julio [mailto:jul...@hp...]
> Sent: 16 August 2007 15:02
> To: Robinson, Gary; sma...@li...
> Subject: RE: [Smartfrog-support] sfStart and program arguments
>=20
> Hi Gary,
>=20
> Welcome to the list.
>=20
> What I get from your question is that you are trying to pass some java
> properties to a program that is deployed using sfStart. If my
> understanding is correct then what you need to do is to have a daemon
> that either was started with those parameters included on the command
> line or you will need your component to use something like system
> properties to get those parameters to your other program.
>=20
> sfStart is used to parse a description and verify that everything is
> correct and then to pass that description to the daemon. Then, the
> daemon is the one that deploys the components that will load your
> application.
>=20
> To start a daemon with special parameters you can use -J . For
example:
> rem JVMARGS are declared using -J token
> rem e.g. -J "-Djava.library.path=3D/libs -Xmx400M"
> rem e.g. -J "-Djava.library.path=3D/libs" -J -Xmx400M
>=20
> If you use SmartFrog with security on you will find that SmartFrog
uses
> the Java Security Manager and also needs a java security policy file.
> This file is set in the script setSFSecurityProperties. For both to
work
> together, you should merge all the security policies in one file. If
you
> only need that policy file because or RMI, and you don't care about
its
> restrictions, then you could enable the "all permitted" policy file
that
> we have for dynamic classloading with no security by just removing the
> comment (#) in
>=20
> # export SFDYNAMICCLASSLOADING_ON=3DENABLED
>=20
> I haven't tried it but to hard code a security policy in a java
program
> you could try this:
>=20
> String myFile=3D"....";
> System.setProperty("java.security.policy",myFile);
> System.setSecurityManager(new SecurityManager());
>=20
>=20
> Julio
>=20
> > -----Original Message-----
> > From: sma...@li...
> [mailto:smartfrog-
> > sup...@li...] On Behalf Of Robinson, Gary
> > Sent: 16 August 2007 11:29
> > To: sma...@li...
> > Subject: [Smartfrog-support] sfStart and program arguments
> >
> > Hi all, hopefully someone here can help me.
> >
> > Is there a way to pass Java program arguments into the sfStart
> command?
> >
> > I have deployed a description that loads a Java RMI server
> application.
> > And
> > for the the server application to work it needs to bind itself with
an
> > RMI
> > registry and therefore needs to have a java security policy file
> > associated
> > with it passed in as an argument.
> >
> > Also, does anyone have any information about how i can hard code a
> java
> > secuirty policy into a Java program?
> >
> > Many thanks,
> > Gary
> >
> >
>
------------------------------------------------------------------------
> -
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a
> browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > _______________________________________________
> > Smartfrog-support mailing list
> > Sma...@li...
> > https://lists.sourceforge.net/lists/listinfo/smartfrog-support

Re: [Smartfrog-support] sfStart and program arguments

[Guijarro, J. <jul...@hp...>]

Hi Gary,

Welcome to the list.

What I get from your question is that you are trying to pass some java
properties to a program that is deployed using sfStart. If my
understanding is correct then what you need to do is to have a daemon
that either was started with those parameters included on the command
line or you will need your component to use something like system
properties to get those parameters to your other program.

sfStart is used to parse a description and verify that everything is
correct and then to pass that description to the daemon. Then, the
daemon is the one that deploys the components that will load your
application.

To start a daemon with special parameters you can use -J . For example:
rem JVMARGS are declared using -J token=20
rem e.g. -J "-Djava.library.path=3D/libs -Xmx400M"
rem e.g. -J "-Djava.library.path=3D/libs" -J -Xmx400M

If you use SmartFrog with security on you will find that SmartFrog uses
the Java Security Manager and also needs a java security policy file.
This file is set in the script setSFSecurityProperties. For both to work
together, you should merge all the security policies in one file. If you
only need that policy file because or RMI, and you don't care about its
restrictions, then you could enable the "all permitted" policy file that
we have for dynamic classloading with no security by just removing the
comment (#) in

# export SFDYNAMICCLASSLOADING_ON=3DENABLED

I haven't tried it but to hard code a security policy in a java program
you could try this:

String myFile=3D"....";
System.setProperty("java.security.policy",myFile);
System.setSecurityManager(new SecurityManager());


Julio

> -----Original Message-----
> From: sma...@li...
[mailto:smartfrog-
> sup...@li...] On Behalf Of Robinson, Gary
> Sent: 16 August 2007 11:29
> To: sma...@li...
> Subject: [Smartfrog-support] sfStart and program arguments
>=20
> Hi all, hopefully someone here can help me.
>=20
> Is there a way to pass Java program arguments into the sfStart
command?
>=20
> I have deployed a description that loads a Java RMI server
application.
> And
> for the the server application to work it needs to bind itself with an
> RMI
> registry and therefore needs to have a java security policy file
> associated
> with it passed in as an argument.
>=20
> Also, does anyone have any information about how i can hard code a
java
> secuirty policy into a Java program?
>=20
> Many thanks,
> Gary
>=20
>
------------------------------------------------------------------------
-
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a
browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Smartfrog-support mailing list
> Sma...@li...
> https://lists.sourceforge.net/lists/listinfo/smartfrog-support

[Smartfrog-support] sfStart and program arguments

[Robinson, G. <gar...@sa...>]

Hi all, hopefully someone here can help me.=20

Is there a way to pass Java program arguments into the sfStart command?

I have deployed a description that loads a Java RMI server application.
And
for the the server application to work it needs to bind itself with an
RMI
registry and therefore needs to have a java security policy file
associated
with it passed in as an argument.

Also, does anyone have any information about how i can hard code a java
secuirty policy into a Java program?

Many thanks,
Gary=20

[Smartfrog-support] FW: start sfDaemon help

[Guijarro, J. <jul...@hp...>]

HI Wayne,=20

=20

How did you intall SmarFrog? Are you using the an svn checkout, a full
distribution or an rpm distribution? What version are you using?

=20

If you are running an RPM-based distribution, start with the RPMS. They
should also work on debian systems, though they don't set up the
environment properly there.

=20

>From the information you provided, I think your problem could be that
SFHOME should be pointing to /usr/local/SmartFrog/dist, but without more
information I cannot be sure.

=20

Regards,=20

=20

Julio

=20

________________________________

From: sit...@li...
[mailto:sit...@li...] On Behalf Of Yuxiang Wu
Sent: 13 August 2007 12:36
To: sma...@li...
Subject: start sfDaemon help

=20

=20

Hi list,

   I just started to use SF. I start-up sfDaemon in Window successfully.
But when I run sfDaemon in Linux shell command line, there is a
Exception:

Exception in thread "main" java.lang.NoClassDefFoundError:
org/smartfrog/sfcore/logging/LogFactory
        at org.smartfrog.SFSystem.sfLog(Unknown Source)
        at org.smartfrog.SFSystem.initSystem(Unknown Source)
        at org.smartfrog.SFSystem.execute(Unknown Source)
        at org.smartfrog.SFSystem.main(Unknown Source)



My environment is:

$SFHOME=3D/usr/local/SmartFrog
$PATH=3D$SFHOME/bin
$CLASSPATH=3D.:$CLASSPATH

Could you tell me what is wrong? Thanks a lot


Wayne

[Smartfrog-support] Announcing SmartFrog 3.11.007beta

[Steve L. <ste...@hp...>]

SmartFrog 3.11.007beta
======================

This is a new release of SmartFrog, the Java-based, LPGL-licensed
distributed deployment framework developed by HP Laboratories. SmartFrog
enables applications to be deployed across multiple machines,
configuring different aspects of the system so that they are all
consistently configured, and managing the life-cycle of the application
as a whole. The project's home page is http://smartfrog.org/

The release artifacts are available at

https://sourceforge.net/project/showfiles.php?group_id=87384&package_id=176308&release_id=531293

This release is 3.11.007beta; built from revision 4969
of the SVN repository. This release has an extended language
with the ability to tag attributes, and includes the following items:

* Core smartfrog daemon, including services to manage files, start and stop
   Java and native programs.
* Example components and applications.
* Ant support: ant tasks to deploy and terminate applications from a build.
* Ant components: the ability to execute ant tasks in a deployment.
* Anubis: a partition aware tuple-space that can be used to implement fault
   tolerant systems.
* JMX: the ability to configure and manage JMX components, and to manage
   SmartFrog components over JMX.
* Logging: integration with Apache commons-logging and Log4J
* Networking: email, FTP, SSH, DNS support.
* Quartz: scheduled operations using Quartz libraries.
* Scripting: support for BSF-hosted scripting languages
* WWW: deployment of WAR and EAR files to application servers. 
deploy-by-copy
   is provided for all application servers that support, and a 
tomcat-specific
   component can communicate with Apache Tomcat. The Jetty component can
   configure and deploy individual servlets, eliminating much of the 
need for WAR
   files themselves.

For Java 1.5 systems, there are some extra components:
* Database: components to issue database commands, and deploy HSLDB and 
MySQL.
* Testing: Distributed JUnit and component testing with SFUnit.
* XML: XML support with XOM.
* XMPP: Presence and messaging over Jabber.

This release is the last ever release that will support Java1.4. We have
long built and tested on both Java 5 and Java 6; Java 5 has a better
concurrency model while Java 6 has fixed some long-standing RMI
problems. After this release, the team will make use of Java 5 language
features and classes in the Java 1.5 runtime, which will prevent it from
building or running on Java 1.4 systems.


Packaging
=========

This release is available as:

* RPM files inside a .tar.gz file.
* a JAR installer.
* the original core smartfrog distribution as .zip and .tar.gz (deprecated)


The RPM installation is for RPM-based Linux systems. It comprises three RPM
files, smartfrog, smartfrog-daemon and smartfrog-demo:

smartfrog:        the core SmartFrog distribution.
smartfrog-daemon: the shell scripts to add the smartfrog distribution to the
                   path, and to run the daemon on start-up.
smartfrog-demo:   example code and documentation.

All the JAR files are also published to a repository that is compatible with
Apache Maven and Ivy. Add http://smartfrog.sourceforge.net/repository/
to your repository list to pull SmartFrog artifacts into your Ivy- or
Maven- based build.

There are also SmartFrog components to retrieve artifacts from such a 
repository
(the Library components under /org/smartfrog/services/os/java/library.sf ),
which can be used for dynamic download of SmartFrog and other artifacts.


Security warning
================

Unless SmartFrog is configured with security, a running daemon will
listen on its configured port for incoming deployment requests, and
deploy the applications with the rights of the user running the daemon.
When the smartfrog-daemon RPM is installed, that means that a process
running as root will be listening on an open port for incoming
deployment requests. Do not deploy SmartFrog this way on any untrusted
network, not without turning security on and, ideally, recreating the
RPMs with signed JAR files.

Building SmartFrog
==================

SmartFrog requires Java 1.4 and Ant 1.7 to build. For a complete release,
Java1.5 or later is required.


The distribution does not include a source tree adequate to build the
entire system. Please follow the instructions at
   http://sourceforge.net/svn/?group_id=87384
and check out smartfrog/trunk/core from our repository.

This release was built with revision 4969 of the repository, which
is available under the SVN branch
https://smartfrog.svn.sourceforge.net/svnroot/smartfrog/tags/release3.11.007beta

We strongly encourage anyone interested in building or extending
smartfrog to get involved in the smartfrog developer mailing list, which
can be found from the sourceforge project page
http://sourceforge.net/projects/smartfrog/

Reporting Bugs
==============

Please file all bug reports at http://jira.smartfrog.org/

Thank you!

The SmartFrog Team        http://smartfrog.org/

Changes since last release
==========================

Since the 3.11.005beta, there have been changes to some of the
components. In particular, the www component now has a tomcat deployment
descriptor that can deploy Apache Tomcat5.5,

   /org/smartfrog/services/www/servers/tomcat5.sf

This is accompanied by one for JBoss 4.0:

   /org/smartfrog/services/www/servers/jboss4.sf

These deployment descriptors are passing our tests of deploy-by-copy
deployment of a test WAR.

The language has been enhanced with the OPTIONAL keyword, which allows
one to define a value to use if the remote reference does not resolve.
To use an example from the jboss tests, here is a binding of jboss.port
either to the property test.jboss.port (in the process parsing the .sf
file, not the destination daemon), and falling back to the value 8080 if
it does not resolve:

   jboss.port OPTIONAL(8080) PROPERTY test.jboss.port;

Consult the reference documentation for more details on this.

** Bug
     * [SFOS-146] - jetty tests failing (disabled)
     * [SFOS-195] - tcn18 is failing (skipped)
     * [SFOS-269] - email setting are not passed to the bootstrap templates
     * [SFOS-282] - TestCompound doesnt report all failing children as 
an error
     * [SFOS-339] - TestCompound doesnt handle failures in startup properly
     * [SFOS-348] - avalanche clean fails in a bulk ivy-clean
     * [SFOS-349] - NPE thown in SmartFrogException when using StringAll
                    and Cause is null.
     * [SFOS-352] - TestCompound doesnt set the status or application status
                    when something fails during startup
     * [SFOS-363] - NPE in test Compound -maybe when tests are skipped?
     * [SFOS-365] - Error on line 377 of release/build.xml on Windows
     * [SFOS-366] - test runner interpets skipped as a junit failure
     * [SFOS-369] - if RunShell/RunJava is set to start late 
(startEarly=false),
                    then reading all other attributes should be delayed
                    until this time.
     * [SFOS-380] - marshalling problem in mysql tests
     * [SFOS-381] - Async test reporting needs to handle unexported 
components
                    raising lifecycle events

** Improvement
     * [SFOS-345] - stop uploading individual RPM files to sourceforge
     * [SFOS-362] - rename Value condition to BooleanValue
     * [SFOS-367] - add description attribute to testblock/testcompound
                    and pass it back through test results
     * [SFOS-379] - support empty [] lists when flattening runjava 
property lists

** New Feature
     * [SFOS-329] - add templates for JBoss and Tomcat

** Sub-task
     * [SFOS-229] - document OPTIONAL
     * [SFOS-322] - migrate 
org.smartfrog.test.system.workflow.delay.DelayTest
                    to async tests
     * [SFOS-323] - migrate 
org.smartfrog.test.system.workflow.retry.RetryTest
                    to async tests

Re: [Smartfrog-support] tomcat.sf

[Bill de h. <bi...@de...>]

Steve Loughran wrote:
> Bill de hOra wrote:
>> Hi,
>>
>> is there a Tomcat .sf file I could look at? I've seen references to a 
>> TomcatServer, but not the actual configuration itself.
>>
>> I'm asking because I'm just getting to grips with SmartFrog and I'm 
>> assuming that something akin to the JettyServer needs to be written 
>> (ie thre'll be a bit more to it that stopping and starting catalina.sh).
>>
>> cheers
>> Bill
>>
> 
> SF 3.11.005 beta has a prototype template for tomcat 5.5 in the www 
> component, sharing a base design with the jboss template that I've used 
> before. In the absence of any functional tests, I would not assume that 
> it works. I'll do the tests this week as we can use it in 
> extras/avalanche for hosting the front end under tomcat.

Cool. I should get to try this out during the week.

cheers
Bill

Re: [Smartfrog-support] tomcat.sf

[Steve L. <ste...@hp...>]

Bill de hOra wrote:
> Hi,
> 
> is there a Tomcat .sf file I could look at? I've seen references to a 
> TomcatServer, but not the actual configuration itself.
> 
> I'm asking because I'm just getting to grips with SmartFrog and I'm 
> assuming that something akin to the JettyServer needs to be written (ie 
> thre'll be a bit more to it that stopping and starting catalina.sh).
> 
> cheers
> Bill
> 

SF 3.11.005 beta has a prototype template for tomcat 5.5 in the www 
component, sharing a base design with the jboss template that I've used 
before. In the absence of any functional tests, I would not assume that 
it works. I'll do the tests this week as we can use it in 
extras/avalanche for hosting the front end under tomcat.

-steve

[Smartfrog-support] announcing SmartFrog 3.11.005 beta

[Steve L. <ste...@hp...>]

It seems like only last week that I was making a new release. Wait a 
minute, it was :)

This is a new iteration with improved RPM termination and some of the 
components included as RPMs. If you are installing SmartFrog via RPMs, 
this update is very important. For other users, the main changes have 
been test related, which have had less effect to the core libraries, 
except in the TestCompound component.

As usual, please file defects on http://jira.smartfrog.org/ , send 
emails to the smartfrog-developer list. We plan for another release in 
two-three weeks time, depending on the feature set.

-Steve

Attached: the JIRA issue log as HTML links.

SmartFrog 3.11.005beta
======================

This is a new release of SmartFrog, the Java-based, LPGL-licensed 
distributed
deployment framework developed by HP Laboratories. SmartFrog enables
applications to be deployed across multiple machines, configuring different
aspects of the system so that they are all consistently configured, and 
managing
the life-cycle of the application as a whole. The project's home page is
http://smartfrog.org/

The release artifacts are available at

http://sourceforge.net/project/showfiles.php?group_id=87384&package_id=176308

This release is 3.11.005beta; built from revision 4827
of the SVN repository. This release has an extended language
with the ability to tag attributes, and includes the following items:

* Core SmartFrog daemon, including services to manage files, start and stop
   Java and native programs.
* Example components and applications.
* Ant support: ant tasks to deploy and terminate applications from a build.
* Ant components: the ability to execute ant tasks in a deployment.
* Anubis: a partition aware tuple-space that can be used to implement fault
   tolerant systems.
* JMX: the ability to configure and manage JMX components, and to manage
   SmartFrog components over JMX.
* Logging: integration with Apache commons-logging and Log4J
* Networking: email, FTP, SSH, DNS support.
* Quartz: scheduled operations using Quartz libraries.
* Scripting: support for BSF-hosted scripting languages
* WWW: deployment of WAR and EAR files to application servers. 
deploy-by-copy
   is provided for all application servers that support, and a 
tomcat-specific
   component can communicate with Apache Tomcat. The Jetty component can
   configure and deploy individual servlets, eliminating much of the 
need for WAR
   files themselves.

For Java 1.5 systems, there are some extra components:
* Database: components to issue database commands, and deploy HSLDB and 
MySQL.
* Testing: Distributed JUnit and component testing with SFUnit.
* XML: XML support with XOM.
* XMPP: Presence and messaging over Jabber.

Packaging
=========

This release is available as:

* RPM files inside a .tar.gz file.
* a JAR installer.
* the original core smartfrog distribution as .zip and .tar.gz (deprecated)


The RPM installation is for RPM-based Linux systems. It comprises three RPM
files, smartfrog, smartfrog-daemon and smartfrog-demo:

smartfrog:        the core SmartFrog distribution.
smartfrog-daemon: the shell scripts to add the smartfrog distribution to the
                   path, and to run the daemon on start-up.
smartfrog-demo:   example code and documentation.

All the JAR files are also published to a repository that is compatible with
Apache Maven and Ivy. Add http://smartfrog.sourceforge.net/repository/
to your repository list to pull SmartFrog artifacts into your Ivy- or 
Maven- based build.

There are also SmartFrog components to retrieve artifacts from such a 
repository
(the Library components under /org/smartfrog/services/os/java/library.sf ),
which can be used for dynamic download of SmartFrog and other artifacts.


Security warning
================

Unless SmartFrog is configured with security, a running daemon
will listen on its configured port for incoming deployment requests, and 
deploy
the applications with the rights of the user running the daemon. When the
smartfrog-daemon RPM is installed, that means that a process running as root
will be listening on an open port for incoming deployment requests. Do not
deploy SmartFrog this way on any untrusted network, not without turning 
security
on and, ideally, recreating the RPMs with signed JAR files.

Building SmartFrog
==================

SmartFrog requires Java 1.4 and Ant 1.7 to build. For a complete release,
Java1.5 or later is required.


The distribution does not include a source tree adequate to build the entire
system. Please follow the instructions at
   http://sourceforge.net/svn/?group_id=87384
and check out smartfrog/trunk/core from our repository.

This release was built with revision 4827 of the repository, which
is available under the SVN branch
https://smartfrog.svn.sourceforge.net/svnroot/smartfrog/tags/release3.11.005beta

We strongly encourage anyone interested in building or extending 
smartfrog to
get involved in the smartfrog developer mailing list, which can be found 
from
the sourceforge project page http://sourceforge.net/projects/smartfrog/

Reporting Bugs
==============

Please file all bug reports at http://jira.smartfrog.org/

Thank you!

The SmartFrog Team        http://smartfrog.org/

Changes since last release
==========================

Since the release 3.11.003beta, the primary changes have been in RPM
packaging and distribution.

* The smartfrog-install JAR is the cross-platform installer JAR,
   recommended for all systems except where RPM installation is desired.

* There are now RPM packages for Anubis and logging services (the latter
   includes Apache Log4J and commons-logging)

* Uninstalling smartfrog-daemon RPM shuts down the /etc/init.d/smartfrogd
   daemon

* Uninstalling smartfrog RPM triggers an attempt to shut down any
   running SmartFrog process

Removing component JARs, such as smartfrog-anubis or smartfrog-logging
does not shut down SmartFrog; this is still something being considered.
Please test and report on any problems with RPM install/uninstall, as
this is an area we are actively trying to stabilise. All RPMs are tested
by installing and removing them from an RHEL5 system, as part of the
build process; behaviour on other RPM-based distributions is still
something we are interested in.

There have been improvements in how tests are run, but these do not
involve significant changes to the core other than in test-related
components.


** Bug
     * [SFOS-48]  - TestCompound, when set up to terminate gracefully
                    (sfShouldTerminate=true) terminates abnormally if
                    the actions threw an exception, even if they were
                    expected
     * [SFOS-272] - Anubis Ping Heartbeat protocol not setting bits in 
heartbeats
     * [SFOS-308] - smartfrog rpm should shut down sfDaemon in %preun pahse
     * [SFOS-310] - the new installer JAR is  not uploading
     * [SFOS-316] - daemon rpm doesnt stop the daemon; raises an error
     * [SFOS-333] - TestCompound should retain termination record text
                    when converting from an abnormal to a normal termination
     * [SFOS-337] - ConditionalTest is failing
     * [SFOS-338] - SequenceTest is failing
     * [SFOS-340] - error when uninstalling the daemons
     * [SFOS-341] - org.smartfrog.test.system.functions.FunctionsSystemTest
                    failing in cruise control: race condition?
     * [SFOS-343] - rpms aren't deleted in a remote-upload
     * [SFOS-344] - redistributables are logging at debug


** Improvement
     * [SFOS-237] - Automate creation of PDF files from .sxw templates
     * [SFOS-311] - Automate upload of maven artifacts
     * [SFOS-315] - add an IsPropertySet condition to look for a system 
property
     * [SFOS-327] - allow <sf-parse> task to take a parsertargets.txt file
                    containing the target list
     * [SFOS-328] - Improve bulk loading of parsertargets
     * [SFOS-334] - make testblock deployable out the box
     * [SFOS-342] - Move TextFile output logic to FileSystem

** New Feature
     * [SFOS-330] - add a links directory with unversioned symlinks to 
the JARs


** Task
     * [SFOS-275] - Copy up new maven artifacts to sourceforge
     * [SFOS-277] - Automate creation of template release annoucement
     * [SFOS-313] - move OptionSet parsing from a switch on characters
                    to string comparision
     * [SFOS-314] - add a -quietexit option to SfSystem
     * [SFOS-331] - add anubis RPM

** Sub-task
     * [SFOS-318] - make 
org.smartfrog.test.system.workflow.conditional.ConditionalTest
                    async

[Smartfrog-support] smartfrog 3.11.003 beta artifacts in a maven2-style repository

[Steve L. <ste...@hp...>]

Also, the SmartFrog Jars are all being published to a maven2-style 
repository:

http://smartfrog.sourceforge.net/repository/

Add this to your list of repositories in Ivy or maven2 to pull things in.

-steve

-----------------------
Hewlett-Packard Limited
Registered Office: Cain Road, Bracknell, Berks RG12 1HN
Registered No: 690597 England

[Smartfrog-support] New release: SmartFrog 3.11.003beta

[Steve L. <ste...@hp...>]

I am pleased to release announcement of a new smartfrog release; I've 
attached the change log as HTML for an easy way to get to the jira 
issues in question.

1. The documentation isn't right yet; we now have OpenOffice generating 
PDFs straight from .sxw files, PDFs that look very nice indeed. I am 
tempted to give up on Forrest and just include all the PDFs.

2. I'm still getting the packing and distribution down. If things are 
missing, or the RPMs misbehaving, let me know.

-steve

SmartFrog 3.11.003beta
======================

This is a new release of SmartFrog, the Java-based, LPGL-licensed 
distributed
deployment framework developed by HP Laboratories. SmartFrog enables
applications to be deployed across multiple machines, configuring different
aspects of the system so that they are all consistently configured, and 
managing
the life-cycle of the application as a whole. The project's home page is
http://smartfrog.org/

The release artifacts are available at

http://sourceforge.net/project/showfiles.php?group_id=87384&package_id=176308

This release is 3.11.003beta; built from revision 4764
of the SVN repository. This release has an extended language
with the ability to tag attributes, and includes the following items:

* Core smartfrog daemon, including services to manage files, start and stop
   Java and native programs.
* Example components and applications.
* Ant support: ant tasks to deploy and terminate applications from a build.
* Ant components: the ability to execute ant tasks in a deployment.
* Anubis: a partition aware tuple-space that can be used to implement fault
   tolerant systems.
* JMX: the ability to configure and manage JMX components, and to manage
   SmartFrog components over JMX.
* Logging: integration with Apache commons-logging and Log4J
* Networking: email, FTP, SSH, DNS support.
* Quartz: scheduled operations using Quartz libraries.
* Scripting: support for BSF-hosted scripting languages
* WWW: deployment of WAR and EAR files to application servers. 
deploy-by-copy
   is provided for all application servers that support, and a 
tomcat-specific
   component can communicate with Apache Tomcat. The Jetty component can
   configure and deploy individual servlets, eliminating much of the 
need for WAR
   files themselves.

For Java 1.5 systems, there are some extra components:
* Database: components to issue database commands, and deploy HSLDB and 
MySQL.
* Testing: Distributed JUnit and component testing with SFUnit.
* XML: XML support with XOM.
* XMPP: Presence and messaging over Jabber.

Packaging
=========

This release is available as:

* RPM files inside a .tar.gz file.
* a JAR installer.
* the original core smartfrog distribution as .zip and .tar.gz (deprecated)


The RPM installation is for RPM-based Linux systems. It comprises three RPM
files, smartfrog, smartfrog-daemon and smartfrog-demo:

smartfrog:        the core SmartFrog distribution.
smartfrog-daemon: the shell scripts to add the smartfrog distribution to the
                   path, and to run the daemon on start-up.
smartfrog-demo:   example code and documentation.

All the JAR files are also published to a repository that is compatible with
Apache Maven and Ivy. Add http://smartfrog.sourceforge.net/repository/
to your repository list to pull SmartFrog artifacts into your Ivy- or 
Maven- based build.

There are also SmartFrog components to retrieve artifacts from such a 
repository
(the Library components under /org/smartfrog/services/os/java/library.sf ),
which can be used for dynamic download of SmartFrog and other artifacts.


Security warning
================

Unless SmartFrog is configured with security, a running daemon
will listen on its configured port for incoming deployment requests, and 
deploy
the applications with the rights of the user running the daemon. When the
smartfrog-daemon RPM is installed, that means that a process running as root
will be listening on an open port for incoming deployment requests. Do not
deploy SmartFrog this way on any untrusted network, not without turning 
security
on and, ideally, recreating the RPMs with signed JAR files.

Building SmartFrog
==================

SmartFrog requires Java 1.4 and Ant 1.7 to build. For a complete release,
Java1.5 or later is required.


The distribution does not include a source tree adequate to build the entire
system. Please follow the instructions at
   http://sourceforge.net/svn/?group_id=87384
and check out smartfrog/trunk/core from our repository.

This release was built with revision 4764 of the repository, which
is available under the SVN branch
https://smartfrog.svn.sourceforge.net/svnroot/smartfrog/tags/release3.11.003beta

We strongly encourage anyone interested in building or extending 
smartfrog to
get involved in the smartfrog developer mailing list, which can be found 
from
the sourceforge project page http://sourceforge.net/projects/smartfrog/

Reporting Bugs
==============

Please file all bug reports at http://jira.smartfrog.org/

Thank you!

The SmartFrog Team        http://smartfrog.org/

Changes since last release
==========================

** Bug
     * [SFOS-91] - Abnormal TerminationRecords dont deserialize unless 
the far end can load every exception in the exception chain
     * [SFOS-101] - database and junit/xunit builds dont create source 
or documentation artifacts
     * [SFOS-147] - LogToLog4JImpl implements Seralizable, but it isnt
     * [SFOS-272] - Anubis Ping Heartbeat protocol not setting bits in 
heartbeats
     * [SFOS-280] - xunit and junit components don't run their published 
target when core/ant runs published
     * [SFOS-289] - avalanche ivy resolve too slow
     * [SFOS-290] - autoloader handles a missing file by throwing an NPE
     * [SFOS-291] - daemon rpm should shut down smartfrog before 
uninstalling
     * [SFOS-297] - callbacks make the daemon lock up under the testharness
     * [SFOS-303] - Asynchronous logging creating too many threads
     * [SFOS-304] - smartfrogd status option is broken


** Improvement
     * [SFOS-207] - Is there a way to automate .sxw to .pdf?
     * [SFOS-270] - Improve logging of deploy times.
     * [SFOS-281] - change Tags manipulation methods to throw 
SmartFrogRuntimeException
     * [SFOS-283] - remove Teardown logic from TestCompound
     * [SFOS-292] - Revert tag manipulation methods in component 
descriptions back to throwing SmartFrogContextException - related to 
SFOS-281
     * [SFOS-307] - Clean up documentation

** New Feature
     * [SFOS-232] - Add new History component for testing sequences of 
operations
     * [SFOS-271] - Add a way to deploy but not start a component


** Task
     * [SFOS-279] - Move JUnit invocation of SF deployments to callback 
notifications
     * [SFOS-288] - code review autoloader class/.sf; add test case

** Sub-task
     * [SFOS-212] - Build Avalanche under Ivy
     * [SFOS-219] - Get the source of sfinstall
     * [SFOS-278] - Replace direct access of TerminationRecord.cause 
with get/set
     * [SFOS-284] - add missing dependency jars of Avalanche to SCM 
repository
     * [SFOS-285] - Fix setup.xml to work with ivy





-- 
-----------------------
Hewlett-Packard Limited
Registered Office: Cain Road, Bracknell, Berks RG12 1HN
Registered No: 690597 England

[Smartfrog-support] Announcing SmartFrog 3.11.001beta

[Steve L. <ste...@hp...>]

Hello everyone! I am pleased to announce the release of 3.11.001beta. 
Most of the changes in the last three weeks are related to RPM 
packaging, along with some recent bug fixes.

I've attached the change log as an HTML file, in which all the links 
point to the relevant JIRA issues.

Everyone using SmartFrog outside a live production environment should 
upgrade and report any problems as soon as they can; we're planning on 
the next release cycle taking two weeks.

-Steve

SmartFrog 3.11.001beta
======================

This is a new release of SmartFrog, the Java-based, LPGL-licensed 
distributed
deployment framework developed by HP Laboratories. SmartFrog enables
applications to be deployed across multiple machines, configuring different
aspects of the system so that they are all consistently configured, and 
managing
the life-cycle of the application as a whole. The project's home page is
http://smartfrog.org/

The release artifacts are available at

http://sourceforge.net/project/showfiles.php?group_id=87384&package_id=176308&release_id=521363

This release is 3.11.001beta; built on Java 1.5 from revision 4586
of the SVN repository. This release has an extended language
with the ability to tag attributes, and includes the following items:

* Core smartfrog daemon, including services to manage files, start and stop
   Java and native programs.
* Example components and applications.
* Ant support: ant tasks to deploy and terminate applications from a build.
* Ant components: the ability to execute ant tasks in a deployment.
* Anubis: a partition aware tuple-space that can be used to implement fault
   tolerant systems.
* JMX: the ability to configure and manage JMX components, and to manage
   SmartFrog components over JMX.
* Logging: integration with Apache commons-logging and Log4J
* Networking: email, FTP, SSH, DNS support.
* Quartz: scheduled operations using Quartz libraries.
* Scripting: support for BSF-hosted scripting languages
* WWW: deployment of WAR and EAR files to application servers. 
deploy-by-copy
   is provided for all application servers that support, and a 
tomcat-specific
   component can communicate with Apache Tomcat. The Jetty component can
   configure and deploy individual servlets, eliminating much of the 
need for WAR
   files themselves.

For Java 1.5 systems, there are some extra components:
* Database: components to issue database commands, and deploy HSLDB and 
MySQL.
* Testing: Distributed JUnit and component testing with SFUnit.
* XML: XML support with XOM.
* XMPP: Presence and messaging over Jabber.

This is a beta release; before the final release we plan to integrate
Forrest-generated documentation into the redistributables, and tune the
redistributable packages themselves.

Packaging
=========

This release represents a beta test of the new packaging/distribution 
options.

It is available as:

* RPM files inside a .tar.gz file.
* a JAR installer.
* the original core smartfrog distribution as .zip and .tar.gz (deprecated)


The RPM installation is for RPM-based Linux systems. It comprises three RPM
files, smartfrog, smartfrog-daemon and smartfrog-demo:

smartfrog:        the core SmartFrog distribution.
smartfrog-daemon: the shell scripts to add the smartfrog distribution to the
                   path, and to run the daemon on start-up.
smartfrog-demo:   example code and documentation.

All the JAR files are also published to a repository that is compatible with
Apache Maven and Ivy. Add
   http://smartfrog.sourceforge.net/repository/
to your repository list to pull SmartFrog artifacts into your Ivy- or 
Maven- based build.

There are also SmartFrog components to retrieve artifacts from such a 
repository
(the Library components under /org/smartfrog/services/os/java/library.sf ),
which can be used for dynamic download of SmartFrog and other artifacts.

List of files and their SHA1 checksums

2a9427a769c519e830f11ce456bc176bcfe6a56e 
smartfrog-3.11.001beta-4.noarch.rpm
3690e69bee17e9d4d3ad7784b15a4c418b35d0c0  smartfrog.3.11.001beta_all.tar.gz
bac8be019eb6d8c5c1b60fa2ad17ec7702bb9dcc  smartfrog.3.11.001beta_all.zip
5aa2c612a620e37871ef68e3693f3d3ba02dc148  smartfrog.3.11.001beta_dist.tar.gz
380f12c826cd8276da158212f2f4a657dd7815f4  smartfrog.3.11.001beta_dist.zip
a086e10c866feb357def39ab21d50d43a8b7bf55 
smartfrog-daemon-3.11.001beta-4.noarch.rpm
8e81f01ba4db76e9ce1c077743164555222f5327 
smartfrog-demo-3.11.001beta-4.noarch.rpm
73c1c58000c9cadbe9e95f652c45f10e344980d9  smartfrog-install-3.11.001beta.jar


Security warning
================

Unless SmartFrog is configured with security, a running daemon
will listen on its configured port for incoming deployment requests, and 
deploy
the applications with the rights of the user running the daemon. When the
smartfrog-daemon RPM is installed, that means that a process running as root
will be listening on an open port for incoming deployment requests. Do not
deploy SmartFrog this way on any untrusted network, not without turning 
security
on and, ideally, recreating the RPMs with signed JAR files.

Building SmartFrog
==================

SmartFrog requires Java 1.4 and Ant 1.7 to build. For a complete release,
Java1.5 or later is required.

None of our distributions include a source tree adequate to build the 
entire
system. Please follow the instructions at
   http://sourceforge.net/svn/?group_id=87384
and check out smartfrog/trunk/core from our repository.

This release was built with revision 4586 of the repository,
https://smartfrog.svn.sourceforge.net/svnroot/smartfrog/tags/3.11.001beta

We strongly encourage anyone interested in building or extending 
smartfrog to
get involved in the smartfrog developer mailing list, which can be found 
from
the sourceforge project page http://sourceforge.net/projects/smartfrog/

Reporting Bugs
==============

Please file all bug reports at http://jira.smartfrog.org/

Changes since last release
==========================

Since the last release, 3.11.000beta, the primary changes have been in
* RPM support: RPMs are now working, according to our automated tests.
* Headless support: there is a -headless option that runs SmartFrog 
without a visible GUI.
* Security

Thank you!

The SmartFrog Team        http://smartfrog.org/

Release Notes - SmartFrog - Version 3.11.001 beta

** Bug
     * [SFOS-112] - Java classpath components
     * [SFOS-161] - core/release build fails on macs and other unix 
systems without rpmbuild on the path
     * [SFOS-162] - 'classic' distribution JARs include old tasks and 
gui JARs, with no coherence
     * [SFOS-163] - scripting redistribution does not include beanshell
     * [SFOS-166] - core smartfrog jars do not md5 their pom.
     * [SFOS-167] - Ant builds run out of memory on windows
     * [SFOS-168] - ivy file excludes beanshell, so scripting component 
is incomplete
     * [SFOS-169] - mysql test problem
     * [SFOS-172] - we arent running all the tests in testharness
     * [SFOS-173] - unable to start SmartFrog as a non-root user
     * [SFOS-174] - RPM installed daemons should not log to a file when 
not started from init.d
     * [SFOS-179] - syntax defects in smartfrog profile
     * [SFOS-180] - SmartFrog installation has warnings
     * [SFOS-185] - scripting component distribution doesnt include 
beanshell library
     * [SFOS-188] - database tests failing on windows
     * [SFOS-190] - ConfigurationDescriptorDeployTest/testurlTest01 is 
failing when there is no default.sf deployment
     * [SFOS-193] - sfGui.bat missing from all .zip release file. 
3.11.000beta
     * [SFOS-198] - org.smartfrog.test.system.deploy.OutputImpl doesnt 
pass sfDeploy up
     * [SFOS-199] - SFGui.bat missing from all.bat
     * [SFOS-200] - init-proxy targets not that useful
     * [SFOS-218] - Ant build fails with unknown option 
'+HeapDumpOnOutOfMemoryError'
     * [SFOS-221] - incorrect unix shells/filenames for smartfrog.sh and 
smartfrog.csh
     * [SFOS-222] - Useless code in 
org.smartfrog.avalanche.client.sf.rpm.RPMUtils
     * [SFOS-223] - /tmp/sflogs is created with default user perms by 
the first user to run smartfrog; if root, nobody else can run smartfrog
     * [SFOS-224] - headless mode isnt working
     * [SFOS-231] - sfManagementConsole prints out too many tag related 
error messages
     * [SFOS-236] - Adding a java.policy file when using no security in 
SF, causes an infinite loop in SF: 
org.smartfrog.sfcore.security.DummySecurityManager
     * [SFOS-260] - SFComponentDescriptionImpl prints exceptions it 
swallows to system.out, when it isnt needed


** Improvement
     * [SFOS-181] - add assertions to test for instanceof in 
SmartFrogTestBase
     * [SFOS-191] - testharness code should use commons-logging to log 
stuff, rather than do it themselves
     * [SFOS-203] - move components in debug build's output from 
system.out to sfLog()
     * [SFOS-214] - make the default option for every build "component"
     * [SFOS-225] - rename smartfrog in the init.d directory
     * [SFOS-248] - sfDumpState in CompoundImpl uses a new thread for 
each visit. It should only do that when visiting a remote object.
     * [SFOS-259] - ScriptPrimImpl relies on NPEs to distinguish source 
from resource paths

** New Feature
     * [SFOS-208] - Add an option to sfDaemon to run headless.
     * [SFOS-247] - Create Dumper object to dump descriptions from an 
already deployed application, using the sfDumpState interface in Prim


** Task
     * [SFOS-42] - Have Ivy set up the classpath for most components
     * [SFOS-226] - Create automated tests for RPM working
     * [SFOS-255] - clean up imports of services

** Sub-task
     * [SFOS-194] - Modify documentation to include information to add 
ANT_OPTS=-XX:MaxPermSize=64m.
     * [SFOS-213] - Get build file to build on everyone's machines
     * [SFOS-216] - Update avalanche to build against SVN_HEAD of the 
sfinstaller
     * [SFOS-233] - layout RPM in FSH-compatible structure
     * [SFOS-241] - move startup scripts (except the daemon) to the main 
smartfrog rpm
     * [SFOS-243] - add sfgui as separate installable in izpack installer
     * [SFOS-245] - pull sfgui from core/smartfrog packaging


-- 
-----------------------
Hewlett-Packard Limited
Registered Office: Cain Road, Bracknell, Berks RG12 1HN
Registered No: 690597 England