On Thu, Jun 9, 2011 at 6:13 PM, <[email protected]> wrote: > Revision: 10311 > Author: [email protected] > Date: Thu Jun 9 11:31:51 2011 > Log: Support RequestContext composition (issue 6234) and mix-in (issue > 6035). > Remove no-method-overloads restriction by using a full method descriptor to > create the operation. > Use obfuscated type and operation tokens to reduce payload and JS size > (issue > 5394). Without this change, the operation tokens can be excessively > lengthly. > The RequestFactory interface is used as the "gwt.rpc" analog. > Add an annotation processor to generate an obfuscated type manifest and add > it > to the gwt-user project. This is only necessary when using the > JRE-compatible > RequestFactory client code. > Review at http://gwt-code-reviews.appspot.com/1447815 > Patch by: bobv > Review by: rjrjr
Some release notes also added to the relevant issues: 6234: Several of the ServiceLayer.resolveX() method signatures have changed in this release. These changes were made in order to allow the use of obfuscated type and operation tokens to reduce payload and generated JS size and to allow the use of overloaded method names in RequestContext subtypes. Users who have written their own ServiceLayerDecorator subclasses that override any of the resolveX() methods will need to modify their code to conform to the new API. In general, the expected behavior of the resolveX() methods is unchanged. Users who need to retain compatibility with 2.3 and 2.4 RequestFactory server code can leave methods with the old signatures in place, removing any @Override annotations. 5394: Users who depend on RequestFactorySource must now compile their proxy interfaces with the RequestFactory annotation processor. This tool is bundled in the requestfactory-client.jar or available separately in requestfactory-apt.jar. For Java 6 users, javac will automatically detect the annotation processor. Eclipse users will need to enable annotation processing via <Project properties> --> Java Compiler --> Annotation Processing and add requestfactory-apt.jar to the list of jars in Java Compiler --> Annotation Processing --> Factory Path. Users can confirm that the annotation processor is installed by looking for a META-INF/requestFactory/typeTokens file to be generated in the compiler's output directory. This file must be packaged into the jar file that contains the compiled proxy classes. Additionally, the -Averbose=true flag can be passed to javac (or specified in the "Annotation Processing" configuration UI) to enable diagnostic output for the annotation processor. -- Bob Vawter Google Web Toolkit Team -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
