Getting Started with Spring RCP

Hi Jacek. You get to the heart of a central concern with your comment. Several responses possible: Firstly, I imagine that either the sample could be rewritten to use annotations or, if it can't, that a next release of Spring RCP should make that possible. Secondly, you can try the Swing Application Framework (JSR-296) if you want annotations rather than XML. That framework provides for applications of similar size to those provided by the Spring RCP, without requiring XML. (And the risks of relying on JSR-296 seem to be about the same as relying on Spring RCP, at this point). Thirdly, personally, I don't see the problem with configuring stuff in XML files. In that sense, it is simply a question of taste.

 

True enough, except that Spring RCP hasn't existed in any real form over the past years. Now it's back but there's no guarantee that it'll go anywhere. (The 1.0.0 release just came out, after two years, and so who knows when the next release will be with us?) I would personally like it to do so (hence this article and hence the tooling I'm providing, should you need evidence), but there's no guarantees (hard to argue with Kirill's comments here). In that sense, depending on Spring RCP is as problematic as depending on JSR-296, but for different reasons. (And that's why I focused only on the technology in this article without being distracted by the politics around it.)

You're right, but the registration you speak of is just the sort of locator pattern we want to refactor out of the system. I'm looking into the annotation based configuration, which works great as long as you don't do a lot of configuration besides injecting other beans (f.e. using a propertyplaceholder configurer in conjunction with the component scanning provided in Spring 2.5 is proving to be a real PITA).

I don't think the XML configuration is that much of a burden, if you have a good IDE with Spring support I don't think you'll have a lot of issues. I've worked in a company where all products were made with Spring RCP, and I haven't encountered any problems concerning writing all those bean definitions. There could be some improvement, but I'm thinking more in the line of custom namespaces.

Anyway, you're right in many ways. Things should be simplified. But then again, writing all my forms in YAML also seems a real hassle, and I'm sure a refactor will certainly cause all sorts havoc there too... :)

Great Geertjan!

Thanks a lot!

Does NetBeans handle the refactoring in XML? If yes, how?

>> Secondly, you can try the Swing Application Framework (JSR-296) if you want annotations rather than XML.

Isn't it possible to configure Spring with Java or a scripting language? In picocontainer this is possible with nanocontainer.

Any hints?

But wouldn't it be cool to provide those things?

Then NetBeans will be the SpringRC-IDE ;-)

Hint: To create the simple app with your plugin it is required to have the jdk1.6 as default (javax.swing.GroupLayout)

Hello!

Excuse me, if this is the wrong place for such questions.

I was interested in using a view to display the changes made in another view, both dockable.

How would you do that, when the both views are not known and they are created by the VLDockingApplicationPageFactory?

I though I could implement the Observer Pattern, but since the views are created by the factory I can´t get any Observable object registered in the Observer View.

Any Ideas?

Thanks!

Thanks for your answer Peter!

What I´ve done is exactly that, just I´m having some problems with the GUI actualization, since the form inputs works on a DialogWizard. The Other docked View must first be "resized" before the changes can be shown... Tipical GUI Problem...

 Best Regards!

Wagner