The component actually has tens of assets (maybe over a hundred), that, in a vanilla HTML page get loaded from the JavaScript by creating a URL. When it was turned into a Tapestry page, the person doing the porting figured out a kludge so that the JavaScript could use the Tapestry URLs to get to the assets. The problem is 3.0.3 needs MD5 checksums to get at assets, so the kludge now fails.

I gather the way to deal with this is to rewrite the script so that all the assets are Tapestry-friendly and include ${ant-like-properties} in the JavaScript files. Unfortunately, the JavaScript file itself is quite a bit beyond me.

Thanks for the suggestions!
Todd

On Apr 8, 2005, at 6:50 AM, Andreas Andreou wrote:

In order to get the valid URL for an asset, one has to call
String imageURL = getMyAsset().buildURL(cycle);
so, he would need to pass the cycle object to the script as well.
Or, he could do all this in java code, then set the url string in a field of his page class and then (in the .html):


<span jwcid="@Script" script="..." asset1Url="ognl: asset1Url" asset2="ognl: asset2Url"/>


Kent Tong wrote:

Todd O'Bryan <toddobryan <at> mac.com> writes:


I'm more than willing to code assets for all the images, other scripts, etc., but how do I reference those assets from inside the JavaScript components?


I may not be understanding your question, why not pass the assets as symbols to the Script component like:

<span jwcid="@Script" script="..." asset1="ognl: assets.foo" asset2="ognl: assets.bar"/>




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to