I think what they're saying is use a pair of deferred bindings for your application. One for the standard use case and another for the admin use case. The standard case should never reference the admin tab and therefore the code that is contained in that tab or referenced in it should be dead-code eliminated by the compiler pass that generates the javascript/etc for the standard case binding option - ergo users can't manipulate the javascript to get into the admin section. For the admin case, it will contain the admin tabs and the others. For users that authenticate as an admin you can set the binding option (meta tag is easiest) on your host page to indicate to the GWT loader that it should load the admin page instead of the standard one.
On Jul 30, 8:16 am, Nickelnext <nickeln...@gmail.com> wrote: > I tried this way but i cannot make my AdminPanel (extends > verticalPanel) serializable, so i cannot transfer it like an object > through rpc... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
