Results 1 to 3 of 3

Thread: One Controller class per UI functionality?

  1. #1

    Default One Controller class per UI functionality?

    Hello. If I have a CRUD type screen (Add, Edit, Delete), should I have one controller for the entire screen or one controller per button/functionality (i.e. Add, Edit, Delete)?

  2. #2
    Join Date
    Aug 2004
    Location
    San Mateo, CA
    Posts
    1,265

    Default

    A matter of taste. You could consider a MultiActionController. Depends how different the responsibilities on the different actions are. Having the one controller perform all of them of course gathers any dependencies--but you could always use a common superclass for this.
    Rod Johnson - GM, SpringSource Division, VMware
    http://www.springsource.com
    Spring From the Source

  3. #3

    Default

    Thanks, Rod.

Similar Threads

  1. Order of Bean definitions matters?
    By cfuser in forum Container
    Replies: 2
    Last Post: Oct 21st, 2005, 10:29 AM
  2. Spring container fails with no exception
    By naor in forum Container
    Replies: 9
    Last Post: Oct 1st, 2005, 03:39 PM
  3. EHCaching Hibernate
    By dencamel in forum Data
    Replies: 3
    Last Post: Sep 6th, 2005, 09:03 PM
  4. Replies: 3
    Last Post: Sep 4th, 2005, 11:11 PM
  5. Stack Overflow
    By rayho222 in forum Container
    Replies: 6
    Last Post: May 17th, 2005, 03:42 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •