Comments on: Flex / AIR Serialization Lessons Learned http://www.brooksandrus.com/blog/2008/03/25/flex-air-serialization-lessons-learned/ This is the blog of Brooks Andrus. Here, at irregular intervals, you may find digital noise centered around the activities of an early 21st century technologist. I work for TechSmith Corporation, but this web space and the views found on it are entirely my own. Wed, 23 Jul 2008 21:20:37 +0000 http://wordpress.org/?v=2.6 By: AndyChou http://www.brooksandrus.com/blog/2008/03/25/flex-air-serialization-lessons-learned/#comment-43657 AndyChou Fri, 18 Apr 2008 01:43:30 +0000 http://www.brooksandrus.com/blog/2008/03/25/flex-air-serialization-lessons-learned/#comment-43657 Need 3 Flex engineers in New York City: 1. You have to be living in New York City for now. 2. Work part time or full time with us. 3. Good at Adobe Flex technology. 4. Please contact us for other requirement and details. Busycode Inc. is a top Adobe Flex shop who develops Flex/AIR applications for clients. For more info, please visit http://www.busycode.com Need 3 Flex engineers in New York City:
1. You have to be living in New York City for now.
2. Work part time or full time with us.
3. Good at Adobe Flex technology.
4. Please contact us for other requirement and details.

Busycode Inc. is a top Adobe Flex shop who develops Flex/AIR applications for clients.
For more info, please visit http://www.busycode.com

]]> By: Sean http://www.brooksandrus.com/blog/2008/03/25/flex-air-serialization-lessons-learned/#comment-43024 Sean Fri, 04 Apr 2008 06:05:18 +0000 http://www.brooksandrus.com/blog/2008/03/25/flex-air-serialization-lessons-learned/#comment-43024 Just use null defaults to get around constructor argument problems, we do this all the time. public function AuthToken(token:String=null, perms:String=null, etc...){ } Just use null defaults to get around constructor argument problems, we do this all the time.

public function AuthToken(token:String=null, perms:String=null, etc…){
}

]]> By: Jamie Bisotti http://www.brooksandrus.com/blog/2008/03/25/flex-air-serialization-lessons-learned/#comment-42455 Jamie Bisotti Fri, 28 Mar 2008 14:36:32 +0000 http://www.brooksandrus.com/blog/2008/03/25/flex-air-serialization-lessons-learned/#comment-42455 We are currently using Granite Data Services (GDS) instead of BlazeDS (we were using it before BlazeDS was open-sourced); it provides a bit more flexibility when it comes to serialization. For example, it's Externalizer's provide an additional method, newInstance(...). We override this instead of readExternal(...) which allows us to use immutable objects (i.e. no setters; no default no-arg constructor). We haven' had any problems with it so far. Might be worth a look. Jamie We are currently using Granite Data Services (GDS) instead of BlazeDS (we were using it before BlazeDS was open-sourced); it provides a bit more flexibility when it comes to serialization. For example, it’s Externalizer’s provide an additional method, newInstance(…). We override this instead of readExternal(…) which allows us to use immutable objects (i.e. no setters; no default no-arg constructor). We haven’ had any problems with it so far.

Might be worth a look.

Jamie

]]> By: James Law http://www.brooksandrus.com/blog/2008/03/25/flex-air-serialization-lessons-learned/#comment-42400 James Law Thu, 27 Mar 2008 19:47:49 +0000 http://www.brooksandrus.com/blog/2008/03/25/flex-air-serialization-lessons-learned/#comment-42400 Thanks! Using Blaze DS it seems to require on the JAVA side, that objects have public setter methods for properties. This doesn't make sense to me but it seems so... JL Thanks!
Using Blaze DS it seems to require on the JAVA side, that objects have public setter methods for properties. This doesn’t make sense to me but it seems so…

JL

]]> By: Paul Gregoire http://www.brooksandrus.com/blog/2008/03/25/flex-air-serialization-lessons-learned/#comment-42266 Paul Gregoire Tue, 25 Mar 2008 15:33:00 +0000 http://www.brooksandrus.com/blog/2008/03/25/flex-air-serialization-lessons-learned/#comment-42266 Great article, I lost a lot of blood learning these things on my own :) but I would like to pass on another tidbit to add to your post. When your AS packages do not match your java classes you have to register the alias in addition to adding the meta data described above. The scenario is this: AS3 class name: com.example.as.Widget Java class name: com.example.java.Widget Put this line somewhere in your startup class after importing your Widget flash.net.registerClassAlias("com.example.java.Widget", Widget); Everything should work from this point on, but as a best practice make sure your packages match!! Great article, I lost a lot of blood learning these things on my own :) but I would like to pass on another tidbit to add to your post. When your AS packages do not match your java classes you have to register the alias in addition to adding the meta data described above. The scenario is this:
AS3 class name: com.example.as.Widget
Java class name: com.example.java.Widget

Put this line somewhere in your startup class after importing your Widget

flash.net.registerClassAlias(”com.example.java.Widget”, Widget);

Everything should work from this point on, but as a best practice make sure your packages match!!

]]>