Thank you very much for your responses Thomas and Y2i. Maybe, this can help to other people who are (like me) changing from Tomcat to Jetty. Refering to the web.xml and jetty-web.xml:
- I did know that jetty.home was pointing to my working directory (C:\workspace\my_app\src\main\webapp in my case), but my problem was that I couldn´t understand that Jetty was going to look for the users in a properties file inside my_app. I was trying to draw an analogy between the tomcat-way and the Jetty-way. I though "if the authentication is against the server (jetty), why do I have to provide the users to Jetty?" And the answer to this question is that this properties file is used to authenticate users ONLY for THIS web application. For Tomcat users: it´s like configuring a realm inside a <Context> element ( http://tomcat.apache.org/tomcat-7.0-doc/realm-howto.html#Configuring_a_Realm ). I presume that in a real context, you can have the properties file inside your_app, or establish the jetty.home system property and point to the properties file inside jetty.home/etc/realm.properties and authenticate as a user shared in all web apps. Thank you very much again. -- 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.
