Hi Christos, this is interesting. We are planning to provide a REST interface for ProfileService in future as well, but haven't started on that. In your TODO list i read that you have problems starting a stopped component. I remember that we had to do some work there as well, but i'm not sure if this fix made it into 5.1.0.GA. It is fixed in the 5_x branch and in the upcoming 5.2.0.Beta1 release though - this might be related. Briefly looking into your application i noticed that you have a implementation for some of our known Components. I think a more generic mapping between ManagedObjects/Components with their ManagedProperties to xml would be good. This would be needed to allow multiple management clients to reuse the same REST api without further interpretation of the exposed information. In general this mapping should be quite easy and you would be able to handle everything ProfileService exposes. Of course depending on your needs you might want to provide some specific implementations for certain ComponentTypes to simplify the usage. If you are interested in that you can look at some similar code i wrote creating a xml representation of the MetaValues: http://anonsvn.jboss.org/repos/jbossas/branches/Branch_5_x/system/src/mai... for the MetaValue JAXB model. and http://anonsvn.jboss.org/repos/jbossas/branches/Branch_5_x/system/src/mai... as well as http://anonsvn.jboss.org/repos/jbossas/branches/Branch_5_x/system/src/mai... for the transformation. This was written for a different purpose so a few more properties about Components would be definitely needed. Still it should give you a starting point in case you want to look at that. Thanks, Emanuel View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260457#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...