Yes, we ended up doing something like: * Introduce a command servlet * Rewrite rules changing the "nice" url to one with parameters that the servlet can parse (including which portal page to use) * Do checking and logic in the command servlet * Use HTTP getting directly inside the command servlet to the correct render url, targetting ctrl:page=Portal.Page with additional parameters * Introduce a portlet superclass that uses Policy to obtain the actual servlet request, and put that on the session so that each portlet on that page can access the information
Not the best of solutions, but no JBoss-specific classes used, and objective reached. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963490#3963490 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963490 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
