View post: GSOC2008: GWT magic - Deferred Binding and Generators
Navigation
Recent posts from all feeds
- JBoss Open Choice, Part 1 - JBoss Enterprise Web Server
- hSenid - officially certified JBCP partner
- jBPM 3 seam/jsf/richfaces based console
- Help push the open sourcing of a jBPM Migration Tool
- JBUG Munich meets Pete Muir with JSR-299 - Contexts and Dependency Injection for Java EE (06.07.09 at 19:00 PM)
- Javarsovia, static analysis and annotations
- Drools Job requested - Buenos Aires Argentina
- Seam and Web Beans downloads temporarily relocated
- Introducing a new smart forms tool: Drools Advisor
- JBoss Cloud introduction video
- « Back to feed: Anton's GSoC'08 Drools blog
GSOC2008: GWT magic - Deferred Binding and Generators
While reading the book further, I realized that I do not need any special library for plugging new content editors to Guvnor.Currently, the editors are instantiated via EditorLauncher class, which provides several static methods for working with the editors. Now, we could actually remove the static property, change EditorLauncher to be interface and instantiate EditorLauncher like this:
EditorLauncher launcher = (EditorLauncher) GWT.create(EditorLauncher.class)
This will actually force the EditorLauncher implementation to be generated at the compile time using our generator (which would be subclassed from com.google.gwt.core.ext.Generator). This cool feature of GWT is called deferred binding ...
... which works by resolving and inserting the required class during compile time instead of runtime, as is the case in the Java language.
Basically, the need for any external library is diminishing in this case.
Post to DZone
Post to del.icio.us
Digg this!
Stumble It!