I like stripes' simplicity, but I often run into a maintenance problem I
don't know how to solve:
I have a handler in an action bean that needs a field that none of the
other action beans need. Worst case scenario, one handler uses half the
fields and another handler uses the other half. Here's
Dan,
It really depends on how the interface of your application is designed. If
you have a complex UI screen where Dogs are listed and someone can edit a
dog in the same screen, it actually might be better to have everything in a
single action bean. Whereas, if you have a discrete list screen
