W-JAX 2009 Vorträge
Sep 22nd, 2009 by P.G.Taboada

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 Community die entscheidenden Impulse.

Google Web Toolkit – Making a Better Web 2.0
Speaker: Papick G. Taboada

Mit Adwords und Google Wave sind die ersten großen GWT basierten Anwendungen von Google erschienen. Mit einem optimierenden Kompiler und pfiffige Codegeneratoren werden mit GWT maßgeschneiderte JavaScript Anwendungen erstellt, die Entwicklung findet allerdings in Java statt. In dem Vortrag werden Konzepte, Neuigkeiten aus 2.0 und die aus Adwords gewonnenen Architektur „Best Practices“ vorgestellt.

SpringSource dm Server: Fitness für die Webanwendungen
Speaker: Agim Emruli, Papick G. Taboada

Java-EE-Webanwendungen tragen Deployment-bedingt eine große Menge an Bibliotheken mit sich. Mit OSGi werden dank einem standardisierten Modularisierungskonzept neue Wege gegangen. Lernen Sie in der Session die Möglichkeiten der Modularisierung in Java-EE-Webanwendungen auf dem OSS SpringSource dm Server kennen, damit schwergewichtige und monolithische Deployments der Vergangenheit angehören.

EDA in der Businessintegration
Speaker: Christian Dedek, Papick G. Taboada

Integrationsszenarien mit ereignisgesteuerten Architekturansätzen in Java umsetzen? Dieser Vortrag bietet Ihnen eine Einführung in EDA und Complex Event Processing (CEP) und stellt den Zusammenhang zwischen EDA und SOA her. Darüber hinaus veranschaulicht er die Architektur und den Aufbau von Esper und zeigt CEP-Einsatzszenarien.

Best Practices For Architecting Your GWT App
Sep 18th, 2009 by P.G.Taboada

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 elsewhere which you can use in your apps.

While dependency injection on the client side in general is nothing new, having it on a GWT application (I mean on the client) is something a little harder to setup. Since we don’t have reflection and dynamic proxies… But GWT provides an alternative called deferred binding, and there is a project called Gin providing the Guice DI approach for GWT apps.

There are some other projects like gwt-dispatch and gwt-presenter that where created inspired by Ray Ryans talk.

So if you are doing or planning GWT development, have a look at the video and the following projects:

  • gwt-dispatch: Inspired by Ray Ryan’s Best Practices For Architecting Your GWT App session at Google I/O 2009, this is an implementation of the ‚command pattern‘ discussed at the beginning of the video.
  • gwt-presenter: Inspired by Ray Ryan’s Best Practices For Architecting Your GWT App session at Google I/O 2009, this is an implementation of the ‚Presenter‘ part of the Model-View-Presenter (MVP) design pattern discussed in the video.
  • google-gin: GIN (GWT INjection) brings automatic dependency injection to Google Web Toolkit client-side code. GIN is built on top of Guice and uses (a subset of) Guice’s binding language. By using GWT’s compile-time Generator support, GIN has little-to-no runtime overhead compared to manual DI.

If you are looking for an easy approach to use Spring in the backend with the gwt-dispatch project have a look at this posting:

If you are looking for a simple and concise approach to use autowire your Gwt-RPC servlets with components from the Spring application context, have a look at this posting:


  • mvp4g: all-in-one approach providing annotation based Event Bus, Dependency Injection, Model View Presenter, Place Service


Use Spring with GWT dispatch
Sep 16th, 2009 by P.G.Taboada

From the GWT dispatch site:

Inspired by Ray Ryan’s Best Practices For Architecting Your GWT App session at Google I/O 2009, „gwt dispatch“ is an implementation of the ‚command pattern‘ discussed at the beginning of the video.

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…

Read the rest of this entry »

Non invasive GWT and Spring integration (reloaded)
Jul 17th, 2009 by P.G.Taboada

New project layout

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…

Read the rest of this entry »

Multichannel communication and social networking
Mai 12th, 2009 by P.G.Taboada

networking #rulez

es ging bei Skype los:

[12.05.09 12:19:46] Falk Sippach: hast du eine idee, wie ich die komplette springide als zip runterladen kann
[12.05.09 12:20:07] Falk Sippach: ich finde nur den link auf die update-site

Ich Google mich also auf folgenden Blog-Posting:

wo ich folgende Stelle finde:

Speaking about interaction with the team, I’d like to encourage every Spring developer and Tomcat user out there to download STS, give it a try and get involved in the community through our forums, JIRA, Twitter (#STS) and email (sts AT springsource DOT com). As a user you can now actively influence where STS is heading and what would be of value to you. Furthermore you don’t need to spend time figuring where to get certain tooling features or what the differences between Spring IDE and STS are.

Da ich Christian Dupuis ja nur „ein bisschen“ kenne (#speakerslounge #jax09), habe ich keinen #Skype Kontakt von ihm.

Tja, aber Christian ist ja auf dem Weg zu Juergen Hoeller

Juergen habe ich in meiner Kontaktliste in Skype, ist aber leider offline, social-network-Sackgasse…

Also habe ich ihn @cdupius „angeTwittert“:

woraufhin ich auch prompt eine Antwort bekommen habe:

Natürlich habe ich mich gleich bedankt und dabei auch Jürgen gegrüsst #networking

Und die wertvolle Info gleich per Skype an Falk weitergegeben:

[12.05.09 14:42:51] Papick G. Taboada:
[12.05.09 14:42:53] Papick G. Taboada: here we go
[12.05.09 14:42:54] Papick G. Taboada: :-)
[12.05.09 14:43:16] Falk Sippach: danke
[12.05.09 14:43:23] Falk Sippach: habs bereits runtergeladen
[12.05.09 14:43:36] Papick G. Taboada: :-)

Ist nicht nur ein Spielzeug…


»  Substance:WordPress   »  Style:Ahren Ahimsa