Skip to content

refactor: path-swap to /resource-server/ + drop resource-server-content overlay#277

Merged
bjagg merged 2 commits into
uPortal-Project:masterfrom
bjagg:chore/resource-server-consolidation
May 8, 2026
Merged

refactor: path-swap to /resource-server/ + drop resource-server-content overlay#277
bjagg merged 2 commits into
uPortal-Project:masterfrom
bjagg:chore/resource-server-consolidation

Conversation

@bjagg
Copy link
Copy Markdown
Member

@bjagg bjagg commented May 7, 2026

Summary

Two commits, both part of the broader resource-server consolidation:

  1. 45f30c2 (prior) — path-swap legacy /ResourceServingWebapp/ to /resource-server/ across JSPs and Spring portlet config.
  2. 8197bc2 (new) — drop the resource-server-content WAR overlay (dep + maven-war-plugin extract). The overlay was unpacking lodash 4.17.4 (4 CVEs), underscore, backbone, modernizr, normalize, and jquery-plugins into the WAR for nothing, plus an explicit extract of jquery 1.11.0/1.12.2, jqueryui 1.8.24, and 3 famfamfam silk PNGs.

Why this is safe

  • gateway.jsp and gatewayEdit.jsp consume the famfamfam PNGs via <rs:resourceURL value="/rs/famfamfam/..."/>. The rs:* taglib does cross-context lookup against the resource-server context (uPortal-start's resource-server-content overlay still serves these). Local WAR copies were fallbacks the taglib never emitted.
  • gatewayNewPage.jsp references /resource-server/webjars/jquery/dist/jquery.min.js directly — modern path, served by uPortal-start's resource-server overlay.
  • grep -rEn '/WebproxyPortlet/rs/' src/ returns no matches.

Test plan

  • mvn clean install -DskipTests builds (verified locally on Java 11)
  • WAR has no rs/ directory (verified)
  • Smoke: /p/gateway/?pCm=view and ?pCm=edit render with the icon thumbnails intact (icons resolve via uPortal-start's /resource-server/rs/famfamfam/...).

Future cleanup

When uPortal-start drops resource-server-content, the JSP <rs:resourceURL> famfamfam refs need a swap (webjar or portlet-local checkout). Not in this PR's scope.

…urce-server/

Problem: gateway-sso-portlet.xml and the gateway docs referenced tango
icon paths under /ResourceServingWebapp/, the legacy resource-server
context that uPortal-start is in the process of retiring.

Goal: align with the modern /resource-server/ context so this portlet's
icons keep resolving once the legacy overlay is dropped.

Changes:
- src/main/webapp/WEB-INF/context/portlet/gateway-sso-portlet.xml:
  swap two p:iconUrl values from /ResourceServingWebapp/rs/tango/...
  to /resource-server/rs/tango/...
- docs/gateway_config.md: update three example iconUrl values to the
  same modern context.

Notes: the underlying tango/0.8.90 icon set ships at byte-identical
paths in the modern resource-server-webapp:1.5.x overlay. Tango is a
2009-era PNG icon set and is queued for replacement (FontAwesome
glyphs or modern icon webjar) as a separate frontend modernization
effort.
… dead libs)

Problem: WebproxyPortlet declared a runtime <dependency> on the
resource-server-content WAR overlay plus a maven-war-plugin <overlay>
config that pulled in rs/jquery/1.11.0/, rs/jquery/1.12.2/,
rs/jqueryui/1.8.24/, and 3 famfamfam silk PNGs. The overlay also
unpacked the entire rs/* tree of legacy libraries (lodash 4.17.4
with 4 known CVEs, underscore, backbone, modernizr, normalize, plus
jquery-plugins) into the WAR for nothing — none of which any source
file references after 45f30c2 path-swapped the legacy
/ResourceServingWebapp/ context to /resource-server/.

Goal: drop the entire overlay (dep + maven-war-plugin extract).
JSPs that consume the famfamfam PNGs (gateway.jsp, gatewayEdit.jsp)
use <rs:resourceURL value="/rs/famfamfam/..."/>, which the rs:*
taglib resolves via cross-context lookup against the resource server
context deployed elsewhere (uPortal-start's resource-server-content
overlay). The local WAR copies were fallbacks the taglib never
emitted.

Changes:
- pom.xml: drop the runtime <dependency> on resource-server-content;
  drop the maven-war-plugin <overlay> config that extracted jquery,
  jqueryui, and the 3 famfamfam PNGs. resource-server-utils (type=jar;
  provides the rs:* taglibs the JSPs use) is unchanged.

Notes: paired with 45f30c2 which did the source-side path swap to
/resource-server/. When uPortal-start retires resource-server-content
(broader fleet effort), the rs:resourceURL famfamfam refs will need
either a webjar swap or a portlet-local PNG checkout — out of scope
here.
@bjagg bjagg changed the title refactor(webproxy): path-swap legacy /ResourceServingWebapp/ -> /resource-server/ refactor: path-swap to /resource-server/ + drop resource-server-content overlay May 8, 2026
@bjagg bjagg merged commit 9ecda2f into uPortal-Project:master May 8, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants