Hi, The .gwt.xml will be used only when you compile the Java code to javascript. So you will not be deploying the .gwt.xml.
Setting the user.agent and locale properties are just to make the development cycle faster. And when you actually do the final build you would not use these properties. I guess you would be able to use the embedded server even if you have integrated the server side to spring. I found this approach some where in the net, but don't remember where. Anyways, if we could map all your remote services to path like /services/ XXXXXService then we would be able to map the spring dispatcher servlet to <url-pattern>/com.abc.xyz.XYZ/services/*Service</url-pattern> or <url-pattern>/com.abc.xyz.XYZ/services/*</url-pattern> ........ I am not sure whether .../*Service worked correctly for me. ...... Well... now... will this actually solve the problem.... changes to the service not reflecting on the fly. I think it will not. I am not sure though... i was developing a prototype and had no time to investigate. I think the GWTShell uses its own class loader and that is how it handles dynamic loading of the changes. And when we took a different path - the spring dispatcher - we lost this feature. But yes the client changes will be reflected because it goes thro GWTShell. Theoretically... G, if you r trying this out pls let us know whether all this makes sense. Thanks, Jossey. On Nov 25, 4:04 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Thanks for answering. > > Is it correct that the user-agent property should be set to IE6 if I > keep on using the default GWT browser? I guess this tells GWT to only > compile the IE6 version, right? This makes me wonder whether or not > the .gwt.xml file is used on a production server, and if it is, do I > have to provide a version where the user-agent property is not set? I > can feel my question being slightly stupid by couldn't keep from > asking, sorry ;-) > > Now the reason why I'm running in -noserver mode is that I'm using > Spring (I need it for injection, and DB transaction management) via > the org.gwtwidgets.server.spring.GWTHandler, and from what I read by > its author, it can only work that way. I did try to make the whole > lot work with the embedded Tomcat server (which I would have been more > than happy with) but from what I understood, the fact that > GWTShellServlet is mapped to the "/*" url leads to conflicts. > > I'll give your suggestions a try, thanks. > > G. > > On Nov 14, 2:46 pm, gregor <[EMAIL PROTECTED]> wrote: > > > Well, if you are running in -noserver mode, then if you change any > > server side code, including classes like DTOs passed between client > > and server, you will naturally have to redeploy. You don't explain why > > you have elected to run in -noserver mode, but if you did you may get > > some suggestions as to how you might be able work with the embedded > > hosted mode Tomcat instance. > > > Two things you could look at to improve tunaround times are: > > > 1) if you set this in your module.gwt.xml file: > > > <set-property > > name="user.agent" > > value="ie6"/> or gecko etc > > > it will cut your module compile times roughly in half > > > 2) Modify your ant script to include a task that builds and deploys a > > WAR that contains just the server side code you need for development > > purposes. You then just click this task from your IDE. > > > regards > > gregor > > > On Nov 14, 8:25 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > > Is my question so trivial that no-one considers answering? --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
