See https://builds.apache.org/job/tapestry-trunk-freestyle/1009/
--
[...truncated 20963 lines...]
PageCatalog: org.apache.tapestry5.corelib.pages.PageCatalog
PropertyDisplayBlocks:
Howard, it is so selfish to assume that everyone's apps should have requests
processed in the sequential order. Only argument you have is that someone wants
it, if you are just going to ignore this issue it will show a bad leadership,
you are not the only one who is using Tapestry.
Use locking
Hi Denis
You have made your point and everybody agrees with you but your tone has not
been polite.
regards
Taha
On Jan 15, 2013, at 6:02 PM, Denis Stepanov wrote:
Howard, it is so selfish to assume that everyone's apps should have requests
processed in the sequential order. Only argument
Sorry, it looked like discussion is over and it will stay this way.
Denis
Jan 15, 2013 v 1:41 PM, Taha Siddiqi tawus.tapes...@gmail.com:
Hi Denis
You have made your point and everybody agrees with you but your tone has not
been polite.
regards
Taha
On Jan 15, 2013, at 6:02 PM,
Hi,
I spent some more time in profiling/debugging. I added caching for all
my OGNL bindings so that's no issue anymore. I add Cachring for tomcat's
WebappClassloader.findResource which was a big hotspot. I cut the link
between my 3 big pages so that only 1 page is loaded at once.
Loading
Locking in the session is a step back. With ajax enabled apps you want to
be able to get these requests to run concurrently. If you're storing your
login token in the session you've now degraded user perception of
performance by making the panels load synchronously.
I believe there could be a
On Tue, Jan 15, 2013 at 3:04 PM, Josh Canfield joshcanfi...@gmail.comwrote:
Locking in the session is a step back. With ajax enabled apps you want to
be able to get these requests to run concurrently. If you're storing your
login token in the session you've now degraded user perception of
I'll check into this; there's some special Gradle magic to setup the
project as 5.0 (not 6.0) compatible.
On Mon, Jan 14, 2013 at 4:33 AM, Ulrich Stärk u...@spielviel.de wrote:
Can you please all make sure that your IDE doesn't emit @Override
annotations on interface
implementations? It
It's still in transit; and yes, that was supposed to be
isLockedByCurrentThread() (or whatever that method name is).
On Tue, Jan 15, 2013 at 3:19 PM, Kalle Korhonen
kalle.o.korho...@gmail.comwrote:
On Tue, Jan 15, 2013 at 3:04 PM, Josh Canfield joshcanfi...@gmail.com
wrote:
Locking in the
