While doing this I came across a problem with re-using the MC metadata classes. Kabir appears to have found the same problem in the aop stuff and used the same hack that I have below. Some of the ValueAdapters are defined at the package/schema level rather than being associated with the type. So I have to redefine them in my schema otherwise I can't use the classes for xml parsing. This is incredibly brittle configuration. https://svn.jboss.org/repos/jbossas/projects/mc-script/trunk/src/main/jav... If somebody adds a new adapter, other users of the classes will break because they don't know about the new adapter. They probably won't use the new adapter but the construction of the SchemaBinding from the annotations will look at the class being adapted and complain. These adapters should be on their respective types. The only reason to define them on the schema is when you can't change the type. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235288#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...