At the moment we have a swing client that connects via rmi and we cannot change the client at all,
what we want to do though is change the way the transactions work, we can everything
except the swing client.
I've looked at Spring MVC, and others like it, and while the pattern implies you can yank one
out and plug in another it's just not the way it works, or seems to work. I suppose this is why there's Spring RPC
for rich clients.
Now maybe I don't need a framework for what I'm after, so let me get to the point.
I want the transaction flow and the config to slap together some components.
The view could be the swing client in most cases but also our website which will expose some transactions
to the public.
We could also have web services simply supply the service class everything it needs to
do it's work without any client populating various objects as it goes along.
Should I look again at Spring Web Flow or something similar?