http://gwt-code-reviews.appspot.com/1447815/diff/65/user/src/com/google/web/bindery/requestfactory/apt/RfApt.java File user/src/com/google/web/bindery/requestfactory/apt/RfApt.java (right):
http://gwt-code-reviews.appspot.com/1447815/diff/65/user/src/com/google/web/bindery/requestfactory/apt/RfApt.java#newcode105 user/src/com/google/web/bindery/requestfactory/apt/RfApt.java:105: log("Not reusing exsitng manifest file: " + e.getMessage()); existing http://gwt-code-reviews.appspot.com/1447815/diff/65/user/src/com/google/web/bindery/requestfactory/server/LocatorServiceLayer.java File user/src/com/google/web/bindery/requestfactory/server/LocatorServiceLayer.java (right): http://gwt-code-reviews.appspot.com/1447815/diff/65/user/src/com/google/web/bindery/requestfactory/server/LocatorServiceLayer.java#newcode53 user/src/com/google/web/bindery/requestfactory/server/LocatorServiceLayer.java:53: Class<? extends ServiceLocator> locatorType = getTop().resolveServiceLocator(requestContext); You'll need to call this out as a breaking change in 2.4, right? Should also point out that this is a wire format change, and that people w/mismatched client and server are a bit screwed. http://gwt-code-reviews.appspot.com/1447815/diff/65/user/src/com/google/web/bindery/requestfactory/vm/impl/OperationKey.java File user/src/com/google/web/bindery/requestfactory/vm/impl/OperationKey.java (right): http://gwt-code-reviews.appspot.com/1447815/diff/65/user/src/com/google/web/bindery/requestfactory/vm/impl/OperationKey.java#newcode47 user/src/com/google/web/bindery/requestfactory/vm/impl/OperationKey.java:47: byte[] data = md.digest(raw.getBytes("UTF-8")); Did RF already require UTF-8 on the wire? http://gwt-code-reviews.appspot.com/1447815/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
