jeffvroom

Your achievements

0% to

Tip / to gain points, level up, and earn exciting badges like the new

Community profile jeffvroom Level 1

Job title here

Location here

4 BADGES

Learn more

Joined the community 06-02-2008 8:47:27 AM

Offline

View leaderboards

Profile

Trophy case

Top badges earned by jeffvroom

Give Back 5

Give Back 3

Give Back

Affirm 1

Re: debugging an LCDS problem - Adobe LiveCycle

Geez, not my day. Apparently the managed code gen does this: private var _115792uid:String; [Transient] [Bindable(event="propertyChange")] public function get uid():String { if (_115792uid == null) { _115792uid = mx.utils.UIDUtil.createUID(); } return _115792uid; }so it will get set to a UUID as soon as you try to get it ifyou use the getter. We will always set it before getting it thoughso we'd (hopefully!) avoid that extra UID. If you can find that_xxxuid member variable you could look at that...

Re: debugging an LCDS problem - Adobe LiveCycle

Oh, I should have mentioned that method does not work for"newly created" items. You have to have an id assigned to look itup by id. For newly created items, in the debugger if you show allvariables (including those not accessible in the current context)you should see the variabled called "uid" in your managed instance.That gets assigned when the object is managed. for a newly createdobject, it will be a "UUID" - i.e. a string with lots of hexdigits. That corresponds to the messageId of the "crea...

Re: debugging an LCDS problem - Adobe LiveCycle

Here's the ASDOC: /** * Looks up the supplied item with the given identity. If theitem is already * managed on this client, the managed instance is returned.If not, null is * returned. Unlike the getItem call, this call does not makea request to the * server and does not add an additional reference to theitem. * * @param An Object that contains the identity properties forthe desired object. * @return The managed object or null if the item with thisid is not yet managed * on this client. * Basica...

Re: debugging an LCDS problem - Adobe LiveCycle

LCDS should only be listening for events for the managedinstances. There are a few ways you can check. there is a"getLocalItem" method which can retrieve the managed instance for aparticular id. Inside of the item itself, there is amx_internal::uid property which gets set for "the" managed object.The is also pretty useful for seeing whathas happened in the system up until that point. In general, a newly created PositionVO would not be managedby anything you get out of or put into that "list" ar...

Re: order of fill results? - Adobe LiveCycle

Calls executed in the same "flash frame" (i.e. in the sameexecution path) are guaranteed to be processed in the same order onthe server no matter what channel you are using. RTMP provides anorder guarantee in general since everything gets queued up in theorder in which they are executed and put into the socket in thatorder and then processed synchronously (one at a time) on theserver. There is a small risk of getting out of order calls whenyou are using HTTP based channels and you make the calls...

Re: is data passed back to responder a read-only copy? - Adobe LiveCycle

I think that this is a bug... I think that today theresponder's token is receiving the raw array of objects receivedfrom the server. It should be given the same object - i.e. the"myModel" object -- in the result event. I'll make sure a fix getsinto the next release. In the meantime, a workaround would be todo: token.myResult = myModeljust after the fill call... then use "myResult" instead oftoken.result.

101

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe