struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yasser Zamani (JIRA)" <>
Subject [jira] [Commented] (WW-5021) Serve static resources from different namespace
Date Fri, 22 Feb 2019 16:02:00 GMT


Yasser Zamani commented on WW-5021:

Sorry I didn't get it again. I say, at end, it's clear who has generated the static resource
request - if it's {{/struts/domTT.js}} then requester is root app. If it's {{/someApp/struts/domTT.js}}
then requester is {{someApp}} app. So you simply can manipulate your load balancer to route
them correctly to requester app, right?

But if you have divided your apps using Struts packages's namespace i.e. you expect root application
to generate {{/someNamespace/struts/domTT.js}} when underlying action is defined in a package
with namespace {{someNamespace}} ({{someNamespace}} here is one of your apps mapped to root
namespaces) then I think it is very specific not general your need that couldn't being added,
and in my opinion is resolvable via a modification to your design i.e. manipulate your load-balancer
to route all of them (/struts/....) to root app.

> Serve static resources from different namespace
> -----------------------------------------------
>                 Key: WW-5021
>                 URL:
>             Project: Struts 2
>          Issue Type: Task
>    Affects Versions: 2.5.20
>            Reporter: k918912
>            Assignee: Lukasz Lenart
>            Priority: Major
>             Fix For: 2.6
> Is it somehow possible to serve the static Struts files from a different path?
> Currently domTT.js is loaded via /struts, but in my environment I would like to serve
it via /test/struts for example. Is there any configuration I'm missing or is this currently
not possible?

This message was sent by Atlassian JIRA

View raw message