Hi Chris, > > What would other benefits be in having Spring fully manage Stripes' > > action beans? > > I have used Spring Security annotations on Spring-managed Stripes > ActionBeans and that was very useful. You can define required > roles/permissions at the class level, or event handler method level.
Interesting. I'd love to see an example added in the "User Additions" part of the site! > I also was able to add low-impact performance monitoring using Spring > AOP interceptors with JaMon. Same thing, I'd love to see an example... > > Is their a specific reason to why you want to open transactions in > your action beans rather than in a service layer? > > Opinion is divided on demarcating transactions within ActionBeans. As > Dmitri mentions, defining pass-through controllers that do nothing but > demarcate transactions across multiple service method calls might be a > waste of time. If the developer understands the tradeoffs, then its fair > game IMHO. Agreed. Unfortunately in my case we have experienced as well as beginner developers on our projects. We also start projects with one team and end up coming back a few months later with another team. This leads us to employ rather strict "layer" (and coding) conventions so that everyone can 1. find their way around easily 2. not have to think when to start a transaction (it's a service method named save*, update*, find* etc.) Pretty much as I describe in my Stripes Spring JPA guide : http://www.stripesframework.org/display/stripes/Stripes+Spring+JPA I'd love to get some feedback! > Chris. Cheers, DJDaveMark ------------------------------------------------------------------------------ _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
