Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've used CGI, PHP, JSP, Struts, Spring MVC (1.2), Bea workshop, JSF, JBoss Seam, Spring MVC (2.5) and <a href="http://wicket.apache.org" rel="noreferrer">Wicket</a> (in that order). I've noticed a jump in both productivity and quality for each new technology I've worked on. It just works better, It <strong>feels</strong> better. I prefer Wicket (with a twist of spring, quartz, etc.) over all of the others. I can honestly say I saw the light, and I don't want to go back to a darker -- or lighter ;) -- side.</p> <p>There is a lot to say about Wicket.</p> <ul> <li>Conversational support (or tab-enabling) comes by default, you do not worry about "open in a new tab" and "back" button problems ever again.</li> <li>It is component-based, so you can re-use code ala swing.</li> <li>Leverages a lot of the standard Java, like the type safety wonders.</li> <li>Supports advanced security features like url encryption.</li> <li>Clusterizable applications by default.</li> <li>And, most important, it is <strong>fun</strong> to use.</li> </ul> <p>There is a lot to improve for JSP and JSF.</p> <ul> <li>The one thing that bothers me the most is the "EL" nonsense, for I believe it breaks the nice java type safety and strength.</li> <li>Both need tooling support for high productivity.</li> <li>You need another framework on top of both of them to really solve the problems (as seen with seam framework, which makes JSF usable).</li> <li>The error handling is very tricky and the exceptions are not straitforward helpful.</li> <li>It is difficult to make reusable components on both frameworks and doesn't support a proper model for separation of concerns.</li> <li>... and, most important, a long etc of minor pains, like <a href="http://techieexchange.wordpress.com/2008/02/21/jsf-session-expired-timeout-solution/" rel="noreferrer">this</a>, or <a href="http://mail-archives.apache.org/mod_mbox/myfaces-users/200508.mbox/%3Cc206dbe9050805070956b59d8f@mail.gmail.com%3E" rel="noreferrer">this</a>.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POJSF and Spring performance vs poor JSP performance
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USH Marcelo Morales
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJSF and Spring performance vs poor JSP performance
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYeah wicket is fine! You should also try Grails (with GORM as very powerful ORM Layer). Its similar to ruby on rails.
      singulars
      1. PO
      1. USMartin K.
 

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