On Thu, 12 Sep 2013 09:43:40 -0300, Barry Books <[email protected]> wrote:
If you have file a b and c. The page includes a which then includes b and c but in your case with a's checksum.
In my case, Tapestry can't know that file a included b and c, because a, which is JavaScript, dynamically included them in the page. It just knows b and c were requested with wrong checksums.
If Tapestry just returned b and c with a's checksum everything would work fine. The only problem would be if you change b or c without changing a. I agree this could be a problem but if you are using a library with releases I would say the odds of this happening are low and is easily fixed by just changing a.
Ville's solution does fix my problem, but it creates another: if you have a, b, c in the same folder and you change one of them, a, b, c will have their checksums changed. I don't think the odds of this happening are low. Just changing another file which didn't need to be changed just to keep Tapestry happy, I'm sorry, I think it's quite bad.
-- Thiago H. de Paula Figueiredo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
