On 20 juil, 03:15, jarrod wrote:
> I've spent some time looking through the new RequestFactory and
> ValueStore packages in GWT 2.1-M2. I am excited to see data binding
> and validation creeping into the core GWT code. However, I have a bit
> of a concern that the current implementation is too s
It is definitely intended that the Editors (data bound widgets) will not
require the RequestFactory.
On Wed, Jul 21, 2010 at 6:38 AM, Thomas Broyer wrote:
>
>
> On 20 juil, 03:15, jarrod wrote:
> > I've spent some time looking through the new RequestFactory and
> > ValueStore packages in GWT 2.
I think it goes a bit deeper then that.
EditorSupport depends on DeltaValueStore, which depends on Record. While
Record is merely an interface, its provided implementation, RecordImpl,
depends on RecordJsoImpl, all three of which imply that my Record (however
it is implemented) has both "id" and "
Maybe I should rephrase my question.
I have a REST service in place that serves JSON... you know, GET, PUT,
POST... the lot. So I am not currently using any GWT RPC or
RequestFactoryServlet mechanisms, nor do I have JPA-annotated beans in my
project. The only thing I do have is a suite of JavaScri
Cell Tables are already all set for you, they're completely independent of
RequestFactory et al.
We're in the midst of a rewrite of EditorSupport that will make it
independent of ValueStore et al, or at least easily severable.
In parallel, we're working to pull ValueStore and Record out of the pu
Well needless to say, I'm looking forward to it. :-)
On Jul 26, 2010, at 12:29 PM, Ray Ryan wrote:
> Cell Tables are already all set for you, they're completely independent of
> RequestFactory et al.
>
> We're in the midst of a rewrite of EditorSupport that will make it
> independent of Value
