It's really no different from GWT-RPC, if you're more comfortable with it.
The main difference is that you can push several things in a RequestContext
before firing it, making a batch request. The other major difference is
that changes to proxies have to be made in a RequestContext, after you
Hi all,
I'm studying new RequestFactory framework and I have a big doubt.
If the RequestFactory is stricly associated with a single Entity,
which is the best way transmit dynamic data to populate form fields
with default values?
For example I want to fill a drop down list, I can not use
you should be able to dynamically populate a drop list using requestFactory.
Once you fetch the data from the server, you can update your list.
The only instance where you would have to build a custom widget is when you
want to dynamically populate a SelectionCell with your dynamic data. For
that
On Wednesday, June 29, 2011 3:44:21 PM UTC+2, ungarida wrote:
Hi all,
I'm studying new RequestFactory framework and I have a big doubt.
If the RequestFactory is stricly associated with a single Entity,
which is the best way transmit dynamic data to populate form fields
with default
i believe to treat rf api , is to first think about how would do it with
normal java dao, and persistence api, then begin to translate them to rf
api's becouse that's basically what it tries to do.
by persistence api, i mainly thinkking about DAO's classes, where each DAO
usually revolves around
You are right, there is a misunderstanding. I try to complete my
question with an example.
My problem is when you want to do a drop down list of cities for a
form of a person entity.
I mean, the problem is not about how to dynamically update a form, it
is about where have I to put data that is
