I've realized that wicket will only render one page at a time, at least it
will not run the constructor and onAttach methods of 2 pages at the same
time. This is a major bottle neck on applications with large user bases.
My app is experiencing problems because database calls are being run in
these constructors and onAttach methods. While there maybe a more
appropriate place for database calls to be run, and I'd like to hear where
these should be, running only 1 page constructor at a time doesn't seem to
be efficient. I've found the code that does this. RequestCycle.874
processEventsAndRespond(){
// Use any synchronization lock provided by the target 874 Object
lock = getRequestTarget().getLock(this); 875 if (lock != null) 876
{ 877 synchronized (lock) 878
{ 879
doProcessEventsAndRespond(processor); 880
} 881 }
can someone explain if this behavior is intentional, is there a way to stop
it? As a result of this behavior while a page is loading, no other page
will load until the first has finish.
I am using wicket 1.2
Scott
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
