"Tugrul ..."
Welcome to the JavaRanch. We don't have many rule around here, but we do ask that you make your display name conform to our
Naming Standards. Please read them and adjust your display name accordingly. It helps us look more professional - even if we do have a moth-eaten mooose head as our logo.
There's limits to what you can overlap in a web app, whether you use
JSF, raw
servlets, or PERL CGI. One of those limits is that HTTP is a request/response protocol and not a client-server one, so the only way to get any overlap at all would be to spin off a worker
thread that could be picked up on the next client request. An HTTP request isn't complete until the server-side code completes.
Also, as a general rule, backing beans in JSF should not talk directly to JSF objects. That is, you wouldn't normally make a bean that seeks out a datatable and stuff things into it. Instead you define the databable to reference the backing bean and have the datatable load itself from the backing bean - which it does automatically when you set the datatable's value attribute. This is a principle known as Inversion of Control (or IoC, for short).
[ March 21, 2006: Message edited by: Tim Holloway ]