DOCSLIB.ORG

EM Open Source and Third Party Documentation 15.3 2021R3

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
EM Open Source and Third Party Documentation 15.3 2021R3 Engagement Management Open Source and Third-Party Documentation Case Management Enterprise & Knowledge Management Enterprise Release 15.3 2021R3 July 2021 Verint.com Twitter.com/verint Facebook.com/verint Blog.verint.com Unauthorised use, duplication, or modification of this document in whole or in part without the written consent of Verint Systems Inc. is strictly prohibited. By providing this document, Verint Systems Inc. is not making any representations regarding the correctness or completeness of its contents and reserves the right to alter this document at any time without notice. Features listed in this document are subject to change. Contact your Verint representative for current product features and specifications. All marks referenced herein with the ® or TM symbol are registered trademarks or trademarks of Verint Systems Inc. or its subsidiaries. All rights reserved. All other marks are trademarks of their respective owners. © 2021 Verint Systems Inc. All rights reserved worldwide. Table of Contents Open Source Attribution ............................................................................................. 1 Product Description ................................................................................................ 1 Unauthorised use, duplication, or modification of this document in whole or in part without the written consent of Verint Systems Inc. is strictly prohibited. By providing this document, Verint Systems Inc. is not making any representations regarding the correctness or completeness of its contents and reserves the right to alter this document at any time without notice. Features listed in this document are subject to change. Contact your Verint representative for current product features and specifications. All marks referenced herein with the ® or TM symbol are registered trademarks or trademarks of Verint Systems Inc. or its subsidiaries. All rights reserved. All other marks are trademarks of their respective owners. © 2021 Verint Systems Inc. All rights reserved worldwide. Open Source Attribution Certain components of this Software or software contained in this Product (collectively, “Software”) may be covered by so-called “free or open source” software licenses (“Open Source Components”), which includes any software licenses approved as open source licenses by the Open Source Initiative or any similar licenses, including without limitation any license that, as a condition of distribution of the Open Source Components licensed, requires that the distributor make the Open Source Components available in source code format. A license in each Open Source Component is provided to you in accordance with the specific license terms specified in their respective license terms. EXCEPT WITH REGARD TO ANY WARRANTIES OR OTHER RIGHTS AND OBLIGATIONS EXPRESSLY PROVIDED DIRECTLY TO YOU FROM VERINT, ALL OPEN SOURCE COMPONENTS ARE PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. Any third party technology that may be appropriate or necessary for use with the Verint Product is licensed to you only for use with the Verint Product under the terms of the third party license agreement specified in the Documentation, the Software or as provided online at https://www.verint.com/utilities/third-party-license/index.html . You may not take any action that would separate the third-party technology from the Verint Product. Unless otherwise permitted under the terms of the third-party license agreement, you agree to only use the third party technology in conjunction with the Verint Product. The following Open Source Components may be included with this Software, with ownership in those components as indicated in the third-party license library: • 1to2 is licensed under MIT 1to2 • abbrev is licensed under ISC abbrev • accepts is licensed under MIT accepts • activation is licensed under CDDL v 1.0 • activeio-core-3.1.4 is licensed under Apache License, Version 2.0 • activemq-client-5.9.0 is licensed under Apache License, Version 2.0 • azure-activedirectory-library-for-java is licensed under MIT adal4j • agent-base is licensed under MIT agent-base • agentkeepalive is licensed under MIT agentkeepalive • aggregate-error is licensed under MIT sindresorhus • ajv is licensed under MIT ajv • Alchemy is licensed under Apache License, Version 2.0 • Alef is licensed under Alef SIL Open Font License Version 1.1 • align-text is licensed under MIT sindresorhus • ambi is licensed under MIT Bevry (1) • amdefine is licensed under BSD amdefine • amqp-client is licensed under Apache License, Version 2.0 • ansi-align is licensed under ISC ansi-align • ansicolors is licensed under MIT ansicolors • ansi-regex is licensed under MIT sindresorhus • ansistyles is licensed under MIT ansistyles Page 1 • ansi-styles is licensed under MIT sindresorhus • ant is licensed under Apache License, Version 2.0 • ant-jmeter is licensed under Apache License, Version 2.0 • ant-launcher is licensed under Apache License, Version 2.0 • ANTLR 2 is licensed under Public Domain • ANTLR 3 is licensed under BSD ANTLR 3 • ANTLR 4 is licensed under BSD ANTLR 4 • AOP Alliance is licensed under Public Domain • Apache BSF is licensed under Apache License, Version 2.0 • Apache Commons Email 1.2 is licensed under Apache License, Version 2.0 • Apache Commons FileUpload 1.3.1 is licensed under Apache License, Version 2.0 • Apache Commons Lang 2.4 is licensed under Apache License, Version 2.0 • Apache Commons Lang 3.4 is licensed under Apache License, Version 2.0 • Apache HTTP Components Client is licensed under Apache License, Version 2.0 • Apache HTTP Components Client 4.5.1 is licensed under Apache License, Version 2.0 • Apache HTTP Components Core 4.4.4 is licensed under Apache License, Version 2.0 • Apache HTTP Components Core 4.4.14 is licensed under Apache License, Version 2.0 • Apache mime4j is licensed under Apache License, Version 2.0 • Apache Neethi is licensed under Apache License, Version 2.0 • Apache Oltu is licensed under Apache License, Version 2.0 • Apache Soap is licensed under Apache License, Version 2.0 • Apache Santuario is licensed under Apache License, Version 2.0 • Apache XML Graphics Commons is licensed under Apache License, Version 2.0 • append-transform is licensed under MIT James Talmage • aproba is licensed under ISC aproba • archy is licensed under MIT • are-we-there-yet is licensed under ISC are-we-there-yet • argparse is licensed under MIT argparse • argparse4j is licensed under MIT argparse4j • Arimo is licensed under Apache License, Version 2.0 • array-flatten is licensed under MIT array-flatten • array-uniq is licensed under MIT sindresorhus • array-unique is licensed under MIT Jon Schlinkert (2) • arr-diff is licensed under MIT Jon Schlinkert (3) • arr-flatten is licensed under MIT Jon Schlinkert (3) • arrify is licensed under MIT sindresorhus • arr-union is licensed under MIT Jon Schlinkert (2) • asap is licensed under MIT asap Page 2 • ASM is licensed under ASM License • ASM Commons is licensed under ASM License • ASM Static Analysis is licensed under ASM License • ASM Tree class visitor is licensed under ASM License • ASM Utilities is licensed under ASM License • ASM-4.1 is licensed under ASM License • asn1 is licensed under MIT asn1 • AspectJ is licensed under Eclipse Public License, Version 1.0 • assert-plus is licensed under MIT assert-plus • assign-symbols is licensed under MIT sindresorhus • Asterisk-Java is licensed under Apache License, Version 2.0 • async is licensed under MIT async • asynckit is licensed under MIT asynckit • atob is licensed under Apache License, Version 2.0 • attoparser is licensed under Apache License, Version 2.0 • attributes-binder is licensed under Apache License, Version 2.0 • avatica-core is licensed under Apache License, Version 2.0 • aws4 is licensed under MIT aws4 • aws-sign2 is licensed under Apache License, Version 2.0 • axiom is licensed under Apache License, Version 2.0 • axios is licensed under MIT axios • Axis is licensed under Apache License, Version 2.0 • Axis2 is licensed under Apache License, Version 2.0 • Axis-saaj is licensed under Apache License, Version 2.0 • b64u is licensed under MIT b64u • babel-code-frame is licensed under MIT babel • babel-generator is licensed under MIT babel • babel-messages is licensed under MIT babel • babel-runtime is licensed under MIT babel • babel-template is licensed under MIT babel • babel-traverse is licensed under MIT babel • babel-types is licensed under MIT babel • babylon is licensed under MIT babylon • backport-util-concurrent is licensed under Public Domain • balanced-match is licensed under MIT balanced-match • base is licensed under MIT Jon Schlinkert (1) • base64-js is licensed under MIT base64js • base64url is licensed under MIT base64url Page 3 • Batik is licensed under Apache License, Version 2.0 • bcpkix-jdk15on is licensed under Bouncy Castle License • bcprov-jdk15on-1.55 is licensed under Bouncy Castle License • bcrypt-pbkdf is licensed under BSD bcrypt-pbkdf • bind-obj-methods is licensed under ISC Isaac Z. Schlueter and Contributors • bin-links is licensed under Artistic-2.0 npm • bintrees is licensed under MIT bintrees • block-stream is licensed under ISC Isaac Z. Schlueter and Contributors • bluebird is licensed under MIT bluebird • body-parser is licensed under MIT body-parser • boilerpipe is licensed under Apache License, Version 2.0 • boom is licensed under BSD boom • Bouncy Castle is licensed
Load more

Recommended publications
  • Security in Cloud Computing a Security Assessment of Cloud Computing Providers for an Online Receipt Storage
    Security in Cloud Computing A Security Assessment of Cloud Computing Providers for an Online Receipt Storage Mats Andreassen Kåre Marius Blakstad Master of Science in Computer Science Submission date: June 2010 Supervisor: Lillian Røstad, IDI Norwegian University of Science and Technology Department of Computer and Information Science Problem Description We will survey some current cloud computing vendors and compare them to find patterns in how their feature sets are evolving. The start-up firm dSafe intends to exploit the promises of cloud computing in order to launch their business idea with only marginal hardware and licensing costs. We must define the criteria for how dSafe's application can be sufficiently secure in the cloud as well as how dSafe can get there. Assignment given: 14. January 2010 Supervisor: Lillian Røstad, IDI Abstract Considerations with regards to security issues and demands must be addressed before migrating an application into a cloud computing environment. Different vendors, Microsoft Azure, Amazon Web Services and Google AppEngine, provide different capabilities and solutions to the individual areas of concern presented by each application. Through a case study of an online receipt storage application from the company dSafe, a basis is formed for the evaluation. The three cloud computing vendors are assessed with regards to a security assessment framework provided by the Cloud Security Alliance and the application of this on the case study. Finally, the study is concluded with a set of general recommendations and the recommendation of a cloud vendor. This is based on a number of security as- pects related to the case study’s existence in the cloud.
    [Show full text]
  • Open Cloud Computing with the Simple Cloud API and Apache Libcloud Doug Tidwell Cloud Computing Evangelist, IBM [email protected]
    Open Cloud Computing with the Simple Cloud API and Apache libcloud Doug Tidwell Cloud Computing Evangelist, IBM [email protected] Session 7665 Agenda • Portability and interoperability • A few words about APIs • The Simple Cloud API • Storage • Queues • Documents • Controlling VMs with Apache libcloud • Resources / Next steps The problem Vendor lock-in • If there’s a new technology, any talented programmer will want to use it. • Maybe the shiny new thing is appropriate for what we’re doing. • Maybe not. • We’re probably going to use it anyway. • The challenge is to walk the line between using the newest, coolest thing and avoiding vendor lock-in. Portability and Interoperability • In writing flexible code for the cloud, there are two key concepts: • Portability is the ability to run components or systems written for one cloud provider in another cloud provider’s environment. • Interoperability is the ability to write one piece of code that works with multiple cloud providers, regardless of the differences between them. How standards work • For a standards effort to work, three things have to happen: • The standard has to solve a common problem in an elegant way. • The standard has to be implemented consistently by vendors. • Users have to insist that the products they use implement the standard. How standards work • All three things have to happen. • If the standard doesn't solve a common problem, or if it solves it in an awkward way, the standard fails. • If the standard isn't implemented by anyone, the standard fails. • If customers buy and use products even though they don't implement the standard, the standard fails.
    [Show full text]
  • Software As a Service
    Software as a Service Haojie Hang Ogheneovo Dibie Executive Summary • In this presentation, we go through the Software as a Service Methodology, examine its benefits and drawbacks and talk about two state-of-art SaaS systems– Amazon Web Service and Google App Engine • We also look into Service Oriented Architecture powering SaaS applications and its impact on modern web 2.0 applications • Finally, we examine hybrids of traditional and SaaS applications Overview • What is Software as a Service (SaaS) • Background o Brief history o Concept o Big picture o Related terms • Computing Today o SasS is everywhere o The SaaS Market • Benefits of SaaS • Drawbacks of SaaS o Robustness o Privacy o Security o Reliability • Service Oriented Architectures (SOA) o Guiding principles of SOA • Case studies o Amazon Web Services (AWS) o Google App Engine • Influence of SOA on Web 2.0 development o Zend Framework • Hybrids of Traditional and SaaS applications o Dropbox o Microsoft Office • Summary • References What is SaaS? • Definition: Software as a Service (SaaS), a.k.a. on- demand software, is a software delivery model in which software and its associated data are hosted centrally and accessed using a thin-client, usually a web browser over the internet. – Wikipedia • Simply put, SaaS is a method for delivering software that provides remote access to software as a web- based service. The software service can be purchased with a monthly fee and pay as you go. What is SaaS? • Where does the term SaaS come from? o The SAAS acronym allegedly first appeared
    [Show full text]
  • Project Dependencies Project Transitive Dependencies
    9/8/2020 Dependencies – Project Dependencies Project Dependencies compile The following is a list of compile dependencies for this project. These dependencies are required to compile and run the application: GroupId ArtifactId Version Type Licenses org.onap.policy.drools-pdp base 1.7.1-SNAPSHOT tar.gz - org.onap.policy.drools-pdp feature-active-standby-management 1.7.1-SNAPSHOT zip - org.onap.policy.drools-pdp feature-controller-logging 1.7.1-SNAPSHOT zip - org.onap.policy.drools-pdp feature-distributed-locking 1.7.1-SNAPSHOT zip - org.onap.policy.drools-pdp feature-eelf 1.7.1-SNAPSHOT zip - org.onap.policy.drools-pdp feature-healthcheck 1.7.1-SNAPSHOT zip - org.onap.policy.drools-pdp feature-lifecycle 1.7.1-SNAPSHOT zip - org.onap.policy.drools-pdp feature-mdc-filters 1.7.1-SNAPSHOT zip - org.onap.policy.drools-pdp feature-pooling-dmaap 1.7.1-SNAPSHOT zip - org.onap.policy.drools-pdp feature-session-persistence 1.7.1-SNAPSHOT zip - org.onap.policy.drools-pdp feature-state-management 1.7.1-SNAPSHOT zip - org.onap.policy.drools-pdp feature-test-transaction 1.7.1-SNAPSHOT zip - org.onap.policy.drools-pdp policy-management 1.7.1-SNAPSHOT zip - Project Transitive Dependencies The following is a list of transitive dependencies for this project. Transitive dependencies are the dependencies of the project dependencies. compile The following is a list of compile dependencies for this project. These dependencies are required to compile and run the application: GroupId ArtifactId Version Classifier Type Licenses antlr antlr 2.7.7 - jar BSD License
    [Show full text]
  • Jakarta Enhancement Guide (V6.0) Table of Contents
    Jakarta Enhancement Guide (v6.0) Table of Contents Maven . 3 Ant . 5 Command Line . 7 Runtime Enhancement . 9 Programmatic API . 10 Enhancement Contract Details . 11 Persistable . 11 Byte-Code Enhancement Myths . 12 Cloning of enhanced classes . 12 Serialisation of enhanced classes. 12 Decompilation. 13 DataNucleus requires that all Jakarta entities implement Persistable and Detachable. Rather than requiring that a user add this themself, we provide an enhancer that will modify your compiled classes to implement all required methods. This is provided in datanucleus-core.jar. • The use of this interface means that you get transparent persistence, and your classes always remain your classes; ORM tools that use a mix of reflection and/or proxies are not totally transparent. • DataNucleus' use of Persistable provides transparent change tracking. When any change is made to an object the change creates a notification to DataNucleus allowing it to be optimally persisted. ORM tools that dont have access to such change tracking have to use reflection to detect changes. The performance of this process will break down as soon as you read a large number of objects, but modify just a handful, with these tools having to compare all object states for modification at transaction commit time. • OpenJPA requires a similar bytecode enhancement process also, and EclipseLink and Hibernate both allow it as an option since they also now see the benefits of this approach over use of proxies and reflection. In the DataNucleus bytecode enhancement contract there are 3 categories of classes. These are Entity, PersistenceAware and normal classes. The Meta-Data (XML or annotations) defines which classes fit into these categories.
    [Show full text]
  • Licensing Information User Manual Release 21C (21.1) F37966-01 March 2021
    Oracle® Zero Downtime Migration Licensing Information User Manual Release 21c (21.1) F37966-01 March 2021 Introduction This Licensing Information document is a part of the product or program documentation under the terms of your Oracle license agreement and is intended to help you understand the program editions, entitlements, restrictions, prerequisites, special license rights, and/or separately licensed third party technology terms associated with the Oracle software program(s) covered by this document (the "Program(s)"). Entitled or restricted use products or components identified in this document that are not provided with the particular Program may be obtained from the Oracle Software Delivery Cloud website (https://edelivery.oracle.com) or from media Oracle may provide. If you have a question about your license rights and obligations, please contact your Oracle sales representative, review the information provided in Oracle’s Software Investment Guide (http://www.oracle.com/us/ corporate/pricing/software-investment-guide/index.html), and/or contact the applicable Oracle License Management Services representative listed on http:// www.oracle.com/us/corporate/license-management-services/index.html. Licensing Information Third-Party Notices and/or Licenses About the Third-Party Licenses The third party licensing information in Oracle Database Licensing Information User Manual, Third-Party Notices and/or Licenses and Open Source Software License Text, applies to Oracle Zero Downtime Migration. The third party licensing information included in the license notices provided with Oracle Linux applies to Oracle Zero Downtime Migration. Open Source or Other Separately Licensed Software Required notices for open source or other separately licensed software products or components distributed in Oracle Zero Downtime Migration are identified in the following table along with the applicable licensing information.
    [Show full text]
  • Diverted Derived Design
    Diverted Derived Design Table of Contents Introduction 0 Motivations 1 Licenses 2 Design (as a) process 3 Distributions 4 Economies 5 Propositions 6 This book 7 Glossary 8 2 Diverted Derived Design Introduction The term open source is becoming popular among product designers. We see websites and initiatives appear with a lot of good intentions but sometimes missing the point and often creating confusion. Design magazines and blogs are always rushing into calling an openly published creation open source but rarely question the licenses or provide schematics or design files to download. We are furniture designers, hackers and artists who have been working with free/libre and open source software for quite some time. For us, applying these prirciples to product design was a natural extension, providing new areas to explore. But we also realized that designers coming to this with no prior open source experience had a lot of information to grasp before getting a clear picture of what could be open source product design. So we set ourselves to mobilize our knowledge in this book. We hope that this tool can be a base for teaching and learning about open source product design; a collective understanding of what one should know today to get started and join the movement; a reference students, amateurs and educators can have in their back pocket when they go out to explain what they are passionate about. How to read this book We have divided this book in sections that make sense for us. Each of these tries to address what we think is a general question you might have about open source product design.
    [Show full text]
  • Cloud Computing Bible Is a Wide-Ranging and Complete Reference
    A thorough, down-to-earth look Barrie Sosinsky Cloud Computing Barrie Sosinsky is a veteran computer book writer at cloud computing specializing in network systems, databases, design, development, The chance to lower IT costs makes cloud computing a and testing. Among his 35 technical books have been Wiley’s Networking hot topic, and it’s getting hotter all the time. If you want Bible and many others on operating a terra firma take on everything you should know about systems, Web topics, storage, and the cloud, this book is it. Starting with a clear definition of application software. He has written nearly 500 articles for computer what cloud computing is, why it is, and its pros and cons, magazines and Web sites. Cloud Cloud Computing Bible is a wide-ranging and complete reference. You’ll get thoroughly up to speed on cloud platforms, infrastructure, services and applications, security, and much more. Computing • Learn what cloud computing is and what it is not • Assess the value of cloud computing, including licensing models, ROI, and more • Understand abstraction, partitioning, virtualization, capacity planning, and various programming solutions • See how to use Google®, Amazon®, and Microsoft® Web services effectively ® ™ • Explore cloud communication methods — IM, Twitter , Google Buzz , Explore the cloud with Facebook®, and others • Discover how cloud services are changing mobile phones — and vice versa this complete guide Understand all platforms and technologies www.wiley.com/compbooks Shelving Category: Use Google, Amazon, or
    [Show full text]
  • Metro User Guide Metro User Guide Table of Contents
    Metro User Guide Metro User Guide Table of Contents Preface .............................................................................................................................. x 1. Introduction to Metro ....................................................................................................... 1 1.1. Required Software ................................................................................................ 1 1.2. What is WSIT? .................................................................................................... 1 1.2.1. Bootstrapping and Configuration ................................................................... 2 1.2.2. Message Optimization Technology ................................................................ 3 1.2.3. Reliable Messaging Technology .................................................................... 4 1.2.4. Security Technology ................................................................................... 4 1.3. How Metro Relates to .NET Windows Communication Foundation (WCF) ...................... 5 1.4. Metro Specifications ............................................................................................. 5 1.4.1. Bootstrapping and Configuration Specifications ............................................... 7 1.4.2. Message Optimization Specifications ............................................................. 8 1.4.3. Reliable Messaging Specifications ............................................................... 10 1.4.4. Security Specifications
    [Show full text]
  • OPEN SOURCE SOFTWARE: WHAT IT IS and WHAT IT CAN DO for YOUR LIBRARY Steven G. Watkins California State University, Monterey Ba
    OPEN SOURCE SOFTWARE: WHAT IT IS AND WHAT IT CAN DO FOR YOUR LIBRARY Steven G. Watkins California State University, Monterey Bay, Library 100 Campus Center Seaside, CA 93955 USA Abstract: In the difficult economic climate in which we find ourselves in 2009, open source software has been adopted by many libraries because it is free to use, reuse, modify, and distribute. From office productivity suites to library-specific applications such as an integrated library system, open source software has a lot to offer libraries. This paper illustrates the wide range of open source applications that are currently in use on the IAMSLIC website and at one IAMSLIC member library. A selective resource guide is included that other libraries can use to locate and obtain open source software for their own use. Keywords: open source software; OSS; FLOSS What is Open Source Software? In attempting to define open source software (OSS), also referred to as free/libre open source software (FLOSS), it is helpful to clarify what it is not: • OSS is not the same as “open access,” which is a publishing model for making scholarly literature freely available. • OSS is not the same as “open archives” or OAI, the Open Archives Initiative, which provides a platform for the creation of institutional repositories into which authors may deposit publications, along with the ability to automatically harvest metadata from such repositories. However, most of the software platforms underlying institutional repositories do consist of open source software programs. • OSS is not the same as web services and utilities that are offered for use free of charge, such as Flickr.
    [Show full text]
  • Sfara Mobile SDK FOSS DISCLOSURE DOCUMENT Sfara Inc
    Sfara Mobile SDK FOSS DISCLOSURE DOCUMENT Sfara Inc. Version 5.0.1, 2020-12-15 TABLE OF CONTENTS 1 FOSS Notices .......................................................................................................................................... 2 2 Used FOSS Packages and Licenses ........................................................................................................... 2 2.1 Overview ........................................................................................................................................................... 2 2.2 Package details ................................................................................................................................................. 3 2.2.1 Google Test .......................................................................................................................................................................................... 3 2.2.2 DSP FIlters ............................................................................................................................................................................................ 3 2.2.3 FFTReal .................................................................................................................................................................................................. 3 2.2.4 Persistence1D ....................................................................................................................................................................................
    [Show full text]
  • Transition from Java EE to Jakarta EE? EE Conclusion What Happened and What You Need to Know
    Search Java Magazine Menu Topics Issues Downloads Subscribe Transition from Java EE to Jakarta JAVA EE EE What Has Been Going on with Java Transition from Java EE to Jakarta EE? EE Conclusion What happened and what you need to know by Arjan Tijms February 27, 2020 Java EE is undoubtedly one of the most recognizable frameworks for server-side Java. It essentially kick-started the industry for using Java on the server, and it goes all the way back to the very beginnings of Java in 1996 with Kiva Enterprise Server (GlassFish) and the Tengah application server (the Oracle WebLogic Server ancestor). Note that here, the word Tengah refers to an administrative region in the center of the island of Java in Indonesia. Java EE, or J2EE (Java 2 Enterprise Edition) as it was known before, is perhaps best known for its Java Servlet specification and for servers implementing that, such as Tomcat and Jetty. These are often called servlet containers. Although there are alternatives, many server applications and third-party frameworks are based on the Java Servlet specification. Besides this specification, Java EE in later years became known for its specifications for persistence (Java Persistence API [JPA], mostly via Hibernate), REST (JAX-RS), WebSocket, and a slew of smaller specifications such as for transactions (Java Transaction API [JTA], mostly used under the covers by JPA), for validation (Bean Validation), and for JSON (JSON-P and JSON-B). In practice, some applications that might not seem to be classified as Java EE applications might use a variety of Java EE APIs.
    [Show full text]