A problem faced in many software services groups that customize a core piece of software for a client is keeping a client within the upgrade path. From a business point of view, consultants should implement solutions for clients in a manner close to what is intended by the core product. From a technical point of view, consultants should not overwrite core code. When we do this and only make use of public APIs, it makes it much easier and cheaper for the client to get to the next software versions, getting the latest bug fixes and the latest features at the same time.
Spring in Workbrain - Part 4 - Forms and Views
Finally we move on to the Spring Web MVC portion of our Workbrain module. This is a long post, so grab some popcorn. Let's create a form in the application that will make use of our previously created services. We'll create a JSP as our view and I'll show you how to create the Java classes that interact with our view and the services.
Spring in Workbrain - Part 3 - Service Layer
So far in our Spring module in Workbrain, we have our Spring beans being automatically added to the Application Context and we have our database tables accessible via Spring in the data layer. Next we would like to add in our business logic and provide a service layer which can be used by our presentation layer.