Posts tagged Mosaic

ADEP: Flex tile is blank? Use the supported Flex SDK version

- Scott Brodersen

I recently had the opportunity to help troubleshoot a Composite Application Framework issue. A member of our community worked through the Create a composite application module of the Create Your First ADEP Experience Server Application tutorial.

Problem: The Flex tile did not populate (it was blank), although the HTML tile appeared fine.

Solution: Use Flex SDK 4.5. Do not use version 4.5.1

Note: This problem/solution applies to ADEP 10.0.0.0. I don’t know what version of the SDK that future ADEP/CAF releases will support out-of-the-box.

If you used Flex SDK 4.5.1 by mistake, here is how to configure the project and tile to use Flex SDK  4.5.0:

  1. In Flash Builder, right-click the Flex project for ADEP and click Properties.
  2. In the properties tree, select Flex Compiler.
  3. At the top of the Flex Compiler panel, set the SDK version to Flex 4.5.
  4. Click OK and when the scary message about overwriting the html-template pops up, click OK.
  5. Open the catalog file (.cxml).
  6. Locate the tile:TileClass element for your tile and in the tile:Content child element, change the value of the flexSDKVersion attribute to 4.5.0.
    <tile:TileClass fitContent="true" height="300" label="WatchedFunds" name="WatchedFunds" width="600">
          <ct:Metadata>
               <ct:Description/>
          </ct:Metadata>
          <tile:Content contentType="application/x-shockwave-flash" flexSDKVersion="4.5.0" loadAs="module" uri="${catalogURL}/tiles/WatchedFunds/WatchedFunds.swf"/>
    </tile:TileClass>
  7. Save the file.

——-

Original article at http://blogs.adobe.com/ADEPhelp/2011/10/adep-flex-tile-is-blank-use-the-supported-flex-sdk-version.html.

Use logging with your Composite Application Framework app

- Scott Brodersen

Adobe forums served up some nice information about logging runtime messages for your Composite Application Framework (aka Mosaic) apps. The Client Component Framework (codename: Gravity) provides the logging libraries….Composite Application Framework runs on Client Component Framework….here’s how to get those logger juices flowing:

<quote>

Yes, Gravity logging APIs can be used in Mosaic as-is. To view the log output:

1.       Open CRXDE lite in a browser and log in
2.       Navigate to /libs/mosaic/components/index/index.jsp
3.       Locate the line in the file that initializes the flashvars variable. In 10.0 this should be on line 65
4.       After that line, add a new line:

flashvars.mdebug = true;

5.       Click the “Save All” button to save the changes

Then, when a new application is launched, a debug window will appear with a “Log Viewer” tab. Note that the debug window will appear in the upper left corner of the browser in a layer that will be behind html or pdf content, so if your application’s layout has html or pdf content in the upper left region you may not be able to see the debug window.

</quote>

What was the OP’s result you may ask?

“That debug window certainly is useful. It has much more useful information than I was expecting. The DOM Viewer is especially nice. It is good to be able to confirm which libraries get loaded.”

Read the full blog post here.

Adobe Retires the “LiveCycle” Brand, Its Services Become Part of Broader Capability

Jayan Kandathil

On June 20, 2011, Adobe announced its new “Digital Enterprise Platform” software or ADEP. The platform is designed to address a new problem domain that Adobe and others have identified as “Customer Experience Management” or CEM. Please use the Twitter hashtag #AdobeCEM to follow tweets regarding CEM.

For customers with extant investment in Adobe LiveCycle and are wondering about what all of this means to them, here are some points to consider:

1) The enterprise services, and the orchestration capabilities that LiveCycle provided will all continue to be available as part of the new Adobe Digital Enterprise Platform software. They will henceforth be called “Document Services“.

2) “Document Services” will continue to be J2EE (JEE) applications requiring a J2EE appserver such as JBoss, WebSphere or WebLogic as well as a relational database such as Oracle, SQL Server, DB2 or MySQL.

3) Day CQ5 will become a “Customer Experience Solution” named “Web Experience Management”. There will also be other Customer Experience Solutions.

4) Mosaic will henceforth be called “Composite Application Framework”

5) LiveCycle Data Services will become “Data Services”

5) All “Customer Experience Solutions”, “Composite Application Framework” and “Data Services” will run on the new Apache Felix OSGi framework, not J2EE (no Tomcat, JBoss, WebSphere or WebLogic required). They will be using a JSR-283 compliant Java Content Repository (JCR) – no relational database will be required.

Here’s a simple equation to remember:
ADEP = LiveCycle + (Day) CQ5 + Mosaic + Data Services + “Customer Experience Solutions” (formerly “Solution Accelerators”)

We will be renaming this blog once the Adobe Digital Enterprise Platform software is released.

For those interested in the history of Adobe’s LiveCycle brand, see this.

——-
Original article at http://blogs.adobe.com/livecycle/2011/06/adobe-retires-the-livecycle-brand-its-services-become-part-of-broader-capability.html.

Go to Top