Databases
StackOverflow2013
Postsdbo
POSpring MVC annotation driven classes vs pure commands
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSpring MVC annotation driven classes vs pure commands
    primarykey
    data
    text
    <p>I have to say that I find the annotation-driven model of Spring MVC convenient, but coming from the Flex world, I am very much used to using the Command design pattern. It makes it very easy to reduce the levels of abstraction, and achieve flexibility by extending generic command functionality. However, I find it difficult to fit this into the Spring environment. </p> <p>In the ideal case, there should be no controllers but one generic HandleWebRequestCommand class, which, based on the request params (or URL path vars) executes another command (or a chain of commands). Other commands will be responsible for calling remote services, handling the DB retrieval/persistence, file manipulation, etc. This will reduce the whole Controller/Service/Persistence cake to a set of interchangeable and uncoupled commands.</p> <p>The hardest part by far seems to be making the mappings between what is happening and which commands should be executed. I see an XML context-like file very appropriate for this purpose where all the commands are declared. Also, their dependencies will be supplied (Every command might have a set of other commands that it depends on (interfaced, of course)) So far, I don't envision the use of an event-driven architecture, since most of the commands will still be executed as a result of HTTP request, so the most important mappings will be those within the HandleWebRequestCommand</p> <p>I am confused. Please help. Should I keep fitting this Spring, or start developing my own architecture directly on top of Java EE? Is such an architecture OK at all?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USArjan Tijms
    1. USpreslavrachev
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSpring MVC annotation driven classes vs pure commands
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload