Secure Coding Practices in Java: Challenges and Vulnerabilities∗

Total Page:16

File Type:pdf, Size:1020Kb

Secure Coding Practices in Java: Challenges and Vulnerabilities∗ Secure Coding Practices in Java: Challenges and Vulnerabilities∗ Na Meng Stefan Nagy Danfeng (Daphne) Yao Wenjie Zhuang Gustavo Arango Argoty Department of Computer Science Virginia Tech Blacksburg, Virginia {nm8247,snagy2,danfeng,kaito,gustavo1}@vt.edu ABSTRACT 1 INTRODUCTION The Java platform and its third-party libraries provide useful fea- The Java platform and third-party libraries (e.g., BouncyCastle [9]) tures to facilitate secure coding. However, misusing them can cost provide useful features to support secure coding. Misusing these developers time and effort, as well as introduce security vulnerabili- libraries and frameworks not only slows down code development, ties in software. We conducted an empirical study on StackOverflow but also leads to security vulnerabilities in software [19, 74, 80, 98]. posts, aiming to understand developers’ concerns on Java secure Prior research has mostly focused on the specific topics of mis- coding, their programming obstacles, and insecure coding practices. using cryptography and secure socket layer (SSL) APIs [23, 26, 29, We observed a wide adoption of the authentication and autho- 60, 72]. For example, Nadi et al. investigated the obstacles intro- rization features provided by Spring Security—a third-party frame- duced by Java cryptography APIs, developers’ usage of the APIs, work designed to secure enterprise applications. We found that and desired tool support [68]. Lazar et al. manually examined 269 programming challenges are usually related to APIs or libraries, published cryptographic vulnerabilities in the CVE database, and including the complicated cross-language data handling of cryptog- found that 83% of them were resulted from cryptography API mis- raphy APIs, and the complex Java-based or XML-based approaches use [60]. Fahl et al. [26] and Georgiev et al. [29] separately reported to configure Spring Security. In addition, we reported multiple se- vulnerable Android applications and software libraries that mis- curity vulnerabilities in the suggested code of accepted answers on use SSL APIs and demonstrated how these vulnerabilities cause the StackOverflow forum. The vulnerabilities included disabling man-in-the-middle attacks. Rahaman and Yao recently introduced the default protection against Cross-Site Request Forgery (CSRF) cryptographic program analysis (CPA) [72], which detects crypto- attacks, breaking SSL/TLS security through bypassing certificate graphic coding errors in C/C++ programs with static taint analysis. validation, and using insecure cryptographic hash functions. Our All these studies on improving cryptography and SSL coding secu- findings reveal the insufficiency of secure coding assistance and rity are timely and important. documentation, as well as the huge gap between security theory In this work, we conducted an in-depth investigation on Java and coding practices. secure coding problems. Our analysis is not limited to cryptography or SSL APIs. We inspected 503 StackOverflow (SO) posts that are CCS CONCEPTS related to Java security. The majority (87%) of the posts are about • General and reference → Empirical studies; non-crypto libraries. For each post, we thoroughly examined the entire thread, including the question and all the responses. We KEYWORDS chose StackOverflow [91] because (1) it is an extremely popular online platform for developers to share and discuss programming Secure coding, Spring Security, CSRF, SSL/TLS, certificate valida- issues and solutions, and (2) SO plays an important role in educating tion, cryptographic hash functions, authentication, authorization, developers and shaping their daily coding practices. StackOverflow, cryptography Our analysis was conducted at the code level, as code-level in- ACM Reference Format: vestigation has the potential to bring deeper insights. The technical Na Meng Stefan Nagy Danfeng (Daphne) Yao Wenjie Zhuang challenge is how to interpret the short and brief posts within the Gustavo Arango Argoty. 2018. Secure Coding Practices in Java: Chal- appropriate programming context in order to understand the security ICSE ’18: ICSE ’18: 40th International Conference lenges and Vulnerabilities. In impact. To comprehend each post’s program context, we studied the on Software Engineering , May 27-June 3, 2018, Gothenburg, Sweden. ACM, context related to the source code, configuration files, and execution New York, NY, USA, 12 pages. https://doi.org/10.1145/3180155.3180201 environments. We aimed to identify the root causes and solutions ∗This work was supported by NSF Grant CCF-1565827 and ONR Grant N00014-17-1- of each problem. To comprehend each post’s security context, we 2498. inferred developers’ implementation intents from their problem descriptions and the involved security libraries. We also leveraged Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed our security expertise to assess whether the accepted solutions for profit or commercial advantage and that copies bear this notice and the full citation fulfilled their original intents. These analysis and reasoning tasks on the first page. Copyrights for components of this work owned by others than ACM require expertise in both software engineering and cyber security. must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a In our analysis of the 503 StackOverflow posts, we investigated fee. Request permissions from [email protected]. the following three research questions (RQs): ICSE ’18, May 27-June 3, 2018, Gothenburg, Sweden © 2018 Association for Computing Machinery. RQ1 What are the common concerns in Java secure coding? We ACM ISBN 978-1-4503-5638-1/18/05...$15.00 https://doi.org/10.1145/3180155.3180201 aimed to identify the libraries and functionalities (e.g., [3, ICSE ’18, May 27-June 3, 2018, Gothenburg, Sweden N. Meng et al. 32, 45, 47, 69, 85]) that were most frequently asked about 2 BACKGROUND by developers. Our scope covers all topics related to Java The examined posts cover three topics on Java security: Java plat- security, not limited to cryptography and SSL. form security, Java EE security, and third-party frameworks. This RQ2 What are the common programming challenges? We aimed section introduces the key terminologies used throughout the paper. to identify the common obstacles that hinder secure cod- ing. Such information can provide software engineering re- 2.1 Java Platform Security searchers actionable insights for designing tools and help The platform defines APIs spanning major security areas, including close the gap between correct API usage and the practice. cryptography, access control, and secure communication [54]. The RQ3 What are the common security vulnerabilities? The high popu- Java Cryptography Architecture (JCA) contains APIs for crypto- larity of StackOverflow may cause insecure code to be shared graphic hashes, keys and certificates, digital signatures, and and used in real-world implementations. This effort helps encryption [47]. Nine cryptographic engines are defined to pro- raise the security awareness among software developers. vide either cryptographic operations (encryption, digital signatures, Our work provides empirical evidences for many significant hashes), generators or converters of cryptographic material (keys secure coding issues that have not been previously reported. The and algorithm parameters), or objects (keystores or certificates) that major findings are summarized as follows. encapsulate the cryptographic data. The access control architecture • There were security vulnerabilities in the recommended code protects the access to sensitive resources (e.g., local files) or sensi- of some accepted answers. For example, when encountering tive application code (e.g., methods in a class). All access control errors during implementing Spring Security authentication, decisions are mediated by a security manager. By default, the developers were suggested a workaround to disable the de- security manager uses the AccessController class for access control fault security protection against Cross-Site Request Forgery operations and decisions. Secure communication ensures that the (CSRF) attacks. Also for example, some posts advised devel- data traveling across a network is sent to the appropriate party, opers to trust all incoming SSL/TLS certificates as a fix to cer- without being modified during the transmission. The Java platform tificate verification errors. Such a setup completely destroys provides API support for standard secure communication protocols the security guarantees of SSL/TLS. Although this insecure like SSL/TLS. HTTPS, or “HTTP secure”, is an application-specific practice was reported by security researchers in 2012 [26, 29], implementation that is a combination of HTTP and SSL/TLS. some SO users still view this option as acceptable. In addi- tion, MD5 or SHA-1 algorithms was repeatedly suggested, 2.2 Java EE Security even though these cryptographic hashing algorithms are Java EE is a standard specification for enterprise Java extensions [59]. weak and should not be used for hashing passwords. For the Various application servers are built to implement this specification, 17 problematic posts (5 on CSRF, 9 on SSL/TLS, and 3 on such as JBoss or WildFly [104], Glassfish [31], WebSphere [101], 1 password hashing), the total view count is 622,922
Recommended publications
  • Spring Roo - Reference Documentation
    Spring Roo - Reference Documentation DISID CORPORATION S.L. Table of Contents Getting started . 1 1. Overview . 2 2. What’s new in Spring Roo 2.0 . 3 Improved extensibility . 3 No backward compatibility . 3 Usability improvements . 3 Centered in Spring technologies . 3 Application architecture . 4 Domain model . 4 View layer . 4 3. Requirements . 6 4. Install Spring Roo . 7 Using Spring Roo . 9 5. The Roo shell . 10 6. Impatient beginners . 12 7. Create your Spring Boot application . 13 8. Configure the project settings . 14 9. Setup the persistence engine . 15 10. The domain model . 16 JPA entities . 16 DTOs . 20 11. The data access layer . 21 Spring Data repositories . 21 Default queries . 21 12. The service layer . 22 Service API and Impl . 22 13. The view layer . 23 Thymeleaf view engine . 23 Spring MVC Controllers . 23 Spring Webflow . 25 14. The integration layer . 26 REST API . 26 WS API . 26 Email . ..
    [Show full text]
  • Course Title
    "Charting the Course ... ... to Your Success!" Spring 3x Advanced Topics Course Summary Description This course is the next step in using the many features Spring 3.x has to offer. Web topics covering Web Flow and MVC address the powerful features for building popular workflow structures in applications today. Spring Batch addresses the Web counterpart to business processing. The final two topics address all areas in Spring. Security touches all layers of a business application. The newly rewritten Spring Security structure covers all areas addressed down to the Method level. Spring Roo is the last topic that can be used to build entire applications, including Spring MVC. Due to the size of Spring Roo, the depth will depend on available remaining time. The various Spring Integration features of messages will be demonstrated based on student requirements. Objectives At the end of this course, students will be able to: Design, create and debug Spring MVC applications. Understand Web Flow and where it can be used. Create, monitor, and test Spring Batch applications. Apply Security to all levels of Spring applications, including methods. Use Spring Roo to create Spring applications. Configure Spring using Java Classes. Apply Spring Integration options. Topics Working with Spring Web Flow Introducing Spring Security The Web Module and Spring MFC Web Security Controllers and Commands Securing the Service Layer Binding and Validation Customizing and Extending Spring Security Introducing Spring Batch Working with Remote Services
    [Show full text]
  • Adding Red Hat Decision Manager Users 44
    Red Hat Decision Manager 7.11 Integrating Red Hat Decision Manager with other products and components Last Updated: 2021-07-06 Red Hat Decision Manager 7.11 Integrating Red Hat Decision Manager with other products and components 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.
    [Show full text]
  • Spring Framework II Course Summary
    "Charting the Course ... ... to Your Success!" Spring Framework II Course Summary Description This course is the next step in using the many features the Spring Framework has to offer. In depth Web topics covering Web Flow and MVC address the powerful features for building popular workflow structures in applications. Spring Security will be applied to all areas including the Method level. Spring ROO will be used to build entire applications, including Spring MVC. Web Services for SOAP and RESTful are included to complete the Web Tier. Objectives At the end of this course, students will be able to: Design, create and debug complex Spring MVC applications. Understand Web Flow and where it can be used. Create, monitor, and test Spring Web Services. Apply Security to all levels of Spring Framework applications, including methods. Use Spring Roo to create Spring Framework applications. Configure Spring Framework using Java Classes and eliminate Web.XML configuration. Incorporate JQuery and JavaServer Faces. Topics Web Development Spring Roo Web Services What’s Next in Spring III Security Audience This course is designed for Developers who have attended the “Spring Framework I” class or equivalent experience in developing or maintaining Spring Framework Web applications. Prerequisites Spring programming experience, a basic knowledge of configuration, familiarity with the Spring Framework dependency injection, and Aspect oriented programming. Duration Five Days Due to the nature of this material, this document refers to numerous hardware and software products by their trade names. References to other companies and their products are for informational purposes only, and all trademarks are the properties of their respective companies.
    [Show full text]
  • Spring Security Reference
    Spring Security Reference 4.2.8.RELEASE Ben Alex , Luke Taylor , Rob Winch , Gunnar Hillert Copyright © 2004-2015 Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically. Spring Security Reference Table of Contents .............................................................................................................................................. xvii I. Preface ................................................................................................................................... 1 1. Getting Started ............................................................................................................... 3 2. Introduction .................................................................................................................... 4 2.1. What is Spring Security? ..................................................................................... 4 2.2. History ................................................................................................................ 6 2.3. Release Numbering ............................................................................................. 6 2.4. Getting Spring Security ........................................................................................ 7 Usage with Maven ............................................................................................
    [Show full text]
  • Spring Security
    Spring Security Reference Documentation Ben Alex Luke Taylor Spring Security: Reference Documentation by Ben Alex and Luke Taylor 3.0.8.RELEASE Spring Security Table of Contents Preface ...................................................................................................................................... x I. Getting Started ....................................................................................................................... 1 1. Introduction ................................................................................................................... 2 1.1. What is Spring Security? ..................................................................................... 2 1.2. History ................................................................................................................ 4 1.3. Release Numbering ............................................................................................. 4 1.4. Getting Spring Security ....................................................................................... 5 Project Modules ................................................................................................. 5 Core - spring-security-core.jar .................................................. 5 Web - spring-security-web.jar ..................................................... 5 Config - spring-security-config.jar ........................................... 5 LDAP - spring-security-ldap.jar ................................................ 5 ACL - spring-security-acl.jar
    [Show full text]
  • SAP Process Mining by Celonis
    TABLE OF CONTENTS REVISION HISTORY 4 INTRODUCTION 5 ABOUT THIS GUIDE 5 TARGET AUDIENCE 5 TECHNICAL CONFIGURATION – SYSTEM LANDSCAPE 8 SINGLE-SERVER DEPLOYMENT 8 MULTI-SERVER DEPLOYMENT (SCALE-OUT) 9 TECHNICAL CONFIGURATION – FILE SYSTEM LAYOUT 9 WINDOWS SYSTEMS 10 LINUX SYSTEMS 12 TECHNICAL CONFIGURATION – MULTI-SERVER 13 TECHNICAL CONFIGURATION – SECURITY 15 GENERAL SECURITY 15 SECURE COMMUNICATION BETWEEN CENTRAL APPLICATION AND COMPUTE SERVICE 17 PYTHON SECURITY 18 TECHNICAL CONFIGURATION – HIGH AVAILABILITY (HA) 19 TECHNICAL CONFIGURATION – LOGGING 21 LOGGING FOR SAP PROCESS MINING BY CELONIS 21 APPLICATION SERVER ADMINISTRATION 24 REQUIRED TOOLS 24 SAP PROCESS MINING BY CELONIS CONFIGURATION 24 SAP PROCESS MINING BY CELONIS AS OPERATING SYSTEM SERVICE 25 PERIODICAL TASKS – ARCHIVING FILES 26 SAP PROCESS MINING BY CELONIS LOG FILES 26 MIGRATION FROM SAP PROCESS MINING BY CELONIS FROM A VERSION BELOW 4.5 TO A VERSION INCLUDING AND ABOVE 4.5 30 SAP PROCESS MINING BY CELONIS CONFIGURATION STORE BACKUPS 32 © 2020 Celonis SE OPERATION GUIDE 2 RECOVERING FROM A BACKUP FOR INTEGRATED CELONIS CONFIGURATION STORE 33 BACKUP AND RECOVERY – BACKUP ANALYTICS DATABASE (SAP HANA) 34 INCLUDED MONITORING FUNCTIONALITY 35 SOFTWARE CHANGE MANAGEMENT 38 SOFTWARE UPDATE PROCEDURE 39 SUPPORT DESK MANAGEMENT 40 SLD REGISTRATION 40 CONFIGURABLE HELP PAGES 40 © 2020 Celonis SE OPERATION GUIDE 3 REVISION HISTORY VERSION NUMBER VERSION DATE SUMMARY OF REVISIONS MADE 1.4 MAR 22, 2017 Application Version 4.2 1.6 FEB 23, 2018 Updated version for application version 4.3 1.9 FEB 03, 2019 Updated version for application version 4.5 1.10 MAY 17, 2020 Updated version for application version 4.5 SP3 1.11 JUN 20, 2020 Updated version for application version 4.6 © 2020 Celonis SE OPERATION GUIDE 4 INTRODUCTION ABOUT THIS GUIDE SAP Process Mining by Celonis is a powerful software for retrieving, visualizing and analyzing real as-is business processes from transactional data stored by the SAP ERP systems.
    [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]
  • Secure Coding Practices in Java: Challenges and Vulnerabilities
    Secure Coding Practices in Java: Challenges and Vulnerabilities Na Meng Stefan Nagy Daphne Yao Wenjie Zhuang Gustavo Arango Argoty Virginia Tech Blacksburg, Virginia 24060 {nm8247,snagy2,danfeng,kaito,gustavo1}@vt.edu ABSTRACT 1 INTRODUCTION Java platform and third-party libraries provide functionalities to fa- Java platform and third-party libraries or frameworks (e.g., Boun- cilitate secure coding. However, misusing these functionalities can cyCastle [6]) provide various features to enable secure coding. Mis- cost developers tremendous time and effort, or introduce security using these libraries and frameworks not only slows development vulnerabilities in software. Prior research focused on the misuse of time, but also leads to security vulnerabilities in the resulting soft- cryptography and SSL APIs, but did not explore the fundamental re- ware [14, 98, 99, 103]. search question: what are the biggest challenges and vulnerabilities Prior research mainly focused on cryptography and SSL API in secure coding practices? In this paper, we conducted a broader misuse causing security vulnerabilities [80, 82, 85, 88]. Specifically, empirical study on StackOverflow posts to understand developers’ Lazar et al. manually examined 269 published cryptographic vul- concerns on Java secure coding, their programming obstacles, and nerabilities in the CVE database, and observed 83% of them resulted the potential vulnerabilities in their code. from cryptography API misuse [88]. Nadi et al. further investigated We observed that developers have shifted their effort to the usage the obstacles introduced by Java cryptography APIs, developers’ of authentication and authorization features provided by Spring usage of the APIs, and desired tool support [94]. Fahl et al. [82] and Security—a third-party framework designed to secure enterprise Georgiev et al.
    [Show full text]
  • Spring Roo in Action by Ken Rimple, Srini Penchikala
    MANNING Ken Rimple Srini Penchikala FOREWORD BY BEN ALEX Spring Roo in Action by Ken Rimple, Srini Penchikala Chapter 10 Copyright 2012 Manning Publications brief contents PART 1STARTING SPRING APPS RAPIDLY WITH ROO...................1 1 ■ What is Spring Roo? 3 2 ■ Getting started with Roo 25 PART 2DATABASES AND ENTITIES ........................................... 55 3 ■ Database persistence with entities 57 4 ■ Relationships, JPA, and advanced persistence 93 PART 3WEB DEVELOPMENT...................................................125 5 ■ Rapid web applications with Roo 127 6 ■ Advanced web applications 156 7 ■ RIA and other web frameworks 173 8 ■ Configuring security 189 PART 4INTEGRATION ...........................................................209 9 ■ Testing your application 211 10 ■ Enterprise services—email and messaging 243 11 ■ Roo add-ons 266 12 ■ Advanced add-ons and deployment 296 vii viii BRIEF CONTENTS PART 5 ROO IN THE CLOUD...................................................321 13 ■ Cloud computing 323 14 ■ Workflow applications using Spring Integration 337 Enterprise services— email and messaging This chapter covers Roo support for enterprise services Asynchronous messaging using a JMS topic Email service Asynchronous messaging using a JMS queue Monitoring messaging activity In the previous two chapters, you secured your Roo application by adding the Spring Security API to the application architecture mix, and you learned how to enrich the web tier of the Roo application so it’s functional from a business stand­ point. In addition to robust security features and a rich user interface, a real-world application also requires services such as customer email notification and offline data processing that occurs outside of your main business operations, where your customers receive notifications about results at a later time. In this chapter, we discuss the integration that the Roo framework provides for email and asynchronous messaging using the Java Message Service (JMS) API.
    [Show full text]
  • Spring Security Reference
    Spring Security Reference 4.2.6.RELEASE Ben Alex , Luke Taylor , Rob Winch , Gunnar Hillert Copyright © 2004-2015 Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically. Spring Security Reference Table of Contents .............................................................................................................................................. xvii I. Preface ................................................................................................................................... 1 1. Getting Started ............................................................................................................... 3 2. Introduction .................................................................................................................... 4 2.1. What is Spring Security? ..................................................................................... 4 2.2. History ................................................................................................................ 6 2.3. Release Numbering ............................................................................................. 6 2.4. Getting Spring Security ........................................................................................ 7 Usage with Maven ............................................................................................
    [Show full text]
  • CELEBRATING JAVA@25 the Everlasting Age of “Write Once, Run
    The Everlasting Age of “Write Once, Run Anywhere” CELEBRATING JAVA@25 Your App Ecosystem | Driven by Java | Accelerated with Low-Code Copyright © 2020, WaveMaker, Inc. This document is not for public distribution. All rights reserved. Abstract It takes a second to sow a seed, years to create a forest, and decades to build an ecosystem. Witnessing the Java community grow everyday is a fascinating experience in itself. Many of us have lived through the launch and wide-spread adoptionof Java and we continue to witness its evolution. 25 years ago, James Gosling and others at Sun Microsystems launched the Java programming language in 1995. The driving force behind creating Java was to build an architecture-neutral, platform-independent language for software embedded in electronic devices. Since then it has evolved into an ecosystem, from the Java Virtual Machine (JVM) to Jakarta EE (Java EE). To keep up with enterprise demands, the new focus of the Java ecosystem is on cloud computing with the aim of providing complete control and flexibility to accelerate application development in the cloud. Enriched layer upon layer, Java as a language has evolved over the decades and has created a special connection with many professional developers. In this eBook, find out how Java is shaping the present and future technology, how it has evolved, the applications of Java and why it is popular, and how it forms the backbone of modern applications and is used to meet the modern enterprise demands. Copyright © 2020, WaveMaker, Inc. This document is not for public distribution. All rights reserved. Table of Contents Introduction 1 How Java is shaping present and future technology Java is still young @25 2 The Evolution Over the Decades 3 Applications of Java and Why it is Popular 4 Combine the Old with New Technology Meet the Demands of the Modern Enterprise 5 The Future of Java and How it is Evolving Copyright © 2020, WaveMaker, Inc.
    [Show full text]