Bear, I tried to use that approach, it seemed to not work so well. Apparently , OO isn't quite used here other than the fact they say they use
java. Hence the massive use of large static classes.
Eric, I was trying to convince them that option B would probably be the way I would go, since there is definitely duplicated logic in each block. I also mentioned option C, but they had never heard of a dispatch action, and said they didn't want to introduce "new" technologies.
I didn't think I was so far off on my thinking to correctly refactor the code.
Thanks for everyone replying. Maybe i'll print out the
thread and show it to the managers
As always, I welcome more thoughts on this issue. If there are valid points for the current way it's being done, speaking strictly from an action perspective and not the business logic in the action, I would love to hear them.