It does so by design (a much requested feature that was added in Flex 1.0), but in order for you to skip the Java Bean like deserialization, you could do the following:
1. Don't send type information using the _remoteClass property (I've never been a fan of this method of object typing) 2. Don't register the AS class using Object.registerClass Without these two bits of information, it should be treated like a normal java.util.Map. With this map, you could do your own bean setter logic. -----Original Message----- From: wcucsd [mailto:[EMAIL PROTECTED] Sent: Thursday, March 03, 2005 3:25 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Remote Object architectural question Flexcoders, I have 2 Java classes: bean and service. The service class has a save method that takes a bean so it knows what to save. I want to use the Flex RemoteObject data service to call the service's save method and pass it a bean. When I do that, Flex appears to be calling all of the setXXX(arg) methods on the bean, whether I want it to or not. Is this how the Remote Object data service was designed? If so, is there any way of breaking that and forcing (or "allowing") Flex to only call certain setXXX(arg) methods on the bean? Thanks, -Will Yahoo! Groups Links
