I don't think there is any way to make things compile much faster. I think the real question is why you think you need hundreds of modules. Does your website really need hundreds of small RIAs? I cannot think of too many situations where this would be needed.
I have used JPA and GWT in an application before without too many problems but not Spring (the app was a standalone RIA). Although debugging is a nice GWT feature it is not its strongest advantage - the organized OO-method of UI web design and AJAX integration are by far the most important aspects of the toolkit. Regards, Matt On Jan 9, 5:29 pm, Steve Anthony <[email protected]> wrote: > Hi, > > My engineering team took the last month to use GWT to implement new > pages for our UI. We had a world of trouble around interactions with > Spring & Hibernate. It was bad enough that the main GWT advantage > (productivity increases from easier debugging) was not realized. > > Likewise, we had some issues around compilation speed, 1-2 minutes to > compile a single module, for example. Think hundreds of modules, and > this isn't going to scale. > > I'm looking to see if there are any recommendations for people who > could provide a _focused_ training session; a few days to help us > understand how to work the technology interactions so that we can > improve our productivity. We know the basics; but are having trouble > adapting the technology into our stack and making effective use of it. > > Recommendations gratefully welcome. > > Steve --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
