Scout Jumps on Eclipse Release Train
The main theme of the Juno Release for us will be the support of web applications within Scout.
This year, Eclipse’s annual Simultaneous Release featured several projects that joined the Release Train for the first time. One of these projects, is the Scout framework. In this interview, JAXenter speaks to co-lead Matthias Zimmermann, about the new, Indigo version of Scout.
JAXenter: For the first time, Scout is part of the Eclipse Indigo Release. What is Scout?
Matthias Zimmermann: Eclipse Scout is a mature and open framework for implementing modern business applications. We have two main goals: First, a developer should have the chance to concentrate on implementing use cases and not on repetitive technical details. Second, we want to keep the entry threshold into Scout low. This way, Java developers can quickly work in a productive manner without having to undergo extensive training.
JAXenter: What is new in the Indigo version of Scout?
Matthias: Recently, we have been working on fitting the internal Scout framework to the guidelines of an Eclipse project. The clearest (and easiest) way was to rename the packages from “com.bsiag.scout” to “org.eclipse.scout.” To secure the backwards compatibility with existing customer projects Scout can now be used with Eclipse versions 3.4 to 3.7.
JAXenter: How is Eclipse Scout connected to other Eclipse projects, for example Eclipse 4.1?
Matthias: As we see it now, for the Juno Release we plan for Scout to work with the Compatibility Layer. In the medium term, of course, Scout – like other projects – will also work with e4 “native”.
Currently, the Scout SDK uses the two projects JDT and Jetty. At the moment, we are working on the integration of RAP. At BSI we also have a BIRT integration, which we want to re-work before publishing.
JAXenter: Which is planned for the Juno Release, next year?
Matthias: The main theme of the Juno Release for us will be the support of web applications within Scout. With the Indigo Release we support Swing and SWT on the client side, but this allows only Rich Clients. From customers as well as developers, we have got the clear signal that they are interested in Scout also supporting web applications. Within this aspect, it will be important that the implementation of web applications does not differ from the development of rich clients for the developer.