LiveCycle Data Services 3.1 and BlazeDS 4 are available

The LiveCycle Data Services version 3.1 is available for download, and also BlazeDS version 4.0. The main features are the extensibility of the model-driven development and improvements to the offline data management feature. A much detailed description can be found on Damon Cooper blog.
SHARETHIS.addEntry({ title: “LiveCycle Data Services 3.1 and BlazeDS 4 are available”, url: “http://cornelcreanga.com/2010/04/livecycle-data-services-31-and-blazeds-4-are-available/” });

LCDS, ManagedObjectProxy and some reserved keywords

Yesterday I struggled for several hours looking in the Livecycle Data Services code in order to investigate the following error message:TypeError: Error #1034: Type Coercion failed: cannot convert “ZGUID” to QName. It was not easy but in the end I understood that it is an issue related to property collision inside of ManagedObjectProxy  class. The […]SHARETHIS.addEntry({ title: “LCDS, ManagedObjectProxy and some reserved keywords”, url: “http://cornelcreanga.com/2009/12/lcds-managedobjectproxy-and-some-reserved-keywords/” });

Flex Data Services, Hibernate and Eclipse – Mike Slinn book

A lot of books about Flash, Flex, ActionScript and Java are available on the market and some of them are really good – however there are still no comprehensive books related to Flex and Java integration – best practices, frameworks, performance issues, patterns and anti patterns. Mike book fills a gap here, talking especially about […]SHARETHIS.addEntry({ title: “Flex Data Services, Hibernate and Eclipse – Mike Slinn book”, url: “http://cornelcreanga.com/2009/10/flex-data-services-hibernate-and-eclipse-mike-slinn-book/” });

Tomcat and common loader

I spent twenty minutes last night trying to understand why the Tomcat delivered with the Livecycle Data Services installation works fine when the libraries for jotm are located in a subfolder of the common/lib. When I’ve installed a clean version of Tomcat and I copied the folder jotm into common/lib the classloader was not able […]SHARETHIS.addEntry({ title: “Tomcat and common loader”, url: “http://cornelcreanga.com/2009/09/tomcat-and-common-loader/” });

BlazeDS, AMF and read only properties

A common scenario when building domain objects is to have only read objects properties. The serialization algorithm from BlazeDS/LCDS does not know to serialize the read only properties – it needs both get and set methods (with one exception – the java.lang.Throwable class). So you have two options in this moment if you do not […]SHARETHIS.addEntry({ title: “BlazeDS, AMF and read only properties”, url: “http://cornelcreanga.com/2009/09/blazeds-amf-and-read-only-properties/” });

Job openings on Livecycle Data Services team

Livecycle Data Services team has three openings: computer scientist, senior computer scientist and principal computer scientist. If you want to work to a really cuttting edge product on a world class company and do you have the required knowledge/passion I encourage you to apply. You will have the chance to work with sharp people, and […]SHARETHIS.addEntry({ title: “Job openings on Livecycle Data Services team”, url: “http://cornelcreanga.com/2009/09/job-openings-on-livecycle-data-services-team/” });

Logging in BlazeDS and LCDS with Java Util

I created a small class to allow integration between the logging mechanism from BlazeDS and java.util.logging. As an example it’s useful if you plan to use BlazeDS or Livecycle Data Services inside Google App Engine – the former one uses java.util.logging.
In order to use it you should modify services-config.xml to use the newly created class […]SHARETHIS.addEntry({ title: “Logging in BlazeDS and LCDS with Java Util”, url: “http://cornelcreanga.com/2009/09/logging-in-blazeds-and-lcds-with-java-util/” });

Logging in BlazeDS and LCDS with Java Util

I created a small class in order to be able to allow integration between the logging mechanism from BlazeDS and java.util.logging. As an example it’s usefull if you plan to use BlazeDS or Livecycle Data Services inside Google App Engine – the former one uses java.util.logging.
In order to use it you should modify services-config.xml to […]SHARETHIS.addEntry({ title: “Logging in BlazeDS and LCDS with Java Util”, url: “http://cornelcreanga.com/2009/08/logging-in-blazeds-and-lcds-with-java-util/” });

HTTP Streaming and Gzip compression

Good observation by Michael Slinn – do not use HTTP compression when using HTTP Streaming channels – you will not be able to receive any messages from the server. If you want to understand better how HTTP Streaming works read this article.
SHARETHIS.addEntry({ title: “HTTP Streaming and Gzip compression”, url: “http://cornelcreanga.com/2009/08/http-streaming-and-gzip-compression/” });

Some internals related to Flex and remoting

When I started working with Livecycle Data Services and Java remoting I was afraid of doing too many remote calls at one time because of the network latency – if the network latency is 100ms and you do ten remote calls in order to fill a panel with data you will lose (10/maximum no of […]SHARETHIS.addEntry({ title: “Some internals related to Flex and remoting”, url: “http://cornelcreanga.com/2009/07/some-internals-related-to-flex-and-remoting/” });