Thanks for the suggestions I still wished it would be possible to use internal jetty server and configure it to support HTTP authentication. It would make debugging of the server code a lot easier.
-- Roman On Apr 3, 5:33 pm, Vitali Lovich <[email protected]> wrote: > Cool trick I found on the web: > > javascript:void(function(){var%20i,a,s;a=document.getElementsByTagName('link');for(i=0;i<a.length;i++){s=a[i];if(s.rel.toLowerCase().indexOf('stylesheet')>=0&&s.href)%20{var%20h=s.href.replace(/(&|%5C?)forceReload=\d+/,'');s.href=h+(h.indexOf('?')>=0?'&':'?')+'forceReload='+(new%20Date().valueOf())}}})(); > > Refreshes your CSS without reloading your page. Pretty useful with > GWT apps since refreshing them regularly can cause problems. > > On Fri, Apr 3, 2009 at 11:31 AM, rudolf michael <[email protected]> wrote: > > if you changed the static files like .css, .html and others then yes you > > will need to re-deploy the war to see the changes in your hosted mod > > browser. > > But if you did change the .java files, then you will see the changes on the > > fly. means that no need to re-delpoy your war, just refresh your hosted mode > > browser. > > > regards, > > ruds > > > On Fri, Apr 3, 2009 at 6:27 PM, Roman <[email protected]> wrote: > > >> Thanks, for your reply. > > >> This would mean, that I could only debug the client code in Eclipse > >> and that the war file needs to be rebuilt and deployed every time I > >> change the server code, right? > > >> -- Roman > > >> On Apr 3, 5:00 pm, rudolf michael <[email protected]> wrote: > >> > Hello, > >> > You can always change your shell command params to point to any other > >> > Servlet container/app server. > >> > i dont think that the Jetty server which comes with the toolkit has > >> > support > >> > for such thing. > >> > in you shell-cmd.bat, add the following: > >> > com.google.gwt.dev.GWTShell -noserver -port 8080 > >> > where 8080 is your app server that your war is hosted. > > >> > On Fri, Apr 3, 2009 at 5:51 PM, Roman <[email protected]> wrote: > > >> > > Hello > > >> > > In my web.xml file I'm using the following configuration to enable > >> > > HTTP authentication for my app: > > >> > > <security-constraint> > >> > > <web-resource-collection> > >> > > <web-resource-name>Demo Application</web-resource-name> > >> > > <url-pattern>/*</url-pattern> > >> > > </web-resource-collection> > >> > > <auth-constraint> > >> > > <role-name>sol</role-name> > >> > > </auth-constraint> > >> > > </security-constraint> > > >> > > <login-config> > >> > > <auth-method>BASIC</auth-method> > >> > > <realm-name>Demo authentication</realm-name> > >> > > </login-config> > > >> > > For web mode I have configured a suitable realm in my tomcat server > >> > > and got HTTP authentication working. > > >> > > Now I would like to use HTTP authentication also in hosted mode using > >> > > the embedded Jetty server (for debugging). > > >> > > Can anybody tell me how to proceed or help me to locate the > >> > > configuration files for the embedded Jetty server? > > >> > > Thanks and regards, > >> > > Roman --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
