mabe wrote:We are using eValid on a GWT application and every time we update our app our entire set of starts failing? What gives?
GWT is a very powerful tool, for sure, but what you have found out the hard way is that GWT assigns element IDs using its own number scheme. When the entire application is "rebuilt" then GWT's system re-invents the assigned numbers, as you have found obviously to your dismay.
What we have found in these cases is that you need to move away from using element IDs as the pivots for AJAX synchronizations, and instead pivot those synchronizations on some other element in the page that IS invariant across build-to-build boundaries. We have used page elements such as anchor tags or input item tags with success.
(Just to be totally accurate here, it is important to point out that the eValid Adaptive Playback feature might fail in the case of a GWT application which has had it's ID tags given new values. The reason for this is that Adaptive Playback depends on ID tags as the nominal page invariants.)
The eValid Team