Refactoring + Spring Integration + Redesign

There is an back-end written in plain Java what uses EclipseLink JPA library. The administrative tasks in the back end (adding/modifying users, accounts, other information - up to 20 business objects) is done with Struts 1 + HTML + Javascript. What needs to be done prior to coding: 1) Update EclipseLink JPA to most recent version 2) Integrate Spring 3.1 Framework to simplify development/testing What is required in terms of new functionality: 3) 2 new sections should be introduced: 3.a) Client search screen. The screen should allow to search existing clients by Name / Phone Number / Postal Code. Upon opening, no data should be displayed. "Search" button should be present on the screen. Upon clicking on the "Search" button, filter parameters should be collected from appropriate fields and sent back to server-side. First 15 records are fetched from the database and displayed in a tabular view. "Load next" button should be available at this point to load more records from the database. Column sorting should be available for any column in the tabular view. Column set is following: "Client Name", "Street Address", "Postal Code", "City", "Email", "Phone Number", "Contact Person". When clicked into a row, existing client details window (see #4) should be opened. "Create New Client" button should be present on the client search screen to trigger new client creation procedure. The new client procedure is the same as editing an existing client. 4) Client edit screen. Please refer to attachment. The client edit screen has 3 tabs: Company Info, Carriers and Markups. Following is a description of every tab: 4.a) Company Info: allows to edit information specific to a client: Company Name, Address, set of usernames; 4.b) Carriers: allows to set up carriers available for the client in a tabular view. "New Carrier" button should be available as well as clicking into an existing carrier must bring up carrier information edit screen. The screen has to be specific to a carrier. Check with UpsCarrierConfiguration and PuroCarrierConfiguration business objects to see the differences between carriers. 4.c) Markups: allows to set up markups applicable to a client. Please check existing markup edit screen to copy it over to a new admin panel. Please note: markups tabular view should only display markups applicable to current client. "New markup" button should be available with the same logic as Edit Carriers. Check with attached screenshot for proposed design. Note: there is no documentation exist on the code, so a developer should be able to set up a project and understand how the code works by himself.