DOCSLIB.ORG

Java EE Technologies for Development of Modern Information Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Java EE Technologies for Development of Modern Information Systems MASARYKOVA UNIVERZITA FAKULTA}w¡¢£¤¥¦§¨ INFORMATIKY !"#$%&'()+,-./012345<yA| Java EE technologies for development of modern information systems BACHELOR THESIS Andrej Makovický Brno, spring 2013 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Andrej Makovický Advisor: Ing. Petr Adámek ii Acknowledgement I would like to thank my supervisor Ing. Petr Adámek for all the support he provided, for his comments, help and supervision during my work on the thesis. I would like to thank head seminar tutor Mgr. Eva Kuˇcírkováfor her invaluable feedback. Last but not least, special thanks go to my family and friends who put their trust and hope into me, comforted me on the days when I was down and pushed me even further when the success was in my reach. iii Abstract The aim of this bachelor thesis is to map the current situation of ar- ticles on Laboratory of Software Architectures and Information Sys- tems wiki and then consolidate and extend the range of existing in- formation about commonly used Java Enterprise Edition technolo- gies on kore.fi.muni.cz, and thus provide centralized source infor- mation about this topic. iv Keywords Java EE, Java, Spring, Enterprise Java Beans, EJB, PA165, Enterprise Applications in Java, Java Platform Enterprise Edition v Contents 1 Introduction ............................3 2 Java Platform, Enterprise Edition ...............5 2.1 Overview ...........................5 2.2 Brief history .........................5 2.2.1 Java 2 Platform, Enterprise Edition 1.2......5 2.2.2 Java 2 Platform, Enterprise Edition 1.3......5 2.2.3 Java 2 Platform, Enterprise Edition 1.4......6 2.2.4 Java Platform, Enterprise Edition 1.5.......6 2.2.5 Java Platform, Enterprise Edition 6........7 2.2.6 Java Platform, Enterprise Edition 7........7 2.3 Core technologies of Java EE under Java Community Process ............................8 2.3.1 Enterprise JavaBeans................8 2.3.2 Java Persistence API................ 10 2.3.3 Java Transaction API................ 10 2.3.4 Java Server Pages.................. 11 2.3.5 Other......................... 11 2.4 Java EE technologies outside Java Community Process 13 2.4.1 Spring........................ 13 2.4.2 JUnit......................... 16 2.4.3 Stripes........................ 16 2.4.4 Other......................... 17 3 Wiki ................................. 18 3.1 MediaWiki .......................... 19 3.2 Navigation on Lasaris MediaWiki ............. 19 4 PA165 Enterprise Applications in Java ............ 22 5 Analysis of current Lasaris wiki site state .......... 23 5.1 First look ........................... 23 5.2 Collecting the Information ................. 24 5.2.1 Data organization.................. 24 5.3 Situation at the beginning ................. 24 5.4 Main deficiencies and appropriate goals ......... 25 5.5 Quick minor change .................... 25 6 Java EE and PA165 category organization ........... 27 7 Article changes .......................... 28 1 7.1 Selection scheme for new entries ............. 28 7.2 New articles in English language ............. 28 7.3 New articles in Czech or Slovak language ........ 29 7.4 Simple language navigation ................ 29 7.5 SimpleTeamManager - example source .......... 30 7.6 Removing and updating selected articles ........ 32 7.7 Cross-referencing ...................... 33 7.8 Redirects ........................... 33 8 Summary of changes ....................... 35 9 Conclusion ............................. 36 A Bibliography ........................... 37 B Attachments ............................ 40 B.1 Attachment 1 ........................ 42 B.2 Attachment 2 ........................ 43 B.3 Attachment 3 ........................ 50 B.4 Attachment 4 ........................ 58 B.5 Attachment 5 ........................ 59 B.6 Attachment 6 ........................ 60 2 1 Introduction Java EE is an astounding platform. It is dedicated to enterprise ap- plications and the emphasis is put on ease of development. During last decade, the technologies used in Java Platform, Enterprise Edi- tion (henceforth only Java EE) made a greoper using Java EE. Thereat leap forwards. The improvement was so big that in this era of free in- formation flow it became confusing and very time-consuming to find crucial information about all the aspects of development. This phe- nomenon is particularly true when someone wants to become a pro- fessional devel are lots of useful application programming interfaces (APIs), frameworks, application servers, containers, and the list goes on and on. Nearly for each enterprise application problem domain both open source or proprietary solutions are provided. When I decided to learn about them, the first thing I tried was to find an information database containing the material I wanted to learn. After a long time of unsuccessful searching I stumbled upon Laboratory of Software Architectures and Information Systems (La- saris) wiki site1. The information regarding Java EE were incredibly chaotic. On one side of the coin, there were entries which were great, easy to read and comprehend and provided loads of information I did not even dream about. On the flip side, many articles were in corrupt state, out-of-date or simply missing. I saw an opportunity to enhance this complex information database and provide quality service to every- one who would be as much interested to learn Java EE as I was. Enhancement of Lasaris wiki entries is not only beneficial but also necessary. When I tried to get into Java EE myself, though being a good learner the learning curve was very steep. Diverse placement of information was not helpful at all and the information-mining soon became very time consuming. Documentations being helpful as they are have never been built for beginners, but mainly for ev- eryday users and experienced developers. Technology providers of- ten purposefully omit comparisons with technologies alternative to theirs and often list only benefits which their product provides. The primary goal I set to myself was to make the entries regarding 1. http://kore.fi.muni.cz/wiki/index.php/Hlavn%C3%AD_strana 3 1. INTRODUCTION Java EE legible, easy to comprehend and simply better in every way. This would include extending the knowledge database and publish- ing articles in English as well. Details about goals can be found on- ward, because I needed thorough mapping of status quo before they could be clarified. I used the most natural structural pattern writing this thesis. It follows the complete process of my work and in detail documents the process of rebuilding Lasaris lab wiki. Chapter 2 and its subsections provides an overview of Java EE platform and contemporary technologies used in development on this platform. Chapter 3 is dedicated to information about wiki sites and MediaWiki application. In chapter 4, there is an overview of course PA165. Chapter 5 focuses on analysis of the relevancy and state of articles regarding Java EE technologies. It contains sections about collecting all the information about current situation on the website, summary of the entries as they were before the actual con- solidation and extension happened or information about Java EE ar- ticle organization. Chapter 5 also contains the outline of the whole approach chosen for improving status quo. Chapter 6 depicts the or- ganization and updates of out-of-date articles. In Chapter 7, the de- scription of all article changes including creation of new articles, and a description of the application, which served as an example source, as well. Chapter 8 frames the whole work and covers the changes made in the process of Lasaris wiki enhancement. Conclusion fol- lows in the last chapter - Chapter 9. 4 2 Java Platform, Enterprise Edition 2.1 Overview Java Platform, Enterprise Edition or Java EE is an enterprise Java computing platform developed by Oracle. Java EE extends the Java Platform, Standard Edition(commonly referred to as Java SE) by in- troducing application programming interfaces (henceforth only APIs) for object-relational maping, distributed and multi-tier architectures, and web services. Java Platform, Enterprise Edition 6 (Java EE 6)1 which is specified by Java Specification Request (JSR) number 316[2] was released on 10th December, 2009 and is current up-to-date re- lease. In Java EE, the Java Platform, Standard Edition APIs are extended with technologies which provide support for web services, object- relational mapping, multi-tier architectures etc. 2.2 Brief history 2.2.1 Java 2 Platform, Enterprise Edition 1.2 In May 1998 Sun announced Java Professinoal Edition project (JPE). The first complete release came shortly after on 12th December, 1999 under the name Java 2 Platform, Enterprise Edition 1.2 or J2EE 1.2. It proposed basic set of technologies extending J2SE and thus ex- tending its range of use. This set includes Enterprise JavaBeans (EJB) 1.1, Java Servlet 2.2, Java Server Pages (JSP) 1.1 and and e few oth- ers, even the first Java Transaction Application API (JTA) version 1.0. Since then it became subdue to Java Community Process (JCP). 2.2.2 Java 2 Platform, Enterprise Edition 1.3 With JSR 58[14] came out next functional release - Java 2 Platform, Enterprise Edition 1.3. The release came out on 24th September, 2001. 1. A complete overview of JavaTM Platform, Enterprise Edition 6 API Specifica- tion
Load more

Recommended publications
  • Download Issue
    Issue October 2019 | presented by www.jaxenter.com #70 The digital magazine for enterprise developers JavaThe JDK’s hidden 13 treasures i Jakarta EE 8 Let the games begin JDK 13 Why text blocks are worth the wait OpenJFX 13 JavaFX gets its own identity © Teguh Mujiono/Shutterstock.com, Pushkin/Shutterstock.com Illustrationen: Sun Microsystems Inc., S&S Media Editorial Let’s celebrate Java – three times! It’s that time again: A new Java version is here! Java 13 Last but not least: Jakarta EE, the follow-up project of was launched as planned, six months after the release Java EE, has announced its first release under the umbrella of of Java 12, and again it has some interesting features on the Eclipse Foundation. We got hold of the executive director board. In this issue of Jax Magazine, we’ve covered them of the Eclipse Foundation, Mike Milinkovich, and asked him for you in detail. about the current status of Jakarta EE. The good news doesn’t end there, as JavaFX 13 has also been released. The UI toolkit is no longer included in the JDK Happy reading, but has adjusted its new version releases to the new Java re- lease cadence. Find out what’s new here! Hartmut Schlosser Java 13 – a deep dive into the JDK’s 3 Kubernetes as a multi-cloud 17 new features operating system Falk Sippach Patrick Arnold Index Java 13 – why text blocks are worth the wait 6 Multi-tier deployment with Ansible 21 Tim Zöller Daniel Stender Jakarta EE 8 is sprinting towards an 9 Do we need a service mesh? 28 exciting future for enterprise Java Anton Weiss Thilo Frotscher
    [Show full text]
  • Weld 3.0.2.Final - CDI Reference Implementation
    Weld 3.0.2.Final - CDI Reference Implementation CDI: Contexts and Dependency In- jection for the Java EE platform by Gavin King, Pete Muir, Jozef Hartinger, Martin Kouba, Dan Allen, and David Allen and thanks to Nicola Benaglia, Gladys Guerrero, Eun- Ju Ki,, Terry Chuang, Francesco Milesi, and Sean Wu A note about naming and nomenclature ............................................................................. ix I. Beans ............................................................................................................................ 1 1. Introduction ......................................................................................................... 5 1.1. What is a bean? ......................................................................................... 5 1.2. Getting our feet wet .................................................................................... 5 2. More about beans ................................................................................................ 9 2.1. The anatomy of a bean ............................................................................. 10 2.1.1. Bean types, qualifiers and dependency injection ............................... 10 2.1.2. Scope ............................................................................................ 13 2.1.3. EL name ........................................................................................ 13 2.1.4. Alternatives .................................................................................... 14 2.1.5. Interceptor
    [Show full text]
  • Pragmatic Guide to Javascript
    www.allitebooks.com What Readers Are Saying About Pragmatic Guide to J a v a S c r i p t I wish I had o w n e d this book when I first started out doing JavaScript! Prag- matic Guide to J a v a S c r i p t will take you a big step ahead in programming real-world JavaScript by showing you what is going on behind the scenes in popular JavaScript libraries and giving you no-nonsense advice and back- ground information on how to do the right thing. W i t h the condensed years of e x p e r i e n c e of one of the best JavaScript developers around, it’s a must- read with great reference to e v e r y d a y JavaScript tasks. Thomas Fuchs Creator of the script.aculo.us framework An impressive collection of v e r y practical tips and tricks for getting the most out of JavaScript in today’s browsers, with topics ranging from fundamen- tals such as form v a l i d a t i o n and JSON handling to application e x a m p l e s such as mashups and geolocation. I highly recommend this book for anyone wanting to be more productive with JavaScript in their web applications. Dylan Schiemann CEO at SitePen, cofounder of the Dojo T o o l k i t There are a number of JavaScript books on the market today, b u t most of them tend to focus on the new or inexperienced JavaScript programmer.
    [Show full text]
  • Jquery: Novice to Ninja
    SECOND Pantone: EDITION CMYK: JQUERYGrey scale PANTONE Orange 021 C PANTONE 2955 C NOVICE TO NCMYK IO, 53, N100, 0 JCMYKA 100, 45, 0, 37 NEW KICKS ANDBlack 50% TRICKSBlack 100% BY EARLE CASTLEDINE & CRAIG SHARKIE SIMPLE, FAST, POWERFUL — JAVASCRIPT THE WAY IT SHOULD BE Summary of Contents Preface . xvii 1. Falling in Love with jQuery . 1 2. Selecting, Decorating, and Enhancing . 19 3. Animating, Scrolling, and Resizing . 53 4. Images and Slideshows . 93 5. Menus, Tabs, Tooltips, and Panels . 139 6. Construction, Ajax, and Interactivity . 187 7. Forms, Controls, and Dialogs . 239 8. Lists, Trees, and Tables . 305 9. Plugins, Themes, and Advanced Topics . 347 A. Reference Material . 409 B. JavaScript Tidbits . 419 C. Plugin Helpers . 425 Index . 431 JQUERY: NOVICE TO NINJA BY EARLE CASTLEDINE & CRAIG SHARKIE wnload from Wow! eBook <www.wowebook.com> o D iv jQuery: Novice to Ninja by Earle Castledine and Craig Sharkie Copyright © 2012 SitePoint Pty. Ltd. Product Manager: Simon Mackie Assistant Technical Editor: Diana MacDonald Technical Editor: Tom Museth Indexer: Michele Combes Expert Reviewer: Jörn Zaefferer Cover Designer: Alex Walker Editor: Kelly Steele Printing History: Latest Update: February 2012 First Edition: February 2010 Second Edition: February 2012 Notice of Rights All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without the prior written permission of the publisher, except in the case of brief quotations included in critical articles or reviews. Notice of Liability The authors and publisher have made every effort to ensure the accuracy of the information herein.
    [Show full text]
  • Rich Internet Applications for the Enterprise
    Final Thesis Rich Internet Applications for the Enterprise A comparative study of WebWork and Java Web Start by Emil Jönsson LITH-IDA-EX–07/063–SE 2007-12-07 Linköping University Department of Computer and Information Science Final Thesis Rich Internet Applications for the Enterprise A comparative study of WebWork and Java Web Start by Emil Jönsson LITH-IDA-EX–07/063–SE Supervisors: Valérie Viale Amadeus Philippe Larosa Amadeus Examiner: Kristian Sandahl Department of Computer and Information Science Linköping University Abstract Web applications initially became popular much thanks to low deployment costs and programming simplicity. However, as business requirements grow more complex, limitations in the web programming model might become evident. With the advent of techniques such as AJAX, the bar has been raised for what users have come to expect from web applications. To successfully implement a large-scale web application, software developers need to have knowledge of a big set of complementary technologies. This thesis highlights some of the current problems with the web programming model and discusses how using desktop technologies can improve the user experience. The foundation of the thesis is an implementation of a prototype of a central hotel property management system using web technologies. These technologies have then been compared to an alternative set of technologies, which were used for implementing a second prototype; a stand-alone desktop client distributed using Java Web Start. Keywords: web development, Rich Internet Applications, WebWork, Java Web Start, Property Management System, hospitality software Acknowledgements First I would like to thank Amadeus for giving me the opportunity to do an internship at their development site in Sophia Antipolis.
    [Show full text]
  • Extending a J2EE™ Server with Dynamic and Flexible Resource Management
    Extending a J2EE™ Server with Dynamic and Flexible Resource Management 1 1 2 1 Mick Jordan , Grzegorz Czajkowski , Kirill Kouklinski , and Glenn Skinner 1 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054, USA {firstname.lastname}@sun.com 2School of Computer Science, University of Waterloo, Waterloo, ON N2L 3G1, Canada [email protected] Abstract. The Java™ 2 Platform, Enterprise Edition (J2EE™) is the standard platform for hosting enterprise applications written in the Java programming language. A single J2EE server can support multiple applications much like a traditional operating system, but performance levels can be difficult to control, due to the absence of resource management facilities in the Java platform. The Resource Management (RM) interface addresses this problem by providing a flexible and extensible framework for managing resources that is applicable across a broad spectrum, from low-level resources like CPU time to higherlevel resources such as database connections. RM has been implemented in the Multi-tasking Virtual Machine (MVM), a scalable operating environment for multiple applications based on the concept of isolated computations. This paper describes the application of MVM and RM to the management of resources in a J2EE Server and shows that application performance can be controlled flexibly and easily with low overhead and minimal intrusion. 1 Introduction The Java™ 2 Platform, Enterprise Edition (J2EE™) [1] is the standard server-side environment for developing enterprise applications in the Java programming lan- guage. J2EE is itself layered on the Java™ 2 Platform, Standard Edition (J2SE™) [2]. In many respects the combination of the J2EE and J2SE platforms subsumes the un- derlying operating system (OS).
    [Show full text]
  • A Bad Case of Stripes
    A Bad Case of Stripes A Bad Case of Stripes Author: David Shannon Publisher: Scholastic Paperbacks (2004) Binding: Paperback, 32 pages Item Call Number: E SHANN Camilla Cream loves lima beans, but she never eats them. Why? Because the other kids in her school don't like them. And Camilla is very, very worried about what other people think of her. In fact, she’s so worried that she's about to break out in a bad case of stripes! Questions to talk about with your child: Why did Camilla break out in stripes (and other patterns?) What did you notice about the patterns that break out on Camilla? Do they have anything to do with what’s happening around her? Look at each of the pictures. Was there anything about Camilla that stayed the same each time she changed? What made Camilla finally turn back into herself? Did Camilla learn anything from having a bad case of stripes? Look at the last page. Was there anything different about the way Camilla looks? Fun things to do together: David Shannon always hides a picture of his white terrier Fergus somewhere in each of his books. Look for the picture of Fergus in this book. Camilla loves lima beans. Have lima beans for lunch or dinner one day. Draw a picture of yourself with stripes, polka dots or some other pattern. Check out a book about patterns, for example, Pattern Bugs by Trudi Harris or Patterns at the Museum by Tracey Steffora. Recognizing and completing simple patterns is an important kindergarten readiness skill.
    [Show full text]
  • Migrating from Java Applets to Plugin-Free Java Technologies
    Migrating from Java Applets to plugin-free Java technologies An Oracle White Paper January, 2016 Migrating from Java Applets to plugin-free Java technologies Migrating from Java Applets to plugin-free Java technologies Disclaimer The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. Migrating from Java Applets to plugin-free Java technologies Executive Overview ........................................................................... 4 Browser Plugin Perspectives ............................................................. 4 Java Web Start .................................................................................. 5 Alternatives ....................................................................................... 6 Native Windows/OS X/Linux Installers ........................................... 6 Inverted Browser Control ............................................................... 7 Detecting Applets .............................................................................. 7 Migrating from Java Applets to plugin-free Java technologies Executive Overview With modern browser vendors working to restrict or reduce the support of plugins like
    [Show full text]
  • (Minus Sign) in Class Diagrams, 15 * (Asterisk) As Wildcard, 58 ? (Question
    Index - (minus sign) in class diagrams, 15 AOP module (Spring), 34, 37 * (asterisk) as wildcard, 58 Apache Axis web services framework, 210 ? (question mark) for positional bind Apache Maven, 280–285 variables, 187 Apache Struts framework, 23 + (plus sign) in class diagrams, 15 Apache Tiles framework, 122, 278 Apache Tomcat, 257 ■ A APF (Authentication Processing Filter), AbstractCachingViewResolver class, 60 233–243 AbstractCommandController class, 74–78 application contexts (Spring), 33 AbstractController class, 71–74 Application Controller pattern AbstractEnterpriseBean class, 158, 200 action/command handling, 52–56 AbstractHandlerMapping, 54 action handlers, using, 56–58 AbstractMessageDrivenBean class, 200 for action-view management, 50–52 AbstractProcessingFilter, 234 background, 50–51 AbstractStatelessSessionBean, 158 benefits and concerns, 68 AbstractTemplateViewResolver class, strategies with Spring framework, 52 60–61 view handlers, 59–62, 62–68 AbstractWizardFormController class, 89 application server transactions, 261 access decision manager (Spring application servers, 138 Security), 228 application service implementation class, accessDecisionManager property, 164 246–247 Application Service pattern Acegi Security, 223–224 benefits and concerns, 167 action/command handling (application to concentrate business logic in POJO controller), 52–56 classes, 162–163 action handlers strategies with Spring framework, page controllers and, 51 164–167 sequence, 54 applicationContext-security.xml, 229 using (application controller), 56–58
    [Show full text]
  • Perception and Effects of Implementing Kotlin in Existing Projects
    Bachelor thesis Undergraduate level Perception and effects of implementing Kotlin in existing projects A case study about language adoption Author: Emil Sundin Supervisor: Wei Song Examiner: Azadeh Sarkheyli Discipline: Informatics Course: IK2017 Credit: 15 credits Examination date: 2018-05-25 Dalarna University provides the opportunity for publishing the thesis through DiVA as Open Access. This means that the thesis work will become freely available to read and download through their portal. Dalarna University encourages students as well as researchers to publish their work in the Open Access format. We approve the publishing of this thesis work under the Open Access format: Yes ☒ No ☐ Dalarna University – SE-791 88 Falun – Phone +4623-77 80 00 Abstract The Kotlin programming language has seen an increase of adoption since its launch in 2011. In late 2017 Google announced first-class support for Kotlin on the Android platform which further popularized the language. With this increase in popularity we felt it was interesting to investigate how Kotlin affects the developer experience. We performed a case study to see how Java developers perceive the Kotlin language, and how it meets the requirements of these developers. To gather the developer requirements and their perception of Kotlin we performed two sets of interviews and rewrote parts of their codebase. The first set of interviews identified developer requirements and the second set of interviews showcased the Kotlin language and its potential use in their codebase. The results show that Kotlin can meet most of the developer requirements and that the perception of Kotlin is positive. Kotlin’s ability to be incrementally adopted was a prominent feature which reduced the inherent risks of technology adoption while providing them the ability to further evaluate the language.
    [Show full text]
  • Openjdk 8 Getting Started with Openjdk 8 Legal Notice
    OpenJDK 8 Getting started with OpenJDK 8 Last Updated: 2021-07-21 OpenJDK 8 Getting started with OpenJDK 8 Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission.
    [Show full text]
  • Develop a Simple Web Application with Apache Wicket and Apache
    Develop a simple Web application with Apache Wicket and Apache Geronimo Combine Wicket, Geronimo, and Apache Derby to form an open source Java Web development platform Skill Level: Intermediate Robi Sen ([email protected]) Vice President Department 13 LLC 10 Jul 2007 Apache Wicket is an innovative Java™ Web application framework that was introduced a couple of years ago. It helps simplify Web application development by clearly separating the roles of developers and designers. It lets you remove logical code from the view layer, eliminating the need for JavaServer Pages (JSP), providing a simple plain old Java object (POJO)-centric mode of development, and removing much of the need for XML and other configuration file formats. In this tutorial, learn how to set up your system to develop a simple Web application with Wicket, using Apache Geronimo as your application server and Apache Derby as the embedded database. Section 1. Before you start This tutorial is designed for developers who have found Java frameworks, such as Struts, lacking in needed functionality. If you're interested in developing Web applications in a more object-oriented manner, where the view is clearly separated from logic and there's minimal configuration and mapping, then Wicket is for you! This tutorial walks you through the basics of how Wicket works, while using Apache Geronimo to set up a Java Platform, Enterprise Edition (Java EE) server, Web server, and embedded database in just minutes. Combining Wicket with Geronimo lets you develop data-driven, scalable Web applications using software that's all open source. Develop a simple Web application with Apache Wicket and Apache Geronimo © Copyright IBM Corporation 1994, 2008.
    [Show full text]