"alesj" wrote : "david.lloyd(a)jboss.com" wrote : | | Well in any case, the metadata has to be the first step. From there, the parser and the converter (to jboss cl) could be developed simultaneously. | | | The metadata is already there: | - http://anonsvn.jboss.org/repos/jbossas/projects/jboss-osgi/trunk/osgi-int... | - http://anonsvn.jboss.org/repos/jbossas/projects/jboss-osgi/trunk/osgi-int... Hmm. This looks more like a thin wrapper around an attribute map. What's the benefit to wrapping attributes like this? Seems kind of hacky/ugly. It would be better to just have an opaque pojo with regular (stringly typed) bean properties (including setters) for the attributes and leave it up to the parser to parse the manifest file and its entry values. Metadata is just metadata - there really shouldn't be any logic in there in my opinion. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203707#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...