Getting Started with Adobe LiveCycle Data Services and JavaPosted: October 30, 2007
Update: Unfortunately, it didn’t take much longer before this configuration ran into memory and other problems. I am looking into other options that are more robust.
Over the past few days, I’ve been experimenting with Adobe LiveCycle Data Services and Java to build a Java-backed Flex application. Over the next few posts, I will chronicle my experiences in the hopes of others avoiding some of the pitfalls I have encountered.
To get started, we’ll set-up and configure our development environment. In order to support development of both the client (Flex) and server (Java), I wanted to configure my IDE to handle both Flex and Java EE.
Note: I always like to use the latest and greatest, but Flex Builder 3 beta 2 and Eclipse 3.3 do not play nicely together. This configuration led to an “Out of Memory” error every twenty minutes or so, which became unmanageable. The approach I followed utilizes Flex Builder 2 with Eclipse 3.3, this is not a support configuration, but it is done in a way that allows you to easily disable the Flex Builder features if desired.
- Eclipse 3.3 for Java EE Developers
- Flex Builder 2 (free 30 day trial available)
- LiveCycle 2.5.x
- Flex SDK 2.01 hotfix 2 (included in the above FB distribution)
- Download all of the above packages.
- Extract Eclipse to a known location. I used “C:\eclipse3.3”
- Install Flex Builder 2 at “C:\Program Files\Adobe\Flex Builder 2” as the stand alone version, not the plug-in
- Install LiveCycle Data Services at “C:\Program Files\Adobe\lcds”
Out of the box, Flex Builder 2 does not work with Eclipse 3.3. A detailed tutorial on how to configure Eclipse to use Flex Builder 2 is available, but the following is the process that I utilized:
- Create a new Eclipse extension:
- Create a new directory “C:\eclipse3.3\extensions” and a second directory “C:\eclipse3.3\extensions\eclipse”
- In this directory, create an empty “.eclipseextension” file (hint: from a command prompt, enter “echo > .eclipseextension”)
- Create two additional directories in the new eclipse directory: “plugins” and “features”
- In Eclipse, select Help > Software Updates > Manage Configuration…
- In the right panel, click on “Add an Extension Location”
- Navigate to “C:\eclipse3.3\extensions” and click “Ok”
- Close Eclipse
- If you have a license for Flex Builder 2, you should launch Flex Builder and enter the license key now. You can then close FB.
- We will now merge Flex Builder into Eclipse:
- Copy “C:\Program Files\Adobe\Flex Builder 2\configuration\com.adobe.flexbuilder.”
- Copy “C:\Program Files\Adobe\Flex Builder 2\features\com.adobe.flexbuilder.*” to your extension feature directory “C:\eclipse3.3\extensions\eclipse\features.”
- Copy “C:\Program Files\Adobe\Flex Builder 2\features\com.adobe.flexbuilder.*” to your extension plugins directory “C:\eclipse3.3\extensions\eclipse\plugins.” Note: There are directories and jar files that need to be copied.
- Finally, restart Eclipse via the clean option (open a command prompt at “C:\eclipse3.3” and enter “eclipse – – clean”). This forces a reload of all Eclipse plugins.
You can verify that Flex Builder capabilities have been installed by checking if the “Flex Development” perspective is available (Window > Open Perspective > Other).
Finally, we will install Peter Martin’s outstanding FDS plugin, which we can use to generate application skeletons for LCDS projects:
- Download the plugin
- Launch Eclipse (if not already open)
- Select Help > Software Updates > Find and Install
- Select Search for new features to install
- Click New Archived Site
- Select the plugin ZIP file you downloaded
- Click Finish
- Check the feature
- Complete the wizard and restart Eclipse when prompted
I’ve been running this configuration for some time now and it seems to be stable (i.e. no Out of Memory errors). I will post updates with any glitches that need to be fixed.