On Thu, Nov 4, 2010 at 4:47 AM, Wilhelmsen Tor Iver <[email protected]> wrote: > > You could maybe even implement that as a custom URLCodingStrategy or whatever > new mechanism in 1.5 is better suited for the task. The simplest case would > be just to have a singleton mapper with two methods, one for adding > (returning token for value) and one for removing (returning value for token) > where the token is just a sequence number. To make it more complicated the > service could be registered as a JNDI resource or a OSGi bundle... :) >
So what if the user just starts guessing tokens, since they're sequential? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
