>> If I can take more of your time, what do you think about >> multi-action controllers? For cases of related but small >> in processing weight actions, it's might be appropriate to >> invoke a single (static) method instead of a class based >> on the url query parameters. Is ControllerSingleton / >> FormBeanUser everything we would possible want for >> multi-action controllers? > >You certainly can do this with ControllerSingleton - but why? Is it >really that hard to have lots of individual classes, one for each >action? What do you hope to gain? > >I find that "lots of little classes" is far more convenient than "few >big classes", especially with several engineers and version control. >YMMV though. > >Jeff Schnitzer >[EMAIL PROTECTED]
I completely agree that in most cases a separate class per action makes code easier to read and understand. I am just trying to simplify exception handling for many (16) tiny classes that take actions on the same model. For now, the exception handling and related logging code is repeated in each of those classes. Or it's not such a big cost after all? Thank you Valeri > >------------------------------------------------------- >This SF.net email is sponsored by: ValueWeb: >Dedicated Hosting for just $79/mo with 500 GB of bandwidth! >No other company gives more support or power for your dedicated server >http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ >[INVALID FOOTER] > _____________________________________________________________ Get 25MB, POP3, Spam Filtering with LYCOS MAIL PLUS for $19.95/year. http://login.mail.lycos.com/brandPage.shtml?pageId=plus&ref=lmtplus ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ [INVALID FOOTER]
