Solutions for developers new to CQ 5 – by Kurt Mossman

Posts in Category "Uncategorized"

A complete example of using data services with ADEP for Windows. This provides instructions for installing Java, Maven, Flash Builder and ADEP. This contains all the instructions and source code necessary to execute a simple java class example with Flash Builder and Data Services. This information also exists within the ADEP documentation here http://help.adobe.com/en_US/enterpriseplatform/10.0/documentation.html. This document provides you with step-by-step instructions.

This had me confused because I “thought” I had configured everything correctly on this new machine. I checked the build.xml and found it failed on the mustellaresultsparser.

After about 30 minutes of review I realized that I didn’t configure the Flash Player with the mm.cfg for the trace output and looking at the java class for MustellaResultsParser it was clear that it was necessary.

Make sure you have the following lines in your mm.cfg file.
ErrorReportingEnable=1
TraceOutputFileEnable=1

Using Flex 4 and the Spark components you can create a custom SkinClass that looks just like the Halo Flex 3 Button. See the attached example files ButtonSkin.mxml and HaloTheme2.mxml the Button below on the right is a Spark Button and the one on the left is a mx Button.
s|Button
{
skinClass: ClassReference("ButtonSkin");
}

Notice in the configuration above we want to send a request from the Client to the Load Balancer as SSL. To do this the SWF uses a channel-definition for SSL. The following class will be used by the SWF to create the channel within ActionScript class=”mx.messaging.channels.SecureAMFChannel“. This will send the request to the Load Balancer where it will terminate the SSL and decrypt it.

The next step in this process is to pass the data from the Load Balancer to the Application server as in the diagram below.

On the server we need to modify the endpoint so it will not use a class that tries to decrypt the data. In this case we will use the endpoint class that specifies AMFEndpoint.

With this modification the request is received on the server at the endpoint https://{server.name}:{server.port}{context.root}/messagebroker/amfsecure/ it will use the flex.messaging.endpoints.AMFEndpoint to process the request. This endpoint will not decrypt the data and will pass back the request to the Load Balancer.

NOTE: Applications built against Adobe AIR 2 beta 1 will not run using the AIR 2 beta 2 runtime. In order for an AIR 2 beta 1 application to run on the AIR 2 beta 2 runtime, the namespace of the beta 1 application descriptor file must first be updated to “2.0beta2” and compiled against the AIR 2 beta 2 SDK. .