Not sure who you are asking this of, but I will say that in general, this is an antipattern. At least, it doesn't fly in the consumer world where people expect graceful, hand-holding UIs. If you aren't allowed to click a button when you aren't logged in, the button should be absent or disabled or clearly flagged *before* it is pressed.
This is, of course, a gross generalization. But when building consumer UIs, I've almost never found it useful to catch login or privilege exceptions - the client should know beforehand whether or not the call will succeed. Jeff On Mon, Jun 6, 2011 at 12:36 PM, Deanna Bonds <[email protected]> wrote: > Have you tried throwing a Login or Privilege Exception from the server to > the client (when server needs the authentication or acl privilege). Then > let the client respond to the exception with a dialog - not a place. Then > the client can respond to the authentication response with reloading areas, > resubmitting the request that threw the exception, and any other internal or > visible updates it needs. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/OWlOdWpUWUVZZXNK. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
