mp3dj

File Release Notes and Changelog

Release Name: mp3dj-4.5

Notes:
The 4.5 release transitions from Flex2 to Flex3 SDK and removes
LCDS and JBoss from the required external components list.
Installation was simplified by bundling the turnkey version of
BlazeDS contributed to Open Source by Adobe, which includes
a Tomcat server.  Ant seamlessly restarts the server after
deploying the webapp.  Ant also creates the /music context
through mp3 files are accessed by Flash Player.


Changes:
# Refrained from starting player at startup.

# Made "refresh" target antcall the "install" target to get
the ApplicationService to reconnect to the database.

# Renamed database.directory  property to database.dir
in build.properties.  Renamed routines and variables in
ApplicationService.java and RefreshFiles.java to match.

# Engaged blazeds_turnkey_3-0-0-544.zip which includes Flex3
SDK, and Tomcat 6.0.14.  Created "unzip-blazeds", which is
invoked from the "prepare" target, to recreate blazeds/ when
blazeds/blazeds.war is not present.  Made the "clean" target
remove the blazeds/ subdirectory.

# Made "unzip-blazeds" also extract flex_skd_3.zip and
runtimes/player/lnx/flashplayer.tar.gz.  Made  the flashplayer
excutable, and made the 'go' and 'go.bat' scripts run the
bundled debugger.

# Removed jboss.* from build.properties, and updated build.xml
to deploy to bundled Tomcat server.

# Automated the "server.xml edit" to create a /music context
to database.dir.   Changes to database.dir in build.properties
are propogated when you deploy the webapp (see the "install"
target in build.xml).  A /music context is created by ant when
it unzips the blazeds distribution file.

# Added "start-windows" and "start-nonwindows" (os family
specific) targets to start the bundled Tomcat server.

# Made the "run" target deploy the webapp, start Tomcat, and
run the browser seamlessly.  This is the default Ant target,
so simply entering 'ant' in the root mp3dj directory does
everything seamlessly.

# Augmented start targets with "stop-nonwindows" and
"stop-windows" targets.   Created separate "-ok" test targets
for the matrix of start and stop targets.  Added test to ensure
scripts exist before attempting to stop.  Verifying CATALINA_PID
file is available before stopping non-windows servers to avoid
messages in the server log when its not running.

# Added tomcat.port property to build.properties to facilitate
using something other than 8400. Made "install" propogate to
the server.xml file.

# Refactored getMessage() in session scope into getStats() in
application scope.  Removed  SessionService.java.  We've never
required client specific state on the server; we have dialogs.

# Added "start" and "stop" Ant targets for starting and stopping
servers.  Made the "run" target depend on "start" rather than
"install".  Made "clean" depend on "stop" so before removing
blazeds/ which contains blazeds/tomcat/bin/${CATALINA_PID}, we
shutdown and free up the server ports.  Also made the "start"
target depend on "stop" to ensure changes to database.dir
in build.properties , which are propogated to server.xml get
engaged by restarting the Tomcat server.

# Updated the go and go.bat flashplayer debugger scripts to use
"start" rather than "install".

# Added "asdoc" Ant target to recreate docs/asdoc (ActionScript
API documentation).

# Added Mac OS/X Installation Instructions.

# Moved /music <context> from server.xml to music.xml. Added
blazeds-tomcat-conf-Catalina-localhost-music.xml, and made
"install" propogate database.dir.  When "refresh" completes
successfully it calls "install", and Tomcat hot deploys after
the edit so the webapp engages a possibly new database.dir
value without restarting the server.  Found no other way than a
server restart to engage database.url, so we're calling "stop"
and then "start" after refreshing successfully.

# Removed browser.executable property, and the "run" Ant target.
Made "start" the default Ant target.