Last push for Engage.
Antranig.Basman at colorado.edu
Fri Oct 16 07:07:31 UTC 2009
The issue here is that the mount directive for engageDemo is incorrect.
Actually it is not "working" in Eclipse because the paths are actually
wrong - it is just that the browser refuses to honour the path "../.."
starting only at depth 1 and so "luckily" the references resolve. When
run standalone, the depth relative to the server is 2, and so the effect
of the incorrect URLs becomes visible.
Since this is one of the cases where the original path was "never
correct" it is necessary to use the "rewriteSource" option as for the
other two mount directives. In this case, the correct mount is
as soon as we release, we will probably change this behaviour since the
requirement to base "rewriteSource" to the same relative directory level
as "source" is quite unintuitive, it would probably be much more
readable to say that in the case "rewriteSource" is required that we
simply have it match the literal prefix in the file, so for this case
this would become "../../engageDemo".
I have committed this to trunk, along with a version of engageApp.js
that has better diagnostics to help with understanding the mount
Yura Zenevich wrote:
> Hi everyone,
> I just wanted to mention the last thing that we are trying to finish
> before the engage is frozen. We added the index.html page (located in
> kettle/src/webapp/engageDemo/html) as a start page for kettle + engage
> demonstration. The initial issue that we had with that page was that we
> had URLs to artifacts browse and view that contained "&" which was not
> appropriate and caused problems in kettle. For that we had to add
> index.js file that would go through the list of links and replace
> escaped ampersands and with actual "&" to make our hrefs work with view
> and browse. Engage demo in current stage works in eclipse however when
> trying to load index.html from build war the files included in that
> index.html are not mounted and hence, not found. However the directorial
> structure doesn't change for engageDemo and the paths don't need to be
> rewritten. We appriciate, If you have any suggestions.
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
More information about the fluid-work