|
||||||
|
September 22nd, 2009
W-JAX 2009 Die Konferenz für Java, Enterprise Architekturen & SOA Die W-JAX ist die Konferenz für ganzheitliches technisches Know-how im Enterprise- und Webumfeld. Hier kommen die besten Experten Europas zusammen, um ihr Wissen und ihre Erfahrung an die Teilnehmer weiterzugeben. Durch ihren einzigartigen Mix an Themen verleiht die W-JAX alljährlich der Java Enterprise [...] September 18th, 2009
Just in case you haven’t seen it yet: there is very interesting talk from Ray Ryan available online: Google Web Toolkit Architecture: Best Practices for Architecting your GWT App A common question people ask is how to architect a GWT app. Ray Ryan discusses real-world learnings and patterns from the Google AdWords team and [...] September 16th, 2009
From the GWT dispatch site:
The project uses Gin in the frontend and Guice in the backend. Guice defines a very nice dependency injection framework, and as such, competes partially with the Springframework. But the Springframework is by far more than dependency injection, and I don’t want to miss any of its features in the backend. So I took a look at the gwt dispatch sources, and decided to use Spring to setup the server side of the dispatch service. GWT dispatch extensively uses constructor injection. This works perfectly with Spring, but not with plain servlets. So I needed to rewrite the DispatchServiceServlet a little… July 17th, 2009
 New project layout Here is my overdue update to my Non invasive GWT and Spring integration blog post from early 2008. Since then we have had the GWT 1.6 and GWT 1.7 releases: One of the biggest changes to GWT 1.6 is a new project structure. The old output format has been replaced by the standard Java web app "expanded war" format, and the actual directory name does default to "/war". Note that the war directory is not only for compiler output; it is also intended to contain handwritten static resources that you want to be included in your webapp alongside GWT modules (that is, things you'd want to version control). As a matter of fact, now we finally can (must) manage the web.xml file ourselves: Projects with server-side code (GWT RPC) must configure a web.xml file at /war/WEB-INF/web.xml. This web.xml file must define and publish any servlets associated with the web application. This is a little pain for really much gain, and that's why I am writing this post after all... Continue reading Non invasive GWT and Spring integration (reloaded) May 12th, 2009
Multi channel communication and social networking with twitter, blogs and skype. [...] |
||||||
|
Copyright © 2012 pgt - All Rights Reserved |
||||||
