The Possible Solutions�

Most of us are used to working in a strict time schedule where often it becomes a compromise between the best solution and the cheapest solution. More often, we end up doing the cheapest solution to keep people above us happy as the project gets delivered on time. So here we outlined the possible solutions we had:

The cheapest solution would be to discard the DynaActionForm and use the normal ActionForm classes and create specific ActionForm classes to represent each domain object. In this approach, we could possibly create an ActionForm class for each of the classes in the domain model and even could cope with the inheritance very easily. In this solution, we could design a class structure as shown in Figure-2.

Figure 2: The ActionForm based solution

The solution we would however like to achieve (dare we say the best!) is to modify the struts internals to cope with the inheritance in a declarative way via the configuration file. To a solution architect, this one is alluring.

We have carefully weighed both the solutions that we have at hand and reached the following conclusions.

The solution 1 is by no means the ideal solution as we lose all the benefits of the DynaActionForm. The properties become pretty much hard coded within the ActionForm classes and the solution is less flexible.
Adding new properties to the forms means changing and recompiling the Java code whereas by using DynaActionForm we can add or remove properties in the configuration files.
More importantly, if we want to achieve dynamism in Model-View- Controller architecture where any change in the Model layer(Domain/Value objects) should only correspond a change in the View layer (JSPs), then it is pretty crucial that we refrain from such system where the Action classes and Form beans need to be changed to accommodate such features.

With these following conclusions in mind, we set out on the road to Solution 2.

Applet Index
(sorted alphabetically)
A B C D E F G H I J K
L M N O P Q R S T U
V W X Y Z #s

The Java Source
(applets w/source code)
A B C D E F G H I J K
L M N O P Q R S T U
V W X Y Z

How to Add Java Applets to Your Site

New on the Java Boutique:

New Review:

Time Management Made Easy with the Quartz Enterprise Job Scheduler
Why not just use the Java timer API? This open source scheduling API boasts simplicity, ease-of-integration, a well-rounded feature set, and it's free!

New Applet:

Reverse Complement
Reverse Complement is a simple applet that converts DNA or RNA sequences into three useful formats.