[
https://issues.apache.org/jira/browse/ESME-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric J. Christeson updated ESME-322:
------------------------------------
Attachment: esme.patch
Here is the patch I generated. It tested it both running from sbt (context
root /) and tomcat (context root /esme)
> Some Scripts aren't loaded on tomcat
> ------------------------------------
>
> Key: ESME-322
> URL: https://issues.apache.org/jira/browse/ESME-322
> Project: ESME
> Issue Type: Bug
> Components: UI
> Affects Versions: 1.2
> Reporter: Dick Hirsch
> Fix For: 1.2
>
> Attachments: esme.patch
>
>
> From the dev mailing list
> I checked out the latest ESME and built a package (I love the sbt
> integration!).
> Deployed on tomcat to discover that display_single_message.js and pretty.js
> did not load. I have a context path of /esme and both files were
> being looked for
> in /scripts instead of /esme/scripts. I found that index.html had this:
> <script src="scripts/display_single_message.js" type="text/javascript"/>
> <script src="scripts/pretty.js" type="text/javascript"/>
> but every other occurrence had this:
> <script src="../scripts/display_single_message.js" type="text/javascript"/>
> <script src="../scripts/pretty.js" type="text/javascript"/>
> The error didn't occur when running under jetty from sbt since the context
> root
> is /
> The fix was to change to this:
> <script src="/scripts/display_single_message.js" type="text/javascript"/>
> <script src="/scripts/pretty.js" type="text/javascript"/>
> everywhere (except index.html) since they are loaded in the user page which
> is one level down.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
