I am familiar with SecurityProvider but it's used from the server, not
place history. SecurityProvider works on the server to determine if
an operation is allowed, which is just checking for the @Service
annotation right now.
I am talking about the new methods in RequestFactory that provide
LGTM.
On Sun, Aug 22, 2010 at 2:07 AM, cromwell...@google.com wrote:
Reviewers: amitmanjhi, rjrjr,
Description:
Fix for date serialization problem in JsonRequestProcessor. Datanucleus
returns custom subtypes of java.util.Date from the datastore, which
causes Dates to be serialized as
Revision: 8619
Author: gwt.mirror...@gmail.com
Date: Sun Aug 22 07:49:19 2010
Log: Fix for date serialization problem in JsonRequestProcessor.
Datanucleus returns custom subtypes of java.util.Date from the datastore,
which causes Dates to be serialized as english strings.
Review at
Revision: 8620
Author: gwt.mirror...@gmail.com
Date: Sun Aug 22 16:25:33 2010
Log: svn merge https://google-web-toolkit.googlecode.com/svn/trunk
-r8618:8619 .
updated branch-info.txt
Patch by: amitmanjhi
http://code.google.com/p/google-web-toolkit/source/detail?r=8620
Modified:
Right, it's not implemented now, but planned. In M4+, all of these tokens
will change from getClass().getName() to an obfuscated identifier (e.g.
getToken(Foo.class) - xW). The security provider implementation on the
server will know how to decode these. I realize that, like pretty and short
URLs,
