Hey! Adobe! What's mx.data.utils.TraitsInfo ?

Today while doing normal work (meaning, not pv3d), I made a little typo combined with code completion, and suddenly I had a class name standing there with the name TraitsInfo, along with it’s import, mx.data.utils.TraitsInfo.
At that moment I didn’t have the time to have a good look at what was happening there, but I decided to revisit that tonight. I had a good look now, and although the class is unavailable, the code completion suggests that Adobe actually does have this class….

There’s a couple of errors and small bugs in Flex which reveal things about the Adobe dev environment, like the path from the building machine (something like c:\dev\…\…\, can’t reproduce right now).

This hint of a class which could us info about the Traits got me particularly excited though; I thought it was a reference to the AS3 Object Model. So if we would have more info on what actually happens with our classes in terms of what the Traits look like, this would give some good insights at runtime…seemed interesting to explore to me. But the package where this is in suggests it hasn’t got anything to do with AS3, but it refers to data services. Still these things get me very curious. If anyone of Adobe reads this (I hope the title advertisement worked), and wants to and can share, please do.

For people interested in the Traits; this is probably the best document on it.

This entry was posted in Flex. Bookmark the permalink.

4 Responses to Hey! Adobe! What's mx.data.utils.TraitsInfo ?

  1. Matt says:

    Hi, this class is used as part of the data services serialization logic. We sometimes do our own serialization instead of relying on direct translation by the Player so that we can work with proxies without sending those proxies over the wire, etc. The traits of a class are included in the AMF3 protocol and we use this internal class for storage. We are not getting traits info from the Player itself.

  2. Dirk Eismann says:

    Interesting. To learn more about the class, its inheritance and accessors etc. try the following

    trace(describeType(mx.data.utils.TraitsInfo));

    This gives you a pretty verbose XML structure with lots of metatdata about the inspected object.

  3. maliboo says:

    Interesting… What version of Flex Builder do you have? Mine is 2.0.155577 and I do not have this.

  4. @Matt :

    Matt, thank you for that info. That is kind of what I thought. But to be exact, this means you have got an AS version of AMF3 Serialisation/Deserialisation you use for debugging ?

    @Dirk : Unfortunatly, I don’t really have the class. It is just being autocompleted.

    @Maliboo : Latest hotfix version…

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Notify me of followup comments via e-mail. You can also subscribe without commenting.