Is anyone else getting any methods in their custom object class being uncontrollably called just after "createMessage()" sends that object (without you actually calling it)?
If I remove the "createMessage()" call, that code isn't called. (It is a method in my the custom class of the object being sent.)
I tried updating to Errai 1.3.2 but the problem remained.
Could this be something to do with Errai, or is it definitely not? I'm having other problems arising from this point onwards. If it is to do with Errai, how to I ensure it doesn't happen?
No, there's no asynchronous behaviour in MessageBuilder.createMessage().
If we could see a stack trace of one or more rogue calls to your custom object's methods, we could probably pinpoint the issue for you.
The simplest way to obtain a stack trace would be to add:
to the methods you don't believe the framework should be calling into. You will find the stack traces in the server log.
Alternatively, you could run your app in a debugger and set a breakpoint in your method. Most debuggers (i.e. eclipse) let you copy a stack trace just by selecting a thread and pressing Ctrl-C.
We look forward to hearing back from you on this.
This might be linked to my other issue of GWT-RPC creating a new servlet instance, because when I remove GWT-RPC, I can't seem to observe the behaviour any longer, but I'm not 100% sure it's gone. So if I could get GWT-RPC and Errai to use the same servlet instance, perhaps this problem will be gone.