So heres my take on it, and I may be oversimplifying it: Here is a standard portal url: http://localhost:8080/portal/auth/index.html?ctrl:id=window.default.PermissionPortletWindow&ctrl:type=windowstate&ctrl:windowstate=maximized
On the admin screen with the PermissionPortlet maximized. URL Components: Context = portal PortletWindow = PermissionPortletWindow Action type = windowstate windowstate = maximized So, can we do something like this? http://localhost:8080/[context]/[portletwindow]/[actiontype]/[windowstate]/ Then we just parse things out like we have now and have the portal interpret this parameter-less url. The only thing that throws a wrench in the works is what to do about the cmsportlet: "/foo/bar/goo.html" Unless you append those at the end of the path, perhaps? Using this scheme, we already can figure out that $1 = context $2 = portletwindow $3 = actiontype $4 = windowstate $5 = cms item ? This is what I do on my personal sites with url-rewriting. I use regexes like this to parse things out and rebuild the url and pass it on a local script for execution. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872790#3872790 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872790 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
