BlazeDS Development

BlazeDS is the server-based Java remoting and web messaging technology enables you to easily connect to back-end distributed data and push data in real time to Adobe Flex and Adobe AIR applications in order to garner more responsive Rich Internet Application (RIA) experiences. It is a scalable option for Flex and Java integration and allows you to create excellent RIAs with both Flex and Java.

The evolution to more engaging RIAs has created the need for better data connectivity options. Remoting simplifies the reuse of existing server logic automatically marshalling calls between the Flash client and the Java methods on the server. In addition, the use of a AMF binary data transfer format increases performance, allowing applications to load data up to 10 times faster than with text-based formats such as XML or SOAP.

BlazeDS provides higher level data functionality such as data synchronization, offline support for Adobe AIR, portal integration, RIA integration with LiveCycle Enterprise Suite business processes and document services, as well as more advanced deployment options for maximum scalability.

Benefits:

• Easily connect Flex and Adobe AIR applications built using Flex and Ajax to existing Java server logic
• High performance data transfer for more responsive applications
• Real-time server push over standard HTTP
• Full pub/sub messaging that extends existing messaging infrastructure
• Free and Open source
• The Remoting Service allows your Flex application to directly invoke methods of Java objects deployed in your application server.
• The Message Service provides a publish/subscribe infrastructure that allows your Flex application to publish messages and subscribe to a messaging destination, enabling the development of real-time data push and collaborative applications.
• The Proxy Service allows your Flex application to make cross-domain service requests in a secure and controlled manner. In other words, it allows your Flex application to access a service available on a domain other than the domain from which the application was downloaded (without having to deploy a crossdomain.xml policy file on the target domain).