Comments on: Swiz 1.0 – Reflection API and Custom Metadata Processors

By: odoenet » Blog Archive » Custom GeocodeProcessor with Swiz

odoenet » Blog Archive » Custom GeocodeProcessor with Swiz — Wed, 31 Mar 2010 20:01:43 +0000

[...] is the ability to create custom metadata processors. To get more familiar with the idea, check this docs page. Note that some items from the docs has changed, such as you no longer extend MetadataProcessor, [...]

By: benclinkinbeard

benclinkinbeard — Mon, 01 Feb 2010 13:41:26 +0000

Hi Sharedtut,

Please use the list at http://groups.google.com/group/swiz-framework for implementation help. Be aware though, you will have to provide more information than you have here in order to be helped. Providing sample code is usually the best way for us to figure out where you might be getting tripped up.

Thanks,
Ben

By: Sharedtut

Sharedtut — Mon, 01 Feb 2010 05:07:04 +0000

I am testing this but not having any luck.

By: benclinkinbeard

benclinkinbeard — Tue, 12 Jan 2010 17:23:19 +0000

Hi Florent,

I assume you are using Flex 4? Shortly after this post we discovered that Flex 4 adds metadata to every property and method of every class when compiling debug builds. We have updated the code on GitHub to ignore that metadata (by ignoring any metadata tags that start with an underscore) to fix this problem. We have not released a new build yet, but if you pull the code down yourself you should see the errors go away.

Thanks,
Ben

By: Florent Cailhol

Florent Cailhol — Tue, 12 Jan 2010 15:48:14 +0000

Great stuff but TypeDescriptor seems to be buggy! If a method called toString() has any metadata, metadataHosts[metadataHostName] will fail (line 98). I made an ugly workaround:

if (metadataHostName == “toString”) {
return new MetadataHostFactory().getMetadataHost( hostNode );
}

By: John Griffin

John Griffin — Tue, 15 Dec 2009 14:36:41 +0000

Thanks for this Ben. Being a Java programmer and now working with Flex I know what the addition of annotations (custom metadata tags) to Java5 did for the Java community. I expect this new addition to Flex to accomplish the same level additional functionality for the Flex community. This starts a whole new ballgame!