Thank you so much for your reply, this has really helped me. The solution for me was to implement my own PlaceHistoryMapper, now I'm getting the exact behaviour I was looking for, while keeping within the A&P framework.
Many thanks, Alex On May 13, 2:28 pm, Thomas Broyer <t.bro...@gmail.com> wrote: > First, you could use the empty string instead of a "random token", and it > would give you a /#ContactUsPlace: token. > > There's also the possibility to either put a bunch of "places" into a single > Place class, and using the "token" to disambiguate them (e.g. > /#CommonPlace:ContactUs); or you could instead use different Place classes > but a single PlaceTokenizer (better IMO) with the same results. > ...and because an empty @Prefix is simply ignored when generating the token, > you could have /#contactus that way. > > Finally, but you shouldn't need it for your use case, you can provide your > own implementation of PlaceHistoryMapper instead of relying on the generator > (you'd lose all the magic related to @WithTokenizers and @Prefix though and > have to do it all by yourself). -- 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.
