[
https://issues.apache.org/jira/browse/WW-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772743#comment-16772743
]
Yasser Zamani commented on WW-5021:
-----------------------------------
I think your mentioned issue doesn't mean Struts should add the "{{Serve static
resources from different namespace}}"'s feature. Struts already must resolve
static resources from current context path. i.e. in your example, if your app
is on {{/test}}, then Struts must resolve {{<@s.url value="/struts/domTT.js"
includeParams="none" encode="false" />}} to {{/test/struts/domTT.js}} (i.e.
regarding and honoring current context path). *Doesn't it?* if no, then I think
it looks like a bug.
> Serve static resources from different namespace
> -----------------------------------------------
>
> Key: WW-5021
> URL: https://issues.apache.org/jira/browse/WW-5021
> 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
(v7.6.3#76005)
