Recently in Data Services Category

LiveCycle Data Services 3 and doc available

| No Comments

LiveCycle Data Services ES2 version 3 is now available. Download the free developer edition.


LiveCycle Data Services documentation is available online:

* Using LiveCycle Data Services HTML | PDF
* Application Modeling Technology Reference HTML | PDF
* ActionScript Language Reference HTML
* Installing LiveCycle Data Services HTML
* Javadoc HTML
* Release Notes HTML
* Quick Starts HTML

LiveCycle Data Services 3 Beta Available

| No Comments

LiveCycle Data Service 3 Beta 1 is now available on Adobe Labs.

The new model-driven development features in LiveCycle Data Services 3 offer a huge leap in productivity and ease-of-use for end-to-end applications. You start an application by creating a data model (a simple XML file) in the new "Modeler" editor that plugs into Flash Builder. From that model, you automatically generate data access logic on the server and Flex client code for working with the server code.

You can even generate much of a model by dragging existing SQL database tables into the Modeler editor. When you save the model, client code is automatically generated. When you deploy the model to the server, a fully functional Data Management Service destination is automatically generated on the LiveCycle Data Services server. You can support even the most advanced Data Management Service features just by creating and deploying a model.

Using Flash Builder with LiveCycle Data Services, you can now build simple or complex data-driven applications without writing any server-side code or configuration files. You can also take full advantage of the new Flash Builder 4 features for building the client side of data-driven applications.

We would love to get your feedback on this release and the documentation. To learn more:

Calling remoting destinations from Flash or Java applications

| 1 Comment
The legacy NetConnection API of Flash Player provides a way to call remoting destinations from a standard (non-Flex) Flash application or from ActionScript in a Flex application if desired. The new Java AMF Client in BlazeDS gives you a Java API patterned on the NetConnection API but for calling remoting destinations from a Java application. You can use either of these APIs with BlazeDS, LiveCycle Data Services, or third-party remoting implementations.

Call a remoting destination from a Flash application

You can use the Flash Player flash.net.NetConnection API to call a BlazeDS remoting destination from a Flash application. You use the NetConnection.connection() method to connect to a destination and the NetConnection.call() method to call the service. The following MXML code example shows this legacy way of making remoting object calls with NetConnection instead of RemoteObject:
<?xml version="1.0"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" width="100%" height="100%"
  creationComplete="creationCompleteHandler();">
  <!--
  -->
  
  <mx:Panel id="mainPanel" height="100%" width="100%">
  <mx:HBox> 
  <mx:Label text="Enter a text for the server to echo"/>
  <mx:TextInput id="ti" text="Hello World!"/>
  <mx:Button label="Send" click="echo()"/>
  <mx:Button label="Clear" click='ta.text = ""'/>
  </mx:HBox>
  <mx:TextArea id="ta" width="100%" height="100%"/>
  </mx:Panel>
  <mx:Script>
  <![CDATA[
  import flash.net.NetConnection;
  import flash.net.ObjectEncoding;
  import flash.net.Responder;
  private var nc:NetConnection
   
  private function creationCompleteHandler():void
  {
   nc = new NetConnection();
   nc.objectEncoding = ObjectEncoding.AMF0;
   nc.connect("http://[server]:[port]/yourapp/messagebroker/amf" );
  }
  private function echo():void
   {
    nc.call( "remoting_AMF.echo", new Responder( resultHandler, faultHandler ), ti.text );
   }
  private function resultHandler(result:Object):void
  {
   ta.text += "Server responded: "+ result + "\n";
   }
  private function faultHandler(fault:Object):void
  {
   ta.text += "Received fault: " + fault + "\n";
  }
  ]]>
  </mx:Script>
</mx:Application>

Call a remoting destination from a Java application

The Java AMF Client is new Java client API in the BlazeDS flex-messaging-core.jar file that makes it simple to work with remoting destinations from a Java application. The Java AMF Client is similar to the Flash Player flash.net.NetConnection API, but uses typical Java coding style rather than ActionScript coding style. The Java AMF Client classes are in the flex.messaging.io.amf.client* package in the flex-messaging-amf.jar file. The primary class of the Java AMF Client is the AMFConnection class. You connect to remote URLs with the AMFConnection.connect() method and call the service with the AMFConnection.call() method. You catch ClientStatusException and ServerStatusException exceptions when there are errors. Here's a simple example of how you can use AMFConnection to call a Remoting Service destination from a method in a Java class:
public void callRemoting()
{
  // Create the AMF connection.
  AMFConnection amfConnection = new AMFConnection();

  // Connect to the remote url.
  String url = "http://[server]:[port]/yourapp/messagebroker/amf";
  try
  {
     amfConnection.connect(url);
  }
  catch (ClientStatusException cse)
  {
     System.out.println(cse);
     return;
  }

  // Make a remoting call and retrieve the result.
  try
  {
     Object result = amfConnection.call("remoting_AMF.echo", "echo me1");
  }
  catch (ClientStatusException cse)
  {
     System.out.println(cse);
  }
  catch (ServerStatusException sse)
  {
     System.out.println(sse);
  }
  // Close the connection.
  amfConnection.close();
}
The Java AMF Client automatically handles cookies similarly to the way in which web browsers do, so there is no need for custom cookie handling.

LiveCycle Data Services ES 2.6 documentation

| 1 Comment

We are happy to announce that LiveCycle Data Services ES 2.6 was just released and includes many documentation improvements. Much of the documentation has been revised and reorganized, and there are completely new sections on:
Getting Started
- Introduction
- Building and deploying

Architecture
- General architecture
- Channels and endpoints
- Managing session data

You can get the documentation here:
http://www.adobe.com/support/documentation/en/livecycledataservices/

The main product page is here:
http://www.adobe.com/products/livecycle/dataservices/

Thanks go out to the LiveCycle Data Services development and quality engineering teams, who put a great effort into shaping and reviewing this content. Special thanks go to Mete Atamel, Seth Hodgson, Ed Solovey, and Jeff Vroom for their contributions.

Master-Detail Flex Application

| 4 Comments

I’m an Adobe writer assigned primarily to Flex Builder and the Flex SDK. I joined Adobe in October of 2007 and have spent the first few months learning and using Flex and Flex Builder.

I’ve recently completed my first Flex application, and am using this blog to write about my learning experience, and also to describe some of the concepts behind the application that make it work. Actually, these are two applications that work together, vRadio and RadioLoginDB.

These applications illustrate how to use Flex to create a master-detail application that accesses data from a PHP server, and also incorporates PHP sessions.

At the end of this posting is a list of documentation sources I used to learn how to create the applications. I also have links to the source files.

vRadio and RadioLoginDB applications

I have always been a fan of Community Radio, and in the past I’ve Googled “Community Radio” to find new stations to listen to over the web. I created the vRadio application to provide a Flex alternative that lists Community and Talk radio stations, providing details about each station including station name and location, station graphic, and clickable links to open the station. RadioLoginDB is a CRUD application to update the database of radio stations used by vRadio.

vRadio is a Master-Detail application, and corresponds to many type of applications that present stored data in a variety of presentation formats, and also provide forms for updating the data.

What is interesting about the the vRadio application is the way Flex handles XML data using the E4X format. By providing an XML feed into the vRadio application, the application displays the XML data in a tree view. When the user clicks a node in the tree, details are displayed.

Community Help

Contribute to Community Help

About this Archive

This page is an archive of recent entries in the Data Services category.

Data Binding is the previous category.

Drag and Drop is the next category.

Find recent content on the main index or look in the archives to find all content.