Jan Normann Nielsen skrev:
Hi
I'm currently writing a Tapestry web application using Tapestry 4.0.2
under Tomcat 5.5.18 and JDK 1.5.0_08.
[bla-bla - snip]
I this is not a lot of information to go by, but my application is
quite big and this is what I have narrowed the problem down to. I have
a feeling that this might be some sort of concurrency issue within
Tapestry, mostly because each of the iframes render fine on their own,
and I am almost sure there were no errors at the time we used XML
files for page/component specs.
Does anyone have an idea what the problem is and what I do work around
it? It's really a show-stopper for me.
Best wishes,
Jan Nielsen
I probably should have Googled for my problem before posting to this
list, anyway I've found out what the problem is: It's issue 848 and by
not running with disable-caching on seemed to fix the problem.
Anyway, having to reload the application on every change slows down
development speed, so it would be nice if anyone had a better solution.
Are there any plans to work on this issue?
Best wishes,
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
