Hi guys,

As you may know, I have been lurking around these forums and tinkering with Spring Rich Client for a couple of months now. Recently, I took a small use case from our business and implemented it from scratch using Spring Rich Client. It worked great but it was basically a proof of concept to show my boss (i.e. proof that Spring Rich Client is better than using our existing rich client architecture).

Now we want to start converting an existing Swing application to use Spring Rich Client. I would prefer to do this conversion in stages, adding various Spring Framework and Spring Rich Client features/services one by one. For example, I would like to start by introducing IOC to ease the wiring of collaborators. Next, I want to get beans like Petclinic's messageSource, imageResourcesFactory, imageSource, applicationObjectConfigurer and iconSource working. Finally, I want to add Spring Rich Client's Views, Forms and Commands support. Is this a good approach? Is there a better migration path?

I started off by adding the various Petclinic context files to my project. Then I starting modifying them and commented out a bunch of settings to try to get the container bootstrapped. One of the settings I commented out was the startingPageId setting because I don't want to introduce Spring Rich Client views right away. Unfortunately, upon startup, the container complained that this setting was required. How can I use Spring Rich Client without setting a startingPageId? I will eventually set it but for now I want to use our existing view classes and view navigation.