According to the documentation, this constant Indicates this update collection message was client generatedand the remote destination determined that it should be reverted onthat client. A subsequent update collection message will followcontaining the correct values to apply getting the clientcollec...

Hello,I'm trying to implement a feature that allows users to freelyre-arrange items into a managed collection, using Drag and Drop. I'm using aTileList object, which already has built-in support for Drag andDrop, provided by Flex.A FDS destination (implemented by a Java class) is used tofill the col...

You are lucky with your 5 minutes. I just tried with myenvironment (LCDS is deployed on Tomcat 5.5), keeping all thedefault settings, killed my browser after connecting (I do haveboth HTTP and RTMP connections created), and noticed the following: - the RTMP session was instantly invalidated - the HT...

Thanks, so as a recap, the following calls need to be done inthis case, in this order:ds.release(); // to release everything that's managed by thisserviceds.disconnect(); // to disconnect the RTMP link to the serverds.logout(); // to logout the destination for all the dsinstances used by this client...

Yes, on Logout all the server resources (including themanaged data) need to be released/cleared. So for instance, theArrayCollection object used to be filled with managed data needs tobe emptied. I noticed explicitly calling removeAll() for thiscollection after disconnecting the data service won't w...

quote:Originally posted by: aBillI just checked what the invalidate() method. It calls thesession destroyListener first before it remove all attributes. Thismight be the problemWilliam ChanThanks William. Clearly a bug.

William,I tried this early in the morning (disconnecting theDataService from the Flex client, using the disconnect()ActionScript call), and it worked, as you predicted. Thanks for thetip. Still I don't know what the client-side implications are withthe managed data, should I also do something specif...

Yes, if I programatically remove the attribute, the"valueUnbound()" method gets called by the framework. But I wouldexpect the same when the HttpFlexSession objects gets invalidatedby calling its "invalidate()" method (or when it times out).I thought these FDS session wrappers work the same as javax...

Here,s the log:[Flex] 10:39:47.328 [DEBUG] [Endpoint.FlexSession]FlexSession created with id '0DB83653B7561285669BB5DC0ABF18E7' foran Http-based client connection.[Flex] 10:40:03.484 [DEBUG] [Endpoint.FlexSession]FlexSession created with id '759CCC2F-DC0D-C199-21BD-7871C6175538'for a direct RTMP cli...

Thanks... really? But in a classic J2EE scenario you don'tneed to register the HttpSessionBindingListener implementations...and the framework calls their "valueBound" and "valueUnbound"methods whenever it is appropriate.http://tomcat.apache.org/tomcat-5.5-doc/servletapi/index.htmlBack to Flex/FDS ca...