I used the onBeforeRender/onRender methods and was able to implement the
desired feature using Callable and Future objects from the
java.concurrent API.
Thanks a lot.
Seb
Igor Vaynberg wrote:
if you want the page to render all at once you have to spin off as
many threads as there are
Hi Sebastian,
If you intend to use Wicket's default detachable models to get data from
those services, they will be called sequentially. So those are out. I
see 2 options:
- In the panel constructor get the data in parallel threads through
standard java 5 constructs (dump all your
in a ExecutorService
and when that is done call get() on the returned Futures...
Regards,
Erik.
--
View this message in context:
http://www.nabble.com/Asynchronous-Components-tp18598968p18607531.html
Sent from the Wicket - User mailing list archive at Nabble.com
/Asynchronous-Components-tp18598968p18607531.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Become a Wicket
if you want the page to render all at once you have to spin off as
many threads as there are components and block rendering until all
threads are done. you can do this in page#onbeforerender() which is
called before any components start to render.
the problem with this is that if it takes a while
you may also consider using a portal framework and portlets, for example
apache jetspeed portal (and possibly others) has parallel portlet
rendering option..
Igor Vaynberg wrote:
if you want the page to render all at once you have to spin off as
many threads as there are components and block
Hi,
I have not yet looked much into Wicket but am quite interested in the
project.
We have a specific requirement where I could not yet find the right
information/documentation for.
We need to put multiple components onto a page receiving data through
web services. A single web services
