This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
Thank you, Lieven!
I, actually read this. I try to understand what new ideas Spring Desktop is supposed to have.
Right now we have home grown SWING application, which becomes big enough. We are looking for solid framework. Netbeans is our first choice. It is a pretty solid platform, but migration cost is high. So, we are still looking around. Spring RCP looks promising. It gives us strong foundation, but we still have a freedom.
Yesterday I read your documentation and it seems Spring RCP doesn't have a feature we need - plugability. Our application is supposed to be a set of many plugins. User should just drop jar file in right place, that's it. In other words, each plugin has his own small configuration file, and framework merges them together when it starts. This is how Netbeans (and eclipse) works. In Spring RCP every single item should be configured manually. Am I right?
Thank you, Lieven!
I actually read this thread. I meant some docs or source code.
We have home grown swing application which becomes pretty complex. So we are looking for solid platform. Right now Netbeans is our first choice. It is pretty powerful platform, but migration cost is high. That's why we still look around. Spring RCP looks promising- it gives us strong ground but also we have freedom.
Netbeans has feature we need a lot- plugability. Our application is a bunch of plugins. User should not configure anything. He just drop jar file in right directory- done. All new menu items, new views appear automatically. Each plugin has his own small configuration file and framework (Netbeans for example) merge them automatically.
Couple days ago I read your documentation on Spring RCP. My understanding is Spring RCP doesn't have such feature. You have to configure manually every single item. Am I right?
I thought new product will have it. That's why I was looking for some info.
Any way, how difficult to plug new jars on the fly?
Well, the project was is a proof-of-concept stage, mainly looking into removing the singleton ServiceLocator pattern from the codebase and generifying the base classes of Spring RCP. Also the use of annotations for configuring binders and such was being explored.