-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is extTID now required? #40
Comments
Hi. On Thursday, 23 August 2012, kevhender wrote:
|
Thanks for the quick response. We are using simple @ExtDirectMethod methods that return ExtDirectResponse objects. These methods are not form POST handlers, so it seems that this is why that param is not passed. Are we wrong to use ExtDirectResponse return objects in this case? We are using them for the simplicity in building them, but I suppose it's possible that we could do without that in these cases. It might still be something that you could change back, though, if that parameter is not essential in other places. Thanks again. |
You should not use ExtDirectResponse in your code. This is an internal If your code returns ExtDirectResponse all your responses are double On Thu, Aug 23, 2012 at 7:10 PM, kevhender notifications@github.com wrote:
|
That's interesting to know, it seems that we've always just dealt with it as needed. Thanks for clarifying this, we will look into our options. Keep up the great work, we're very pleased with this project. |
My guess is that your code looks something like this: @ExtDirectMethod and the call on the client service. doSomething (function(result) { The prefered way looks like this: @ExtDirectMethod service. doSomething (function(result) { If you don't want change the client code you could create a wrapper object public class Wrapper { On Thu, Aug 23, 2012 at 8:54 PM, kevhender notifications@github.com wrote:
|
We just updated to v1.2 from v1.0.15. I noticed that the constructor for ExtDirectResponse has changed from:
To:
Essentially, the extTID parameter is now REQUIRED, and if it is not there, an exception is thrown. This has broken some of our calls. Is there a reason why this was changed? Thanks.
The text was updated successfully, but these errors were encountered: