RE: 'implements Serializable' versus 'extends ASOb ject'

I wrote an article on this, I map a java object to a flash object and
serialize them fine, of course you have to duplicate any behavior on both
sides, however I find it better to use the "transferred" objects purely as
value object and put the behavior in business objects.


I'm using openAMF with the Ariaware Arp framework (flash side) and weblogic
8.1 sp2 with EJB's and it all works very nicely

The article I wrote is here :

http://theresidentalien.typepad.com/ginormous/2005/08/openamf.html

Cheers,
Grant.


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Todd Hivnor
Sent: Monday, October 17, 2005 2:53 AM
To: [email protected]
Subject: [Openamf-user] 'implements Serializable' versus 'extends ASObject'

I'm working on a new application using OpenAMF. I  want to send objects 
from Java to Flash, and from Flash to Java. I hope to define the same 
class in both Java and Flash, such that Java can create the object, send 
it to Flash, and have Flash create an instance of it. The same should 
work in reverse. I want more than just an ASObject, I want full-on 
objects, with the methods available. Also, I want to be able to nest my 
objects.




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl