Hi Isomorphic,
I'm transitioning existing 5.1p (v10.1p_2016-04-12) server code that was used from the client to work from server/servlet use as well, making it not depend on a RPCManager-instance presence.
Right now I'm seeing a problem where an update request if triggered from servlet, does not do a cacheSync after the successful update, while it does so when triggered from the client.
The only difference I can see is that it has an RPCManager in the client-case, while it has no RPCManager but a DSTransaction in the servlet-case.
I don't think this is on purpose. Can you have a look at the framework code here?
If needed I can try to prepare a testcase.
Thank you & Best regards
Blama
I'm transitioning existing 5.1p (v10.1p_2016-04-12) server code that was used from the client to work from server/servlet use as well, making it not depend on a RPCManager-instance presence.
Right now I'm seeing a problem where an update request if triggered from servlet, does not do a cacheSync after the successful update, while it does so when triggered from the client.
The only difference I can see is that it has an RPCManager in the client-case, while it has no RPCManager but a DSTransaction in the servlet-case.
I don't think this is on purpose. Can you have a look at the framework code here?
If needed I can try to prepare a testcase.
Thank you & Best regards
Blama
Comment