Still no trace of this error and cannot seem to reproduce it.
I am pretty sure this was caused by using jQuery though - before replacing
the $ sign with the word jQuery.
http://docs.jquery.com/Using_jQuery_with_Other_Libraries
and, while I was messing around trying to fix the apparent
I think you might be having a name clash with a page name and a CSS file
name in the same folder and tapestry is thinking it's an event URL to the
page instead of a CSS path.
Solution: name the CSS file differently or move it to a different folder
On Tue, 24 Apr 2012 06:45:03 -0300, Lance Java lance.j...@googlemail.com
wrote:
I think you might be having a name clash with a page name and a CSS file
name in the same folder and tapestry is thinking it's an event URL to the
page instead of a CSS path.
Solution: name the CSS file
Most likely, your template has a relative path to it ... you've done:
link rel=stylesheet src=css/site.css/
That works great inside a static page, where you know exactly what the
browser URL is going to be.
In Tapestry, once you add page activation contexts, various folders,
and other mappings
Aha. Thanks, Howard. Makes sense. That is probably what was going on.
I am, however, using the context: in all my templates and corresponding
java classes, as intended.
And, for the life of me, I am unable to trap the issue any longer. The logs
seem to be free of it last time I checked
