OK.....
There was no change anywhere in the relevant code, so, the fact that updating to the latest version “fixed” the problem probably indicates that your environment has been getting corrupted in some way, and whatever process you used to update SmartGWT (perhaps restarting your IDE?) actually fixed that underlying corruption.
This might also explain the mysterious Spring issue you are reporting. And it may explain why your team keeps reporting issues where we have a nearly 90% rate of never reproducing the problem (which is unique amongst all customers).
So whatever you did.. please do it periodically, and make sure to do it before reporting any new bugs!
There was no change anywhere in the relevant code, so, the fact that updating to the latest version “fixed” the problem probably indicates that your environment has been getting corrupted in some way, and whatever process you used to update SmartGWT (perhaps restarting your IDE?) actually fixed that underlying corruption.
This might also explain the mysterious Spring issue you are reporting. And it may explain why your team keeps reporting issues where we have a nearly 90% rate of never reproducing the problem (which is unique amongst all customers).
So whatever you did.. please do it periodically, and make sure to do it before reporting any new bugs!
Comment