Re: [uportal-dev] UP-2237 - Framework Portlets initial data import should respect uportal.docbase

[Eric Dalquist]

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 sure what a good solution for 3.0.x will be though.

-Eric

Dustin S. wrote:

Hi,





http://www.ja-sig.org/issues/browse/UP-2237

Dustin.
--

You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
eric.dalqu...@doit.wisc.edu
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

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 property explicitly for this filter replacement since a docbase of ROOT implies / not /ROOT in Tomcat and there may be similiar idiosyncrosies with other containers.

smime.p7s
Description: S/MIME Cryptographic Signature