Not easy question... I ll try an answer. on the same way as you did : - look at the chain of interceptor (interceptor stack), in the jmx service descriptor that define it - look at the interceptor that are after the pageInterceptor, and customise "all that" so you can still invokeNext, but skip what you don't want - keep the interceptor that are vital for the portal. may be rearrange them. not sure it will work. may be a lot to do, as you touch the core engine of the portal.
other way : I would do it at the url/command level when an url is requested, the portal decode it and build a command, that will be executed (ie call the proper page, call the portlet which is called by the url, etc...). there, you may be able change the url state, so it is considered as a secured one. or even build a new type of command, that will do what you want. other way : using a servlet filter ? in front of the main serlvet(s) of the portal, change/rewrite the url so the portal see it as a secured one. look at the portal-server war for that. there are for servlet (two not secured, two secured). should be the best way, as it does not touch the portal processing. just make it see what you want it to see. hope this can help... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072438#4072438 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072438 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
