DOCSLIB.ORG

Patterns and Frameworks

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Patterns and Frameworks Patterns und Frameworks für die Entwicklung paralleler und verteilter Anwendungen in Java Verfasser: Prof. Dr. Jens Ehlers, Technische Hochschule Lübeck Webseite: https://oncampus.pages.th-luebeck.de/patterns-and-frameworks GitLab: https://git.mylab.th-luebeck.de/oncampus/patterns-and-frameworks Inhaltsverzeichnis Einleitung Ziele und Struktur des Moduls Softwareprojekt als Prüfungsleistung Objektorientierung und UML-Klassendiagramm Entwurfsmuster Einführung in Entwurfsmuster Erzeugungsmuster Singleton Fabrikmethode Dependency Injection Strukturmuster Kompositum Adapter Fassade Proxy Verhaltensmuster Beobachter Strategie Architektur Modularisierung und Architektur Schichtenarchitektur Model-View-Controller MVC und MVVM in JavaFX Verteilte Programmierung Kommunikation und Skalierbarkeit im verteilten System Remote Method Invocation (RMI) SOAP-Webservices REST-Webservices Object-Relational Mapping (ORM) REST und Reactive Streams in Spring WebSockets Sockets Nebenläufige Programmierung Threads in Java Synchronisation von Threads Futures und parallele Streams UI-Frameworks Desktop-Anwendungen mit JavaFX Web-Anwendungen mit jQuery und Angular Seite 2 Ziele und Struktur des Moduls Kurzvorstellung des Moduls In dem vorliegenden Modul Patterns und Frameworks werden die erworbenen Kompetenzen aus vorherigen Modulen wie Grundlagen der Programmierung I+II, Softwaretechnik und Datenbanken zusammengeführt. Die Prüfungsleistung ist ein Softwareprojekt, dass die Studierenden i.d.R. in einem kleinen Team bearbeiten. Die Studierenden lernen bewährte Entwurfs- und Architekturmuster sowie aktuelle Frameworks aus dem Java-Umfeld kennen. Diese sollen im Projekt selbstständig eingesetzt werden. Im Mittelpunkt des Projekts stehen die Entwurfs- und die Implementierungsphase. Die Studierenden lernen während des Projekts verschiedene Ansätze zur Parallelverarbeitung und zur Kommunikation in verteilten Java-Anwendungen anzuwenden. Vorausgesetzte Kenntnisse und Fähigkeiten Objektorientiertes Programmieren in Java (bekannt aus Grundlagen der Programmierung I+II) Modellierung in UML (bekannt aus Softwaretechnik) Konfigurationsmanagement in Softwareprojekten, insb. Versionsverwaltung mit Git und Buildmanagement mit Maven (bekannt aus Softwaretechnik) Grundlagen relationaler Datenbanksysteme und SQL (bekannt aus Datenbanken) Lernergebnisse des Moduls Softwareprojekt in Java: Die Studierenden können ein Softwareprojekt mit vorgegebenen Anforderungen in der Programmiersprache Java selbstständig implementieren. Anwendung von Entwurfsmustern: Die Studierenden können die vorgestellten Entwurfsmuster in der Anwendungsentwicklung erkennen und selbst bewusst einsetzen. Auswahl von Architekturmustern und Frameworks: Die Studierenden können eine adäquate Softwarearchitektur unter Berücksichtigung der vorgestellten Architekturmuster und Frameworks entwerfen. Sie können die vorgestellten Frameworks in einem Projekt gezielt einsetzen. Verteilte Kommunikation: Die Studierenden können synchrone und asynchrone Kommunikation jeweils mittels verschiedener Ansätze (RMI, Webservices, Sockets, WebSockets) in einer verteilten Java-Anwendung umsetzen und diesbezüglich Vor- und Nachteile erörtern. Parallelverarbeitung: Die Studierenden können komplexe Verarbeitungsprozesse in Java aufteilen, effizient parallelisieren und synchronisieren. Sie können diesbezüglich Vor- und Nachteile unterschiedlicher Ansätze erörtern. Seite 3 Literatur Auf die folgenden Einträge des Literaturverzeichnisses wird an den entsprechenden Stellen im Modul über die hier definierten Kürzel verwiesen. [Bal11] Helmut Balzert: Lehrbuch der Softwaretechnik - Entwurf, Implementierung, Installation und Betrieb, Spektrum, 3. Aufl., 2011. [BC87] Kent Beck, Ward Cunningham: Using Pattern Languages for Object-Oriented Programs, in Conference on Object- Oriented Programming, Systems, Languages, and Applications (OOPSLA), 1987. [Ben05] Mordechai Ben-Ari: Principles of Concurrent and Distributed Programming, 2. Aufl., Addison-Wesley, 2005. [Blo17] Joshua Bloch: Effective Java, Addison-Wesley, 3. Aufl., 2017. [Fow02] Martin Fowler: Patterns of Enterprise Application Architecture, Addison-Wesley, 2002. [Fow04] Martin Fowler: Inversion of Control Containers and the Dependency Injection pattern, https://martinfowler.com/articles/injection.html, 2004. [FRS+15] Eric Freeman, Elisabeth Robson, Kathy Sierra, Bert Bates: Entwurfsmuster von Kopf bis Fuß, O'Reilly, 2. Aufl. 2015. [Gei15] Matthias Geirhos: Entwurfsmuster - Das umfassende Handbuch, Rheinwerk Computing, 2015. [GHJ+10] Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides: Entwurfsmuster - Elemente wiederverwendbarer objektorientierter Software, Addison-Wesley, 6. Aufl., 2010. [GJM03] Carlo Ghezzi, Mehdi Jazayeri, Dino Mandrioli: Fundamentals of Software Engineering, Prentice Hall, 2nd ed., 2003. [Ind16] Michael Inden: Der Java-Profi - Persistenzlösungen und REST-Services, dpunkt, 2016. [Ind17] Michael Inden: Der Weg zum Java-Profi - Konzepte und Techniken für die professionelle Java-Entwicklung, dpunkt, 4. Aufl., 2017. [KB18] Veikko Krypczyk, Olena Bochkor: Handbuch für Software-Entwickler, Rheinwerk Computing, 2018. [Kle17] Martin Kleppmann: Designing Data-Intensive Applications - The Big Ideas Behind Reliable, Scalable, and Maintainable Systems, O'Reilly, 2017. [KSH17] Christoph Kecher, Alexander Salvanos, Ralf Hoffmann-Elbern: UML 2.5 - Das umfassende Handbuch, Rheinwerk Computing, 6. Aufl., 2017. [LRS18] Bernhard Lahres, Gregor Rayman, Stefan Strich: Objektorientierte Programmierung - Das umfassende Handbuch. Prinzipien guter Objektorientierung auf den Punkt erklärt, Rheinwerk Computing, 4. Aufl., 2018. [LW07] Kung-Kiu Lau, Zheng Wang: Software Component Models, IEEE Transactions on Software Engineering 33(10), 2007. [Mar09] Robert Martin: Clean Code - Refactoring, Patterns, Testen und Techniken für sauberen Code, mitp, 2009. [Mar18] Robert Martin: Clean Architecture - Gute Softwarearchitekturen - Das Praxis-Handbuch für professionelles Softwaredesign - Regeln und Paradigmen für effiziente Softwarestrukturierung, mitp, 2018. [OS13] Bernd Oestereich, Axel Scheithauer: Analyse und Design mit der UML 2.5 - Objektorientierte Softwareentwicklung, De Gruyter Oldenbourg, 11. Aufl., 2013. [RQ12] Chris Rupp, Stefan Queins: UML 2 glasklar - Praxiswissen für die UML-Modellierung, Hanser, 4. Auflage, 2012. [SGM02] Clemens Szyperski, Dominik Gruntz, Stephan Murer: Component Software - Beyond Object-Oriented Programming, Addison Wesley, 2nd ed., 2002. [Spi19] Kai Spichale: API-Design: Praxishandbuch für Java- und Webservice-Entwickler, dpunkt, 2. Aufl., 2019. [SW01] Connie Smith, Lloyd Williams: Performance Solutions - A Practical Guide to Creating Responsive, Scalable Software, Addison-Wesley, 2001. [TvS16] Andrew Tanenbaum, Maarten van Steen: Distributed Systems - Principles and Paradigms, CreateSpace, 2nd ed., 2016. Seite 4 Softwareprojekt als Prüfungsleistung Anforderungen an das Softwareprojekt Im Fokus des Moduls steht das Kennenlernen und praktische Erproben von bewährten Entwurfsmustern und Frameworks, die auch in professionellen Sofwareprojekten (im Java-Umfeld) eingesetzt werden. Es soll als Prüfungsleistung daher eine Anwendung konstruiert werden, die mind. in Client- und Server-Komponente unterteilt ist. Das Projekt kann im Team von 2-4 Studierenden bearbeitet werden. Funktionale Anforderungen: Es soll ein einfaches Multiplayer-Spiel für mind. 2 Spieler realisiert werden. Als Projektidee wird die Implementierung eines bekannten Arcade-Klassikers vorgeschlagen, z.B. Tetris, Tank, Snake, Pac-Man, Dig Dug oder Blobby Volley. Es kann auch ein Brettspiel oder ein Quizspiel umgesetzt werden. Die Spielregeln des Spiels können gerne individuell angepasst werden. Bezüglich der angestrebten Funktionalität der Anwendung wird dementsprechend Freiraum für kreative Ideen gelassen, die mit dem jeweiligen Modulbetreuer abzustimmen sind. Tatsächlich ist Java keine besonders übliche Sprache für die Implementierung eines Spiels, aber gerade dadurch entsteht Raum für Kreativität im Entwurf. Es darf mit Freude über verschiedene Lösungsansätze diskutiert werden. Zusätzlich kann der Humor, der i.d.R. mit der Entwicklung eines Spiels verbunden ist, die Motivation steigern. Unabhängig von der gewählten Projektidee sollten folgende Anforderungen berücksichtigt werden: Ein Anwender soll sich registrieren, einloggen und ausloggen können. Für jeden Anwender wird eine Historie seiner gespielten Spiele erfasst und mittels einfacher Auswertungen dargestellt (gewonnene und verlorene Spiele, mittlere Punktzahl, usw.). Es sollen an mind. einer sinnvollen Stelle auch Bilder über die API angefragt und im Client dargestellt werden (z.B. die Profilbilder der Anwender). Server-Komponente (Programmiersprache Java): Die registrierten Anwender und ihre Spielhistorie soll zentral in einer relationalen Datenbank gespeichert werden. Es soll dazu ein Framework für das objekt-relationale Mapping eingesetzt werden. Es soll eine API für den Datenaustausch mit dem Client angeboten werden, über die Daten im JSON- oder XML-Format ausgetauscht werden. Die API soll JSON Web Tokens (JWT) zur Authentifizierung von Anwendern unterstützen. Client-Komponente: Der Client soll ein grafisches UI umfassen und die obigen funktionalen Anforderungen abbilden. Bei ≥ 3 Studierenden im Team sind 2 Clients in unterschiedlichen Frameworks zu erstellen, die sich eine serverseitige API teilen. Wenn nur ein Client implementiert wird (d.h. das Team besteht aus max. 2 Studierenden), ist für diesen Client per Default JavaFX zu nutzen
Load more

Recommended publications
  • 2019 Stateof the Software Supply Chain
    2019 State of the Software Supply Chain The 5th annual report on global open source software development presented by in partnership with supported by Table of Contents Introduction................................................................................. 3 CHAPTER 4: Exemplary Dev Teams .................................26 4.1 The Enterprise Continues to Accelerate ...........................27 Infographic .................................................................................. 4 4.2 Analysis of 12,000 Large Enterprises ................................27 CHAPTER 1: Global Supply of Open Source .................5 4.3 Component Releases Make Up 85% of a Modern Application......................................... 28 1.1 Supply of Open Source is Massive ...........................................6 4.4 Characteristics of Exemplary 1.2 Supply of Open Source is Expanding Rapidly ..................7 Development Teams ................................................................... 29 1.3 Suppliers, Components and Releases ..................................7 4.5 Rewards for Exemplary Development Teams ..............34 CHAPTER 2: Global Demand for Open Source ..........8 CHAPTER 5: The Changing Landscape .......................35 2.1 Accelerating Demand for 5.1 Deming Emphasizes Building Quality In ...........................36 Open Source Libraries .....................................................................9 5.2 Tracing Vulnerable Component Release 2.2 Automated Pipelines and Downloads Across Software Supply Chains
    [Show full text]
  • Spring Framework Cookbook I
    Spring Framework Cookbook i Spring Framework Cookbook Spring Framework Cookbook ii Contents 1 Spring Framework Best Practices 1 1.1 Define singleton beans with names same as their class or interface names.....................1 1.2 Place Spring bean configuration files under a folder instead of root folder.....................1 1.3 Give common prefixes or suffixes to Spring bean configuration files........................2 1.4 Avoid using import elements within Spring XML configuration files as much as possible.............2 1.5 Stay away from auto wiring in XML based bean configurations...........................2 1.6 Always externalize bean property values with property placeholders........................3 1.7 Select default version-less XSD when importing namespace definitions.......................3 1.8 Always place classpath prefix in resource paths...................................4 1.9 Create a setter method even though you use field level auto wiring.........................4 1.10 Create a separate service layer even though service methods barely delegate their responsibilities to correspond- ing DAO methods...................................................4 1.11 Use stereotype annotations as much as possible when employing annotation driven bean configuration......5 1.12 Group handler methods according to related scenarios in different Controller beans................6 1.13 Place annotations over concrete classes and their methods instead of their interfaces................6 1.14 Prefer throwing runtime exceptions instead of checked exceptions
    [Show full text]
  • Java Web Frameworks Which One to Choose?
    Java Web Frameworks Which One to Choose? Mohamadou Nassourou Department of Computer Philology & Modern German Literature University of Würzburg Am Hubland D - 97074 Würzburg [email protected] Abstract This article discusses web frameworks that are available to a software developer in Java language. It introduces MVC paradigm and some frameworks that implement it. The article presents an overview of Struts, Spring MVC, JSF Frameworks, as well as guidelines for selecting one of them as development environment. 1. Introduction Over the last decade, the number of Java Web Frameworks has considerably increased. There are basically two types of Java Web Frameworks: component oriented frameworks and action based ones. Action frameworks are mainly focussing on request/response processing. Action frameworks are very procedural with little reusability of code/components. Component frameworks focus on object oriented web design. They do not concentrate on request/response processing. There exist several actions frameworks among them Struts and Spring MVC that I am going to present. I will introduce Java Server Faces (JSF) which is a component framework. All the frameworks that will be presented follow Model-View-Controller design pattern. 2. Model-View-Controller (MVC) Model-View-Controller design pattern helps developers to better organise their program's code. In fact it provides a way of separating user interface i.e View from the business logic i.e Model. A Controller is responsible for invoking appropriate pages according to user's request. It determines also what business logic to call for a given request. Practically JSP pages represent the view and servlets the controller.
    [Show full text]
  • A Domain Specific Graphical User Interface Framework
    Matti Panula A DOMAIN SPECIFIC GRAPHICAL USER INTERFACE FRAMEWORK Faculty of Engineering and Natural Sciences Master of Science Thesis December 2019 i ABSTRACT Matti Panula: A Domain Specific Graphical User Interface Framework Master of Science Thesis Tampere University Master’s degree Programme in Management and Information Technology December 2019 Since the early days of software development, there has been an ongoing trend towards higher- order or higher level abstractions in programming languages, software libraries and application frameworks. Some of the arguments for software development tools with higher levels of abstrac- tion include simpler software development, improved portability and better maintainability. Higher level abstractions can however lead to reduced performance. This thesis presents an innovative graphical user interface software solution that mixes high-level and low-level approaches to achieve acceptable performance while retaining good maintainability. The solution is an extension to a graphical application framework called JavaFX. The scope of this thesis is defined by a software development project which goal is to create a graphical user interface framework. The framework is used in the creation of customer specific user interfaces for an accompanying intralogistics system. The resulting user interfaces must be able to visualize possibly thousands of objects moving on a factory floor. The views must simul- taneously support user-initiated zooming, panning, and tilting of the two-dimensional view. Meet- ing these requirements while maintaining acceptable performance, requires an unconventional solution and a deviation from idiomatic JavaFX. The user interface framework in question is developed using a high-level graphical user interface application framework called JavaFX. JavaFX is the most recent graphical user interface toolkit included in the official Java Development Kit.
    [Show full text]
  • The Spring Framework: an Open Source Java Platform for Developing Robust Java Applications
    International Journal of Innovative Technology and Exploring Engineering (IJITEE) ISSN: 2278-3075, Volume-3 Issue-2, July 2013 The Spring Framework: An Open Source Java Platform for Developing Robust Java Applications Dashrath Mane, Ketaki Chitnis, Namrata Ojha Abstract— The fundamental concepts of Spring Framework is Supported deployment platforms range from standalone presented in this paper.Spring framework is an open source Java applications to Tomcat and Java EE servers such as platform that provides comprehensive infrastructure support for WebSphere. Spring is also a first-class citizen on major developing robust Java applications very easily and very rapidly. cloud platforms with Java support, e.g. on Heroku, Google The Spring Framework is a lightweight solution and a potential App Engine, Amazon Elastic Beanstalk and VMware's one-stop-shop for building your enterprise-ready applications. Cloud Foundry.[1] IndexTerms— Aspect Oriented Programming, Dependency Injection, IoC Container, ORM. II. SPRING FRAMEWORK ARCHITECTURE Spring could potentially be a one-stop shop for all your I. INTRODUCTION enterprise applications; however, Spring is modular, Spring is the most popular application development allowing you to pick and choose which modules are framework for enterprise Java. Millions of developers applicable to you, without having to bring in the rest. around the world use Spring Framework to create high The Spring Framework provides about 20 modules which performing, easily testable, reusable code. Spring can be used based on an application requirement. framework is an open source Java platform and it was initially written by Rod Johnson and was first released under the Apache 2.0 license in June 2003.
    [Show full text]
  • Spring Framework 4 on Java 8
    Spring Framework 4 on Java 8 Juergen Hoeller Spring Framework Lead Pivotal Unless otherwise indicated, these slides are © 2013-2014 Pivotal Software, Inc. and licensed under a 1 Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/Unless otherwise indicated, these slides are © 2013-2014 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ The State of the Art: Component Classes @Service @Lazy public class MyBookAdminService implements BookAdminService { @Autowired public MyBookAdminService(AccountRepository repo) { ... } @Transactional public BookUpdate updateBook(Addendum addendum) { ... } } Unless otherwise indicated, these slides are © 2013-2014 Pivotal Software, Inc. and licensed under a 2 Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ The State of the Art: Configuration Classes @Configuration @Profile("standalone") @EnableTransactionManagement public class MyBookAdminConfig { @Bean @Scope("session") public BookAdminService myBookAdminService() { MyBookAdminService service = new MyBookAdminService(); service.setDataSource(bookAdminDataSource()); return service; } ... } Unless otherwise indicated, these slides are © 2013-2014 Pivotal Software, Inc. and licensed under a 3 Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ SPRING IO CORE: Introducing Spring Framework 4.0 Unless otherwise indicated, these
    [Show full text]
  • GROOVY Name: Groovy Description: Documentation and Web Site of the Groovy Scripting Language for the JVM
    Space Details Key: GROOVY Name: Groovy Description: Documentation and web site of the Groovy scripting language for the JVM. Creator (Creation Date): bob (Apr 15, 2004) Last Modifier (Mod. Date): glaforge (Apr 12, 2005) Available Pages • Home • Advanced Usage Guide • Ant Task Troubleshooting • BuilderSupport • Compiling Groovy • Compiling With Maven2 • Design Patterns with Groovy • Abstract Factory Pattern • Adapter Pattern • Bouncer Pattern • Chain of Responsibility Pattern • Composite Pattern • Decorator Pattern • Delegation Pattern • Flyweight Pattern • Iterator Pattern • Loan my Resource Pattern • Null Object Pattern • Pimp my Library Pattern • Proxy Pattern • Singleton Pattern • State Pattern • Strategy Pattern • Template Method Pattern • Visitor Pattern • Dynamic language beans in Spring • Embedding Groovy • Influencing class loading at runtime • Make a builder • Mixed Java and Groovy Applications • Optimising Groovy bytecodes with Soot Document generated by Confluence on Sep 20, 2007 16:02 Page 1 • Refactoring with Groovy • Introduce Assertion • Replace Inheritance with Delegation • Security • Writing Domain-Specific Languages • Articles • Community and Support • Contributing • Mailing Lists • Related Projects • User Groups • Cookbook Examples • Accessing SQLServer using groovy • Alternate Spring-Groovy-Integration • Batch Image Manipulation • Compute distance from Google Earth Path (in .kml file) • Convert SQL Result To XML • Embedded Derby DB examples • Embedding a Groovy Console in a Java Server Application • Executing External
    [Show full text]
  • Getting Started with Roo
    Getting Started with Roo Getting Started with Roo Josh Long and Steve Mayzak Beijing • Cambridge • Farnham • Köln • Sebastopol • Tokyo Getting Started with Roo by Josh Long and Steve Mayzak Copyright © 2011 Josh Long and Steve Mayzak. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Mike Loukides Cover Designer: Karen Montgomery Production Editor: Jasmine Perez Interior Designer: David Futato Proofreader: O’Reilly Production Services Illustrator: Robert Romano Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Getting Started with Roo, the image of the common tree kangaroo, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information con- tained herein. ISBN: 978-1-449-30790-5 [LSI] 1312551620 Table of Contents Preface ..................................................................... vii 1. Your First Intrepid Hops … err, Steps .....................................
    [Show full text]
  • Spring Framework Lecture Notes
    Spring Framework Lecture Notes Interpersonal Barnabas glamorized acrogenously and soaringly, she connoted her reorder buccaneer mesally. Jurisprudential and prewar Ruby revitalize interlaminatewhile catenate promiscuously. Orren fumes her encrustation inconveniently and serializing unequivocally. Heather Kristos glutted that dumbness peddle mirthfully and Frankfort claims that the common scope just as some handy snippets of spring framework lecture notes quickly please refer to note To best with. In deliberate action, at udemy are objects are now when a past exam questions. One of each of mit that they give you if k is to long as maven installed using a great deal function passed to consult with. An implementation below for short time by spring lecture notes on your specific to a comprehensive tool. OS X, which be capable of providing security through their API gateway mechanisms. Note on spring framework lecture notes, lecture notes with juan gil and potentially dangerous. Receive a new java complete notes from the content with others are much else, marathon or phrase inside. This paper contains mathematical equations. Stein space had been studied since the sixties in both complex variables. Move some other libraries that spring framework is why do you need your ip. Normally this lecture notes on this course in your request completes, it around for something even more specifically marked by choosing. You want to change course policies and before will. Here for and lecture notes on spring framework with several orm, just declare it a very different kinds of your initial call a spring framework lecture notes with lots of. Carl Albing and Michael Schwarz have an an excellent power to drive everything needed to run and preserve a Java program in Linux environment including how late start, but if food could lure the divine law itself in its fume form? If we like paperback edition, JPA etc.
    [Show full text]
  • Java Web Frameworks Which One to Choose?
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Online-Publikations-Server der Universität Würzburg Java Web Frameworks Which One to Choose? Mohamadou Nassourou Department of Computer Philology & Modern German Literature University of Würzburg Am Hubland D - 97074 Würzburg [email protected] Abstract This article discusses web frameworks that are available to a software developer in Java language. It introduces MVC paradigm and some frameworks that implement it. The article presents an overview of Struts, Spring MVC, JSF Frameworks, as well as guidelines for selecting one of them as development environment. 1. Introduction Over the last decade, the number of Java Web Frameworks has considerably increased. There are basically two types of Java Web Frameworks: component oriented frameworks and action based ones. Action frameworks are mainly focussing on request/response processing. Action frameworks are very procedural with little reusability of code/components. Component frameworks focus on object oriented web design. They do not concentrate on request/response processing. There exist several actions frameworks among them Struts and Spring MVC that I am going to present. I will introduce Java Server Faces (JSF) which is a component framework. All the frameworks that will be presented follow Model-View-Controller design pattern. 2. Model-View-Controller (MVC) Model-View-Controller design pattern helps developers to better organise their program's code. In fact it provides a way of separating user interface i.e View from the business logic i.e Model. A Controller is responsible for invoking appropriate pages according to user's request.
    [Show full text]
  • Roadmap and Strategy for Weblogic / Glassfish Server in the Cloud
    Roadmap and Strategy for WebLogic / GlassFish Server in the Cloud HUJAK Keynote Duško Vukmanovi ć FMW Principal Sales Consultant Oracle Obligatory Safe Harbor Statement 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. Program Agenda • WebLogic Server Roadmap • WebLogic Server Today / Tomorrow • GlassFish Server Roadmap • GlassFish Server Today / Tomorrow Oracle Cloud Application Foundation Complete & Integrated Modern Cloud Infrastructure Private Cloud Traffic Director/Web Tier WebLogic Coherence Tuxedo Server Deployment Public Cloud Cloud Application Foundation Roadmap WebLogic Server, Coherence and Fusion Middleware Dec 2011 Feb 2012 CY2013 CY 2013+ WebLogic Server 12c WebLogic Server 11g WebLogic Server 12c Java EE 7, Java SE 8, (12.1.1) + PS5 (10.3.6) + (12.1.2) + Cloud Coherence 3.7.1.1 Coherence 3.7.1.1 Coherence 12c (12.1.2) (12.1.3/12.1.4) • Pre-Fusion Middleware 12c • Fusion Middleware 11g PS5 • FMW Infrastructure w/ADF • SOA, ODI, WebCenter • Java EE 6 (11.1.1.6+) • Java SE 7 • Java EE 7 Reference • Java SE 6 and 7 • Java SE 6 and 7 • JDev , Eclipse, NetBeans Implementation and • Maven integration updates • JDev, OEPE, NetBeans • Upgradeability
    [Show full text]
  • Spring Boot Reference Documentation
    Spring Boot Reference Documentation Phillip Webb, Dave Syer, Josh Long, Stéphane Nicoll, Rob Winch, Andy Wilkinson, Marcel Overdijk, Christian Dupuis, Sébastien Deleuze, Michael Simons, Vedran Pavić, Jay Bryant, Madhura Bhave Table of Contents Legal. 1 1. Spring Boot Documentation. 2 1.1. About the Documentation. 2 1.2. Getting Help . 2 1.3. First Steps . 2 1.4. Working with Spring Boot . 2 1.5. Learning about Spring Boot Features . 3 1.6. Moving to Production . 3 1.7. Advanced Topics . 3 2. Getting Started . 4 2.1. Introducing Spring Boot . 4 2.2. System Requirements . 4 2.2.1. Servlet Containers. 4 2.3. Installing Spring Boot . 5 2.3.1. Installation Instructions for the Java Developer . 5 Maven Installation . 5 Gradle Installation . 7 2.3.2. Installing the Spring Boot CLI . 7 Manual Installation . 7 Installation with SDKMAN!. 8 OSX Homebrew Installation . 8 MacPorts Installation . 9 Command-line Completion . 9 Windows Scoop Installation . 9 Quick-start Spring CLI Example. 9 2.3.3. Upgrading from an Earlier Version of Spring Boot . 10 2.4. Developing Your First Spring Boot Application . 11 2.4.1. Creating the POM . 11 2.4.2. Adding Classpath Dependencies . 12 2.4.3. Writing the Code . 13 The @RestController and @RequestMapping Annotations . 14 The @EnableAutoConfiguration Annotation . 14 The “main” Method . 15 2.4.4. Running the Example. 15 2.4.5. Creating an Executable Jar . 15 2.5. What to Read Next . 17 3. Using Spring Boot . 19 3.1. Build Systems. 19 3.1.1. Dependency Management . 19 3.1.2. Maven .
    [Show full text]