On Saturday, December 11, 2010 11:51:28 PM UTC, AP wrote:We are not using Spring Roo. The problem is as follows
1. User provides credentails to login to a portal. 2. An existing portal verifies the credentials. Reads LDAP and grabs more information about the user. 3. This info is added to the Http header and the http request is to be forwarded to the new GWT app. 4. The GWT app needs to read a the header and different users will land on different pages. I was hoping that there would be a way to read the HTTP header and decide which page to serve the user. It seems to me that I will have to intercept the request in an servlet and let the servlet decide where the user need to in the app. When you say land on different pages, you mean different HTML pages? Are these different pages all hosts for the same GWT app? It definitely sounds like something you'd want to do server-side otherwise there'll be a page presented after logon which loads a GWT application, all just to be redirected to a different page. Is there a reason you prefer to code this logic in the client? If you mean there's just one page after login but depending on the user the GWT app will present a different "screen", then that's a different problem and something you could communicate (but HTTP headers wouldn't be the vehicle of choice). Thanks, Pete -- 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.
