This has been addressed in trunk for 3.1 which is why it requires
Servlet 2.5 so the portal can determine its context path at runtime.
Also when publishing a portlet in the trunk there is a framework portlet
toggle to tell the portal it should use its current context path as the
root.
I'm not
Hi,
I noticed that the Fragment Administration portlets hard code the
portletApplicationId to /uPortal. If you change the docbase for the uPortal
distribution it will break these portlets. This problem will occur for all
included framework portlets in the future.
It may be necessary to add a prop
