Discussion:
${pageContext.request.contextPath} in javascript files
Michael Aemisegger
2005-07-19 12:46:01 UTC
Permalink
Dear List

I've built magnolia 2.1 from trunk and it's working fine. I then built magnolia
using my custom build process and am facing a problem with a technology I
haven't encountered yet.

There are parameters in javascript files that do not get translated. I guess,
when delivering the javascript file tomcat is supposed to replace those
expressions with their corresponding values.

How would this expression processing be triggered? Am I on the wrong path?

--
Cheers,
Michael

----------------------------------------------------------------
Philipp Bracher
2005-07-19 13:13:58 UTC
Permalink
Those javascript files are included into the
admintemplates/js/admincentral.jsp where the jstl parameters get
replaced.

This parameters a not something special in this case. If you call
admintemplates/js/admincentral.jsp in the browser you should get a
translated javascript.

Philipp
Post by Michael Aemisegger
Dear List
I've built magnolia 2.1 from trunk and it's working fine. I then built
magnolia using my custom build process and am facing a problem with a
technology I haven't encountered yet.
There are parameters in javascript files that do not get translated. I
guess, when delivering the javascript file tomcat is supposed to
replace those expressions with their corresponding values.
How would this expression processing be triggered? Am I on the wrong
path?
--
Cheers,
Michael
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------

Loading...