Apache Flex SDK is an application development framework for easily building
Flash-based applications for mobile devices, web browsers, and desktops.
Apache Flex BlazeDS is the server-based Java remoting and web messaging
technology that enables developers to easily connect to back-end distributed
data and push data in real-time to Adobe® Flex® and Adobe AIR™ applications
for more responsive rich Internet application (RIA) experiences.
Apache Flex BlazeDS 4.8.0 is an update to the initial release of BlazeDS
from the Apache Software Foundation. Prior to this, releases were provided
by Adobe Systems Inc. It is compatible with most code written to target Adobe
Flex 4.6.
For detailed information about Apache Flex please visit
http://flex.apache.org/
Getting the latest sources via Git
==================================
Getting the source code is the recommended way to get Apache Flex BlazeDS.
You can always checkout the latest source via git using the following
command:
git clone https://git-wip-us.apache.org/repos/asf/flex-blazeds.git blazeds
cd blazeds
git checkout develop
For further information visit http://flex.apache.org/download-source.html
Building Apache Flex BlazeDS 4.8.0
==================================
Apache Flex BlazeDS is a large project. It requires some build tools which must be
installed prior to building BlazeDS and it depends on some external software
which are downloaded as part of the build process. Some of these have
different licenses. See the Software Dependencies section for more
information on the external software dependencies.
From Apache's perspective, the Adobe Flash Player and Adobe AIR have
excluded licenses so they can not be bundled with the Apache Flex binaries.
They must be installed prior to building Apache Flex.
Linux support is currently experimental and while it is possible to compile
BlazeDS it has not been fully tested so you may run into issues.
Install Prerequisites
---------------------
Before building the Apache Flex BlazeDS you must install the following software
and set the corresponding environment variables using absolute file paths.
Relative file paths will result in build errors.