I'm working on it. The first step was to take care of the deployment, I think that is taken care of now. JBossPortal has it's own way of request interception which is not how war files usually works. My implementation is that then a war is deployed with a *-object.xml which doesn't refer to a parent id, a new context is created which binds to the virtual-host and context path specified by the war. That way both the old JBossPortal way and the usual way a war works can be supported without any hassles. Now I'm following the request flow to work out all the issues that is caused by a slightly different model. Supprisingly few so far but it's a bit complex to follow. For example I was struggeling a lot with an issue in the security interceptor which I haven't figured out yet but I have seen it happen also on a unmodified JBossPortal that suddenly it's not possible to do unchecked accesses and the only solution is to restart the app server. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970162#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...