Hehe yeah its pretty hard to reproduce it in a new project. Even in our app branch for that issue I have to delete things out very carefully. As soon as I delete too much or something wrong, the ClassCastException disappears because split points are generated slightly different or GWT optimizes code in a way that it does not call dynamicCast() anymore. Another example: In our app we also use GIN and after upgrading GIN from r236 to latest trunk (r251) the issue disappears because now GIN generates its Ginjector slightly different which results in different split points assignments (I think the previously non working constructor is now in the left over fragment and works again.).
You can see how fragile the situation must be and thats probably why its hard to reproduce. Seems like our app hits that single if statement in the compiler/optimizer/codesplitter that no one else hits ;-) -- J. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
