[DSingh]

Additional Files for Previous Post.

Actually Its not allow to upload Zip.

Thanks,
DSingh

[Isomorphic]

One more thing before we try to run your test case:
You're reporting this problem against a build dated 2013-07-24 - can you confirm whether this is still a problem in the latest nightly build?

Thanks
Isomorphic Software

[DSingh]

We tried with latest build of Power Edition “v9.0p_2013-12-14/PowerEdition Deployment”.

Still facing the same issue.

Thanks,
Deepak Singh

[DSingh]

Any update on this issue.

Thanks,
Deepak Singh

[Isomorphic]

Your example adds an editCompleteHandler in the Save button's click handler, so every time you click "Save", it adds another handler. The behavior of this sample - one message on the first save, two messages on the second, three on the third, and so on - is therefore to be expected. Note, it is not related to changing multiple records - the same behavior occurs if you change a single record, because that's what the sample has been written to do.

This bug in the sample aside, we see no issue. Although your server side involves the intervention of the BatchDataSource class, the responses coming over the wire are correct with no duplication, and a quick sanity test of the editComplete handling subsystem in both SmartClient and SmartGWT shows that we have no general problem with multiple calls to handlers.

So either you have a similar problem of multiple handlers in your real application code, or the underlying problem is not demonstrated by this sample case.

Regards,
Isomorphic Software Support

[DSingh]

Hi,

Yes your are correct It is happens for single record also. Can you let me know how could read Multiple Response using editCompleteHandler. Becasue I dont see any other way to get Callback response and read the Messages I send from Server.

Regards,
DSingh

[Isomorphic]

The problem is this:

Your example adds an editCompleteHandler in the Save button's click handler, so every time you click "Save", it adds another handler

There is no problem with using editCompleteHandler - the problem is that you are adding an additional handler every time you click "Save". The solution is simply to move your call to addEditCompleteHandler() out into code that only runs once.