Hi:
Apologize for the delayed response.
That sounds different to the issue I was running into. In my case I do
recall the update working (server side) as well as the actual response over
the wire. For me It was purely an issue of how the Store/List Provider was
populated and shown in the UI
I actually found the underlying cause. Basically on the second update I am
getting an optimistic locking error.
But I am convinced I am using my JPA correctly.
Does that ring any bells or jog your memory?
On 21 December 2013 15:54, Alfredo Quiroga laww...@gmail.com wrote:
Ufff it's been so
Hello Alfredo. I am having a similar issue. Did you get to the bottom of
this?
Thanks
On Saturday, August 4, 2012 3:10:46 PM UTC+1, Alfredo Quiroga-Villamil
wrote:
I am still investigating here on my side, but I have a feeling I might
be missing the obvious so if someone knows what I am
Ufff it's been so long I can't remember :( sorry and on top of it I deleted the
project. I just read my own email again to see if I could tell what I was doing
wrong and even now can't really tell.
Sent from my iPhone
On Dec 21, 2013, at 8:40 AM, Javed Sumra javed.su...@specsavers.com wrote:
I am still investigating here on my side, but I have a feeling I might
be missing the obvious so if someone knows what I am missing or
potentially doing wrong please let me know.
Elements:
- A CellTable
- A ListDataProvider
- RequestFactory
- A refresh button
Scenario:
- The CellTable is
