@ Eric - I saw that you were testing on an ancient installation of
ESME [1].  Our test system is running on the Stax.net [2]  this has
our most recent code-drop.

D.

[1] http://www.esme.us/esme/
[2] http://esmecloudserverapache.dickhirsch.staxapps.net/

On Fri, Jan 14, 2011 at 8:49 AM, Richard Hirsch <[email protected]> wrote:
> On Thu, Jan 13, 2011 at 11:40 PM, ejc <[email protected]> wrote:
>> I wanted to run this past the list before submitting a bug.  I guess I've 
>> been
>> following the Lift list too long :-)
>
> We still have a long way to go before matching the activity on the
> lift list ( ;->).   Feel free to submit a bug report to Jira [1]
>
>>
>> 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.
>>
>> I'm wondering exactly how lift merges <head> elements since the
>> scripts/<filename>
>> in index.html should be different from
>> ../scripts/<filename>
>> right?
>>
>> Anyway, a patch is attached.
>
> The Apache mailing lists don't allow attachments. I've created a Jira
> item [2] - can you submit your patch there?
>
> Thanks
>
> D.
>
>>
>> Thanks,
>> Eric
>>
>
> [1] https://issues.apache.org/jira/browse/esme
> [2] https://issues.apache.org/jira/browse/ESME-322
>

Reply via email to