It turns out dom.js was being cached. What makes this tricky to figure out is
requirejs apparently adds the script tags to the DOM which makes it appear
prototype.js is being added by Tapestry when in fact it's being included by
the cached dom.js.
I'm looking forward to checksums in asset paths.
Often, the JavaScript cached in the browser is the issue, not the HTML
markup.
On Mon, Jan 14, 2013 at 1:01 PM, trsvax wrote:
> I'll restest this when I get home but I'm pretty sure this is it. I did not
> believe it either so I tried a few times. Also I don't think it's a cache
> issue. The gen
I'll restest this when I get home but I'm pretty sure this is it. I did not
believe it either so I tried a few times. Also I don't think it's a cache
issue. The generated HTML changes
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/5-4-alpha-2-jQuery-support-solution-and
Must be a client side cache effect.
I have already had this kind of problem while doing the monkey between
differents tapestry version on a Tapestry5-jQuery demo application.
This option could be validated by clearing the browser cache or by
upgrade application version to 0.0.2-SNAPSHOT.
2013/1/14
I strongly suspect it is something else; Tapestry doesn't do anything with
the APPLICATION_VERSION but embed it into some URLs.
On Mon, Jan 14, 2013 at 5:33 AM, trsvax wrote:
> After removing most of the code from the project I found the line that
> causes
> prototype to be included. If I Symbo
After removing most of the code from the project I found the line that causes
prototype to be included. If I SymbolConstants.APPLICATION_VERSION contains
'-SNAPSHOT' I get prototype.
So this includes prototype and dom.js is the prototype version
public class AppModule
{
@Contribute(SymbolProvi
