Benutzer-Werkzeuge
becki:linux:java_web_programming
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
|
becki:linux:java_web_programming [2010-04-30 14:19] becki created |
becki:linux:java_web_programming [2010-04-30 14:29] (aktuell) becki |
||
|---|---|---|---|
| Zeile 1: | Zeile 1: | ||
| ====== Java Web Programming == | ====== Java Web Programming == | ||
| ===== Overview == | ===== Overview == | ||
| + | |||
| + | All technologies here need a servlet container such as [[:becki:linux:Apache Tomcat]]. | ||
| The [[wp>Java_Servlet]] API is basically [[http://www.linux-magazin.de/Heft-Abo/Ausgaben/2008/08/Reiches-Angebot|like CGI]]: Servlets dynamically produce HTML Pages. | The [[wp>Java_Servlet]] API is basically [[http://www.linux-magazin.de/Heft-Abo/Ausgaben/2008/08/Reiches-Angebot|like CGI]]: Servlets dynamically produce HTML Pages. | ||
| Zeile 12: | Zeile 14: | ||
| Apache Wicked has a first-class component model like Echo. It uses non-intrusive approach to HTML like Tapestry. It automatically manages server-side state. All code written in Java ala Swing. [[http://wicket.apache.org/introduction.html|Source]]. Wicket is [[wp>Apache_Wicket|lightweight]] but for [[wpde>Apache_Wicket|experienced Java programmers]]. Wicket is meant for building [[http://stackoverflow.com/questions/2168249/apache-wicket-vs-apache-click|complex applications]] (think desktop). [[ibm>web/library/wa-aj-wicket/|Intro]] | Apache Wicked has a first-class component model like Echo. It uses non-intrusive approach to HTML like Tapestry. It automatically manages server-side state. All code written in Java ala Swing. [[http://wicket.apache.org/introduction.html|Source]]. Wicket is [[wp>Apache_Wicket|lightweight]] but for [[wpde>Apache_Wicket|experienced Java programmers]]. Wicket is meant for building [[http://stackoverflow.com/questions/2168249/apache-wicket-vs-apache-click|complex applications]] (think desktop). [[ibm>web/library/wa-aj-wicket/|Intro]] | ||
| - | Apache Click claims to be //simple// and easier than Stuts and Tapestry. It uses no MVC and claims MVC is overkill for web apps. Click uses the Velocity template engine. It uses little XML. [[http://click.apache.org/docs/why-click.html|Source]]. [[ibm>library/wa-apacheclick/|Intro]] | + | [[Apache Click]] claims to be //simple// and easier than Stuts and Tapestry. It uses no MVC and claims MVC is overkill for web apps. Click uses the Velocity template engine. It uses little XML. [[http://click.apache.org/docs/why-click.html|Source]]. [[ibm>library/wa-apacheclick/|Intro]] |
| Unlike Wicket, Click by default maintains no state, but it comes with [[http://www.avoka.com/click-examples/home.htm|ready to use controls]]. [[http://stackoverflow.com/questions/2168249/apache-wicket-vs-apache-click|Source]] | Unlike Wicket, Click by default maintains no state, but it comes with [[http://www.avoka.com/click-examples/home.htm|ready to use controls]]. [[http://stackoverflow.com/questions/2168249/apache-wicket-vs-apache-click|Source]] | ||
becki/linux/java_web_programming.1272637145.txt.gz · Zuletzt geändert: 2010-04-30 14:19 von becki
Seiten-Werkzeuge
