I'm having a problem finding the correct architecture for a new project we are working on.
The application has a Flex front end with Java acting as a remoting/gateway to the UI.
This means 80% of the java code is going to be database calls, data objects with 20% being business logic and listener services. There will be no JSPs, no servlets, no view etc etc...
So I'm trying to find an architecture that is built around that mindset. Just a tight, lean, webservices framework that could support multiple developers working on various aspects (and all the other good stuff (like scalability) that comes with a defined framework).
However, most of the frameworks I've seen feel more "all inclusive" then I want. It doesn't sound like Struts, Spring or any of that is really going to be beneficial in this respect since we only care about a robust and solid web service listener.
Any thoughts on this? Maybe I'm completely off base and should go with struts or some equivalent... it just feels like way to much overhead.
Yeah we are using Blaze... which is nice. But that only handles the messaging part. I was hoping for something, an architecture that uses BlazeDS but has a nice layout for where all the DTOs should go, JUnit integration, and all that sort of stuff.