if I do not put EntityProxyId and ProxyClass in the History token,
is it still possible to get RequestFactory to work ?
in RF code, there are classes like getHistoryToken ,
and getProxyId, which assume certain pattern in the History Token.
(mainly RF compatible history tokens, @xx@ etc)
is it possible to maintain two Ids in our place,
for example:
EmployeePlace {
String/Long prettyId;
EntityProxyId<EmployeeProxy> record;
String action;
}
1- prettyId, is the entity's ID as it is stored in the database,
a Long value for example.
2- EntityProxyId, is the ID that RequestFactory works with,
which contains @xx@ characters.
if I use prettyId, during tokenization,
to create and parse tokens in the format /employee/777
and internally set the EntityProxyId to satisfy RequestFactory,
do you think it will work, or result in unpredictable behaviour in RF?
placeController.goTo(new EmployeePlace("view", 777,
employeeProxy.stableId())
what do you think of this approach,
is it flawed ?
Thank You
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
