|
Let me first give you a quick overview on
how this works, then I’ll discuss how to diagnose it further. When the fill call is sent to the server,
it serializes the fill parameters from client to server. The server then
stores the fill parameters in a java representation. When that fill is
updated, an update collection message is sent to the client which contains the
fill parameters as well. Now these get converted to ActionScript objects
again. We then go through the existing fills on the client and call
ObjectUtil.compare to see if they are the same. This compares the class
name and if they match, it will do a property-by-property comparison. In your case, FDMS is likely not seeing “systemObject”
as being the same when it gets serialized to the server and comes back again. One
common problem is that managed objects can end up with a “uid”
property which gets set to a universally unique id by default on each instance.
When you serialize the object to the server and get it back again, the
uid property is not the same so the client thinks it was pushed an update
collection message for a different fill. This is probabl not your problem
but if systemObject is a strongly typed AS class which does not map to a Java
class, the type can be lost when going from client to server. When it
comes back again it will not match (you need to use [RemoteClass] either with
no argument as a signal to preserve the strong AS type or with an alias
argument that points to a corresponding Java class that has the same public
properties). These problems can be tricky to figure out
so I usually recommend that folks stick with primitive values in the fill
parameters. If you do need this to work, I recommend trying to send
systemObject to dummy Java method which just returns the argument passed and
see if the result compares against ObjectUtil.compare. You can probably
dig into it in the debugger to figure out why it is not comparing. I
think that if you initialize “uid” to a default value it will
override the auto-generating of the unique uid, but be careful if you use this
object in a DataGrid or other list based component as those components use the
uid to differentiate objects. I hope this helps. Jeff From: Hello everyone i have a bug when using the DataService
component. I am -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___ |
- RE: [flexcoders] Possible DataService BUG, can anyone hel... Jeff Vroom
- RE: [flexcoders] Possible DataService BUG, can anyon... Diego Miramontes
- [flexcoders] Re: Possible DataService BUG, can a... passive_thoughts
- Re: [flexcoders] Re: Possible DataService BU... Diego Miramontes

