smartfrog-developer — Development list

[Smartfrog-developer] 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

[Smartfrog-developer] 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-developer] 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-developer] 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-developer] Minor modification to tags interfaces in sfCore

[Murray, P. (HP L. Bristol) <pm...@hp...>]

The tags interfaces in sfCore have been changed to throw
SmartFrogRuntimeException instead of SmartFrogContextException. The
former is a super type of the latter. This is not in the latest release.

Paul.

Paul Murray
Hewlett-Packard Laboratories, Bristol
phone: +44 117 3129309=20

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

The contents of this message and any attachments to it are confidential
and may be legally privileged. If you have received this message in
error, you should delete it from your system immediately and advise the
sender.

To any recipient of this message within HP, unless otherwise stated you
should consider this message and attachments as "HP CONFIDENTIAL".

[Smartfrog-developer] instability in testharness for a couple of days

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

I'm making changes in the testharness, testblock and testcompound 
classes; expect some turbulence there. We wont get cruise control 
complaints as it is down and I couldnt get it restarted -when Geoff 
comes back next week he should have better luck.

This is what I am doing: http://jira.smartfrog.org/jira/browse/SFOS-267

-modifying the test containers to send lifecycle and test status 
notifications to any registered listener, and extending the testharness 
to allow it to wait for the results. This should remove some of the 
brittleness to timings in the workflow system, and let us run more 
complex test sequences.

-steve

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

[Smartfrog-developer] warning: SVN access via http://svn.sourceforge.net/ has gone away

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

Subversion have updated their status today  ( 
http://sourceforge.net/docman/display_doc.php?docid=2352&group_id=1#1184001090 
) and announced that you can no longer access any SVN repository 
directly from svn.sourceforge.net; you have to use the project specific 
hostname.

If you cannot update or check in code, it means you are still using the 
old URL, and not https://smartfrog.svn.sourceforge.net/svnroot/smartfrog

Here is the information on accessing sourceforge SVN
	http://sourceforge.net/svn/?group_id=87384

1. yes, you do need to check everything out. svn switch doesn't let you 
change hostnames
2. I've attached a build file that can copy IDEA project files from one 
svn repository tree to another. you can use this to pull over old 
project files once the checkout is complete

-steve

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

Re: [Smartfrog-developer] headless operation

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

>=20
> > It
> > would be nice if there was a command line option (and SmartFrog
> > component) which would deploy all *.sf files in some directory (eg.
> > /etc/smartfrog/init.d). I am thinking of writing such component
myself,
> > but I don't know when I will get to it. Until then I would go with
> > init.sf which creates root compound and default.sf which deploys in
it
> > by default.
> >
>=20
> That's an idea I had last month and filed away as a possible future
todo
> item:
> http://jira.smartfrog.org/jira/browse/SFOS-149
>=20
> Have the unix startup scripts or a component deploy every .sf file in
a
> well known directory.
>=20
> There's some security complications there: do you want to keep
> everything secured in a JAR, or can you get away with everything in
> plain text .sf files. Personally, I like the plain text option, and
> would certainly like to see something like this too; something that
> would poll the dir for changes and undeploy when the file(s) go away,
> deploy when they arrive. It would let you do deploy-by-copy deployment
> of smartfrog systems.
>=20
> -steve
>

The main problem with such a component are the security implications but
it could be very helpful for quick testing.

As an alternative, if you want to deploy several description when the
daemon starts, you can use the -f option to load a file with a list of
descriptions (described using ConfigurationDescriptor format for the
command line, check smartfrog -? or the manuals) that need to be
deployed.

Also, but only if you want you default description to be loaded in every
daemon and in every subprocess, there is no limit in the number of
"default" descriptions that can be loaded. Our daemon scripts only load
one because that is what we need but you could add as many as you want.=20

-Dorg.smartfrog.sfcore.processcompound.sfDefault.sfDefault=3D"%SFHOME%\bi=
n
\default.sf"

If you want your own description to be loaded using "myName" as name you
only need to add:
-Dorg.smartfrog.sfcore.processcompound.sfDefault.myName=3DmyDesc.sf

To add this with the normal scripts you can add to your normal command
line:
sfDaemon=20
-J "-Dorg.smartfrog.sfcore.processcompound.sfDefault.myName=3DmyDesc.sf"

Aleksander thanks for input.

Julio

> -----Original Message-----
> From: sma...@li...
[mailto:smartfrog-
> dev...@li...] On Behalf Of Steve Loughran
> Sent: 09 July 2007 12:04
> Cc: sma...@li...
> Subject: Re: [Smartfrog-developer] headless operation
>=20
> Aleksander Bandelj wrote:
> > I like 4). SmartFrog would then start with /etc/smartfrog/init.sf.
>=20
> For the latest release we've just gone to -headless (which
> init.d/smartfrogd sets), so that you can
> (a) test without trying to unset things
> (b) not break on a mac which is Unix-without-X11.
>=20
> We've also fixed the management console to fail gracefully if it it
> cannot start up, so you still deploy a GUI without causing the server
to
> fail and roll back the root deployment.
>=20
> > It
> > would be nice if there was a command line option (and SmartFrog
> > component) which would deploy all *.sf files in some directory (eg.
> > /etc/smartfrog/init.d). I am thinking of writing such component
myself,
> > but I don't know when I will get to it. Until then I would go with
> > init.sf which creates root compound and default.sf which deploys in
it
> > by default.
> >
>=20
> That's an idea I had last month and filed away as a possible future
todo
> item:
> http://jira.smartfrog.org/jira/browse/SFOS-149
>=20
> Have the unix startup scripts or a component deploy every .sf file in
a
> well known directory.
>=20
> There's some security complications there: do you want to keep
> everything secured in a JAR, or can you get away with everything in
> plain text .sf files. Personally, I like the plain text option, and
> would certainly like to see something like this too; something that
> would poll the dir for changes and undeploy when the file(s) go away,
> deploy when they arrive. It would let you do deploy-by-copy deployment
> of smartfrog systems.
>=20
> -steve
>=20
> > -a
> >
> > Steve Loughran wrote:
> >> I've been having some fun with the rpms and headless operation.
> >>
> >> 1. setting the DISPLAY to localhost:8 doesnt work. it may work on
some
> >> boxes, but not all.
> >>
> >> 2. what we ought to do is have the daemon start up from init.d
without
> >> any display at all, somehow.
> >>
> >> 3. we could maybe have it start up a specific default.sf
> >>
> >> 4. or we make the startup scripts clever, use the absence of
$DISPLAY
> to
> >> set java.awt.headless=3Dtrue and then dynamically decide whether to
> deploy
> >> the display or not based on the LAZY PROPERTY java.awt.headless.
> >>
> >> Thoughts?
> >
> >
> >
------------------------------------------------------------------------
> -
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Smartfrog-developer mailing list
> > Sma...@li...
> > https://lists.sourceforge.net/lists/listinfo/smartfrog-developer
>=20
>=20
> --
> -----------------------
> Hewlett-Packard Limited
> Registered Office: Cain Road, Bracknell, Berks RG12 1HN
> Registered No: 690597 England
>=20
>
------------------------------------------------------------------------
-
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Smartfrog-developer mailing list
> Sma...@li...
> https://lists.sourceforge.net/lists/listinfo/smartfrog-developer

Re: [Smartfrog-developer] headless operation

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

Aleksander Bandelj wrote:
> I like 4). SmartFrog would then start with /etc/smartfrog/init.sf. 

For the latest release we've just gone to -headless (which 
init.d/smartfrogd sets), so that you can
(a) test without trying to unset things
(b) not break on a mac which is Unix-without-X11.

We've also fixed the management console to fail gracefully if it it 
cannot start up, so you still deploy a GUI without causing the server to 
fail and roll back the root deployment.

> It 
> would be nice if there was a command line option (and SmartFrog 
> component) which would deploy all *.sf files in some directory (eg. 
> /etc/smartfrog/init.d). I am thinking of writing such component myself, 
> but I don't know when I will get to it. Until then I would go with 
> init.sf which creates root compound and default.sf which deploys in it 
> by default.
> 

That's an idea I had last month and filed away as a possible future todo 
item:
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.

There's some security complications there: do you want to keep 
everything secured in a JAR, or can you get away with everything in 
plain text .sf files. Personally, I like the plain text option, and 
would certainly like to see something like this too; something that 
would poll the dir for changes and undeploy when the file(s) go away, 
deploy when they arrive. It would let you do deploy-by-copy deployment 
of smartfrog systems.

-steve

> -a
> 
> Steve Loughran wrote:
>> I've been having some fun with the rpms and headless operation.
>>
>> 1. setting the DISPLAY to localhost:8 doesnt work. it may work on some 
>> boxes, but not all.
>>
>> 2. what we ought to do is have the daemon start up from init.d without 
>> any display at all, somehow.
>>
>> 3. we could maybe have it start up a specific default.sf
>>
>> 4. or we make the startup scripts clever, use the absence of $DISPLAY to 
>> set java.awt.headless=true and then dynamically decide whether to deploy 
>> the display or not based on the LAZY PROPERTY java.awt.headless.
>>
>> Thoughts?
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Smartfrog-developer mailing list
> Sma...@li...
> https://lists.sourceforge.net/lists/listinfo/smartfrog-developer


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

Re: [Smartfrog-developer] headless operation

[Aleksander B. <ale...@ac...>]

I like 4). SmartFrog would then start with /etc/smartfrog/init.sf. It 
would be nice if there was a command line option (and SmartFrog 
component) which would deploy all *.sf files in some directory (eg. 
/etc/smartfrog/init.d). I am thinking of writing such component myself, 
but I don't know when I will get to it. Until then I would go with 
init.sf which creates root compound and default.sf which deploys in it 
by default.

-a

Steve Loughran wrote:
> I've been having some fun with the rpms and headless operation.
> 
> 1. setting the DISPLAY to localhost:8 doesnt work. it may work on some 
> boxes, but not all.
> 
> 2. what we ought to do is have the daemon start up from init.d without 
> any display at all, somehow.
> 
> 3. we could maybe have it start up a specific default.sf
> 
> 4. or we make the startup scripts clever, use the absence of $DISPLAY to 
> set java.awt.headless=true and then dynamically decide whether to deploy 
> the display or not based on the LAZY PROPERTY java.awt.headless.
> 
> Thoughts?

[Smartfrog-developer] 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

[Smartfrog-developer] headless operation

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

I've been having some fun with the rpms and headless operation.

1. setting the DISPLAY to localhost:8 doesnt work. it may work on some 
boxes, but not all.

2. what we ought to do is have the daemon start up from init.d without 
any display at all, somehow.

3. we could maybe have it start up a specific default.sf

4. or we make the startup scripts clever, use the absence of $DISPLAY to 
set java.awt.headless=true and then dynamically decide whether to deploy 
the display or not based on the LAZY PROPERTY java.awt.headless.

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

[Smartfrog-developer] you need commons-logging to build the testharness

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

As of a few minutes ago, the testharness now depends on commons-logging 
to build and run; it also takes advantage of log4j if it is there. See 
http://jira.smartfrog.org/jira/browse/SFOS-191

you wont notice with ivy setting up the classpaths, but if you use the 
IDE to build and run the tests/testharness, add commons-logging-1.0.4 to 
the classpath of the testharness project, and, under idea, set up that 
project to export commons logging to all its dependents.

right now the change doesnt do much; it just makes logging in the tests 
at different levels a bit cleaner. All the test components now log via 
sfLog() too. Anyone writing more tests (yes please!) should use the 
commons-logging apis (subclasses of SmartFrogTestBase can call getLog() 
to get a log), or, in the components, with sfLog().

Where this gets interesting is if I were to use smartfrog to host the 
entire test run of tests itself. I havent done that yet, but I am 
thinking about what it would take...

-steve

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

Re: [Smartfrog-developer] wrong definition of ToggleToFalseWorkflow ?

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

Andreas Unterkircher wrote:
> Hello,
> 
> Looking at the tests for the Sequence component I see in the file
> 
> ./testharness/testcases/org/smartfrog/test/system/workflow/sequence/ 
> testSequence.sf
> 
> [...]
> 
> sfConfig extends TestBlock {
> 
>      action extends Sequence {
>        //set sfConfig:value=false
>         toggle1 extends ToggleToFalseWorkflow {
>            target LAZY PARENT:PARENT;
>         }
> 
> [...]
> 
> ToggleToFalseWorkflow is defined in ./testharness/testcases/org/ 
> smartfrog/test/system/assertions/components.sf:
> 
> [...]
> 
> ToggleToFalseWorkflow extends BooleanTrue {
>    sfShouldTerminate true;
> }
> 
> I think with this definition it does not set value=false in its  
> target attribute. Shouldn't the definition be
> 
> ToggleToFalseWorkflow extends ToggleToFalse {
>    sfShouldTerminate true;
> }
> 

Looks like it. I will make the change, and see what happens .

Thank you for your code review!

-steve

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

[Smartfrog-developer] wrong definition of ToggleToFalseWorkflow ?

[Andreas U. <and...@ce...>]

Hello,

Looking at the tests for the Sequence component I see in the file

./testharness/testcases/org/smartfrog/test/system/workflow/sequence/ 
testSequence.sf

[...]

sfConfig extends TestBlock {

     action extends Sequence {
       //set sfConfig:value=false
        toggle1 extends ToggleToFalseWorkflow {
           target LAZY PARENT:PARENT;
        }

[...]

ToggleToFalseWorkflow is defined in ./testharness/testcases/org/ 
smartfrog/test/system/assertions/components.sf:

[...]

ToggleToFalseWorkflow extends BooleanTrue {
   sfShouldTerminate true;
}

I think with this definition it does not set value=false in its  
target attribute. Shouldn't the definition be

ToggleToFalseWorkflow extends ToggleToFalse {
   sfShouldTerminate true;
}


?

Best regards,
Andreas

[Smartfrog-developer] Announcing Smartfrog 3.11.000beta

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

SmartFrog 3.11.000beta


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 artifacts are available at
http://sourceforge.net/project/showfiles.php?group_id=87384&package_id=176308&release_id=516351

This release is 3.11.000beta; the first beta of the 3.11 release, built 
on Java 1.5
from revision 4328 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 sfUnit testing.
* 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:

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

The JAR installer will become the recommended distribution in the future;
the original distribution is retained for backwards compatibility, and 
because
we have yet to integrate the documentation with the JAR installer.

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.

Again, we hope to broaden the contents of the RPM packaging and perhaps
supplement with a .deb distribution.

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.

The files and SHA1 checksums are:

9a5e7da61309fb4e214a1812d2f9d9da4db1a867 
sf.3.11.000beta.20070614_all.tar.gz
d3f7488d7afad967b508c1ba8769f52a500a4f65  sf.3.11.000beta.20070614_all.zip
bd06a2d61fea78f4297eb693872debc8db28c3c5 
sf.3.11.000beta.20070614_dist.tar.gz
5dbfcb841f3182a064834eb76ce4ee93613c4901  sf.3.11.000beta.20070614_dist.zip
a8fba7fc8a51e625defbab46d8646610e022c1f8  sf-install-3.11.000beta.jar
306eeda6da1da2a2530435dd34a10a6c2eb0fb29  sf-rpm-bundle-3.11.000beta.tar.gz


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.

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/

Re: [Smartfrog-developer] problem with rpm task

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

Andreas Unterkircher wrote:
 > Hello,
 >
 > I just tried to build SF 3.11.000beta on Mac OS X but it fails with
 >
 > rpm:
 >       [rpm] Building the RPM based on the smartfrog.spec file
 >
 > BUILD FAILED
 > /Users/unterkir/workspace/SmartFrog/build.xml:491: The following error
 > occurred while executing this line:
 > /Users/unterkir/workspace/SmartFrog/release/build.xml:291:
 > java.io.IOException: rpm: not found
 >
 > This is understandable as there is no rpm on Mac OS X as far as I know.
 > I think it would be best to make the rpm task optional and disabled per
 > default. Or one introduces some detection to see if rpm is present on
 > the build machine.
 >

I had the build switching to use rpmbuild on unix/not unix, as you can 
even get the exe on non-linux systems.

I will tweak the test to be unix && rpmbuild is in env.PATH

.

[Smartfrog-developer] problem with rpm task

[Andreas U. <and...@ce...>]

Hello,

I just tried to build SF 3.11.000beta on Mac OS X but it fails with

rpm:
       [rpm] Building the RPM based on the smartfrog.spec file

BUILD FAILED
/Users/unterkir/workspace/SmartFrog/build.xml:491: The following  
error occurred while executing this line:
/Users/unterkir/workspace/SmartFrog/release/build.xml:291:  
java.io.IOException: rpm: not found

This is understandable as there is no rpm on Mac OS X as far as I  
know. I think it would be best to make the rpm task optional and  
disabled per default. Or one introduces some detection to see if rpm  
is present on the build machine.

Best regards,
Andreas

[Smartfrog-developer] release 3.11.0000beta1 is SVN commit #4328

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

I'm about to start uploading the release artifacts to the various 
repositories; SVN repository at commit #4328 built on Java1.5 is the 
release marker (no, I havent made a tag yet in SVN, because I have to 
set up the entire repository image first, and that takes time indeed)


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

[Smartfrog-developer] binary release to be made tonight

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

Hello,

I'm just warning that once I've got all the tests passing on my clean 
Java1.5/xubuntu vm, (which may involve skipping out those tests that 
fail unless run.failing.tests is set), then I'm going to tag the 
repository and make a release. This will be something like smartfrog 
3.11.0000.beta1, and will include the izpack and rpm packagings 
alongside the original .zip and .gz distributions.

If anyone has any major changes that may break anything,  now is not the 
ideal time to commit them; hold them off until after the release

-steve

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

[Smartfrog-developer] Cruise Control is working!

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

Just a note to point out that CC is working, to the extent that if a 
build fails, it is probably a real test failure, and not some build problem.

The CC server now
  -builds every component that builds under java1.4, and some of the 
stuff under /extras (anyting with an ivy.xml file that it has not been 
told to skip)
-runs the test target on every component, as well as the main 
testharness run.

There is much more building and testing than before. This makes the 
build slow, and with more tests, the likelihood of a change breaking a 
test is higher. But the outcome should be less surprises when we ship.

-steve

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

[Smartfrog-developer] SFOS-91: Abnormal TerminationRecords dont deserialize unless the far end can load every exception in the exception chain

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

There's something I'd like to discuss to see how people react: bug 
SFOS-91, "Abnormal TerminationRecords dont deserialize unless the far 
end can load every exception in the exception chain"

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

when you create a TerminationRecord with a nested exception, that 
exception gets included in the serialization that gets sent over RMI. If 
the far end doesnt have every JAR for every fault that could be thrown 
by the far end, the file won't deserialize, so you can't find out why 
something terminated. You know that your database isnt there, but you 
don't know that you got a  com.mysql.MysqlException with something 
meaningful inside,

I've written the code to take a chained fault and if anything in the 
chain is not an instanceof SmartFrogException, convert it to 
SmartFrogExtractedException. Once you set the cause of an exception, you 
can't change it, which is why I have to recreate the whole tree, when 
needed:

http://svn.sourceforge.net/viewvc/smartfrog/trunk/core/smartfrog/src/org/smartfrog/sfcore/common/SmartFrogExtractedException.java?view=markup

the only place this is being used right now is TestBlockImpl and 
TestCompoundImpl, both of which implement an RMI method to return 
whatever exception caused the test to fail. I'm explicitly 
post-converting the TerminationRecord after the test run.

What I am wondering, is this:

1. should we *always* convert the exception chain in a termination 
record to a list of exceptions that we believe are terminatable

2. what breaks?

3. what exceptions should we leave alone? Right now I convert all that 
isnt instanceof SmartFrogException, but we could also expand this to 
include everything in a class under java.*, and maybe those javax.* 
packages built in to java1.4.

There's a risk of things breaking if they actually read in the term 
record and look for a specifically typed exception. Has anything other 
than the tests (that we can change) made use of this?

-steve

Re: [Smartfrog-developer] creating child compound component

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

Hi,

=20

________________________________

From: sma...@li...
[mailto:sma...@li...] On Behalf Of
Kalbagilmath, Vishwanath (STSD)
Sent: 16 March 2007 05:33
To: sma...@li...
Subject: [Smartfrog-developer] creating child compound component

=20

hi,

Is it possible to create a new child component of type Compound under
another Compound component, I could see a method sfCreateNewChild()
which creates child of type Prim, however I did not find one for
Compound component. Is the purpose of sfAddChild(), to convert the child
Prim component to Compound?

=20

sfCreateNewChild() can create any type of child as long as it implements
Prim interface. Compound implements Prim (aka Primitive) and the same
with every SmartFrog component.

sfCreateNewChild() will use sfAddChild(). You don't need to use
sfAddChild() unless you manage you deployment manually.


I understand that, when a child SF component (either Prim or Compound)
is created, it undergoes its entire lifecycle. Can the entire lifecycle
process be bypassed?

Yes, but it is up to the parent to decide this. Compound will drive its
children through their lifecycle but other components like Parallel will
behave in a different way.

Programmatically you can change all this to fit your requirements. Check
this thread for more info

http://thread.gmane.org/gmane.comp.java.smartfrog.devel/517/focus=3D521

PS:
=20
Reminder: the lists archives with RSS feeds are available at:
http://news.gmane.org/search.php?match=3Dsmartfrog


Thanks in adv,
--ViK

Re: [Smartfrog-developer] problem with component deploy

[Murray, P. \(HP L. Bristol\) <pm...@hp...>]

The message below seems to describe the problem we had last week -
although we were running with 3.10.035. At the time we had other
problems with a messed up environment so we decided to sort everything
out and try again.=20

Sebastien, did it re-occur after sorting out your environment? Did you
manage to sort out the build?=20

The problem was not a matter of a refresh. As with the message below, we
also had the sfStart command completing successfully but reporting the
name *unknown*.

Paul.

-----Original Message-----
From: sma...@li...
[mailto:sma...@li...] On Behalf Of
Goldsack, Patrick
Sent: 21 March 2007 06:50
To: Kalbagilmath, Vishwanath (STSD);
sma...@li...
Subject: Re: [Smartfrog-developer] problem with component deploy


I suspect that you simply have to "refresh" the window - there is a
button to do that.

Patrick=20

-----Original Message-----
From: sma...@li...
[mailto:sma...@li...] On Behalf Of
Kalbagilmath, Vishwanath (STSD)
Sent: 21 March 2007 02:16
To: sma...@li...
Subject: [Smartfrog-developer] problem with component deploy

hello,

Though sfStart says successfully deployed (see o/p below), the sfPing is
successful and even I could see the prints I have in sfStart method of
component.

(C) Copyright 1998-2006 Hewlett-Packard Development Company, LP
 - Successfully deployed: 'HOST "15.76.222.25":rootProcess:*unknown*',
[simulators/components/ABC.sf],  host:localhost

But I still don't see the deployed component on the GUI window of
sfDaemon. Even the sfResolve() is failing to resolve this component.

Maybe the catch here is the name of the component, though I give any
name to CLI sfStart (in my case I gave as VIK) but then the output is
*unknown*

I am missing anything here? I have SF 3.10.016 running and have set
SFHOME and SFUSERHOME appropriately.

Note: I did not see this problem when I build my stuff under
~org.smartfrog.example.abc with SF 3.10.000 version


thanks in adv, for your helping

--ViK



------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDE
V
_______________________________________________
Smartfrog-developer mailing list
Sma...@li...
https://lists.sourceforge.net/lists/listinfo/smartfrog-developer

------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDE
V
_______________________________________________
Smartfrog-developer mailing list
Sma...@li...
https://lists.sourceforge.net/lists/listinfo/smartfrog-developer

Re: [Smartfrog-developer] problem with component deploy

[Goldsack, P. <pat...@hp...>]

I suspect that you simply have to "refresh" the window - there is a
button to do that.

Patrick=20

-----Original Message-----
From: sma...@li...
[mailto:sma...@li...] On Behalf Of
Kalbagilmath, Vishwanath (STSD)
Sent: 21 March 2007 02:16
To: sma...@li...
Subject: [Smartfrog-developer] problem with component deploy

hello,

Though sfStart says successfully deployed (see o/p below), the sfPing is
successful and even I could see the prints I have in sfStart method of
component.

(C) Copyright 1998-2006 Hewlett-Packard Development Company, LP
 - Successfully deployed: 'HOST "15.76.222.25":rootProcess:*unknown*',
[simulators/components/ABC.sf],  host:localhost

But I still don't see the deployed component on the GUI window of
sfDaemon. Even the sfResolve() is failing to resolve this component.

Maybe the catch here is the name of the component, though I give any
name to CLI sfStart (in my case I gave as VIK) but then the output is
*unknown*

I am missing anything here? I have SF 3.10.016 running and have set
SFHOME and SFUSERHOME appropriately.

Note: I did not see this problem when I build my stuff under
~org.smartfrog.example.abc with SF 3.10.000 version


thanks in adv, for your helping

--ViK



------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDE
V
_______________________________________________
Smartfrog-developer mailing list
Sma...@li...
https://lists.sourceforge.net/lists/listinfo/smartfrog-developer