DOCSLIB.ORG

Session 6 - Main Theme J2EE Component-Based Computing Environments

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Session 6 - Main Theme J2EE Component-Based Computing Environments Application Servers G22.3033-011 Session 6 - Main Theme J2EE Component-Based Computing Environments Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda Component Technologies Database Technology Review EJB Component Model J2EE Services JNDI, JMS, JTS, CMP/BMP/JDBC, JavaMail, etc. J2EE Web Architectures Security in J2EE Application Servers Structured Applications Design Tips Summary Readings Assignment #5 2 1 Summary of Previous Session COM and COM+ Introduction to .Net Component Technologies Object Management Architectures Java-Based Application Servers Windows Services Summary Readings Assignment #5 3 Additional References Intranet Architectures and Performance Report http://www.techmetrix.com/lab/benchcenter/archiperf/archiper ftoc.shtml#TopOfPage RMI FAQ http://java.sun.com/products/javaspaces/faqs/rmifaq.html CORBA beyond the firewall http://www.bejug.org/new/pages/articles/corbaevent/orbix/ Web Object Integration (vision document) http://www.objs.com/survey/web-object-integration.htm 4 2 Application Servers Architectures Application Servers for Enhanced HTML (traditional) a.k.a., Page-Based Application Servers Mostly Used to Support Standalone Web Applications New Generation Page-Based Script-Oriented App. Servers First Generation Extensions (e.g., Microsoft IIS with COM+/ASP) Servlet/JSP Environments XSP Environment Can now be used as front-end to enterprise applications Hybrid development environments Distributed Object Computing Platforms Provide an infrastructure for distributed communications enabling Still need to merge traditional web-oriented computing with object computing Object Management Architectures DOC Platform + APIs to reusable services and facilities 5 OMAs + Component Models -> J2EE, CCM, DNA Part I VMs and Component Technologies JVM and .Net CLR 6 3 Virtual Machines (VMs) • Provide level of abstraction on top of OSs • Support binary compatibility between components (language independence / requires language translators) • Support for data marshalling between components and clients • Streamline component installation and deployment • Work at finer granularity level than component infrastructure for deployment (e.g., classes) • Compliance with definition of component infrastructure not required • VM is integral part of component infrastructure • VM is not a component technology by itself • Component infrastructure = VM with component support? 7 Java Virtual Machine (JVM) • Provides OO environment for compiling Java classes and executing compiled bytecodes locally and remotely • Provides an execution environment where Java classes in binary format are loaded, verified, and executed • Hide the platform dependency for developers (WORA) 8 4 .Net • Provides OO environment with local and remote execution capabilities • Provides an execution environment with additional support for deployment and versioning of object code • Improves the performance of scripted and interpreted code • Hides the specifics of the underlying platform architecture • Provides full code compatibility allowing vendors to add language compilers which produce MSIL format • .Net provides a Common Type System (CTS) that allows introspection of managed code 9 .Net (continued) • .Net provides memory management, threading, and synchronization models similar to the Java environment • .Net provides a set of base classes and libraries called .Net framework, a virtual machine called CLR, and development languages (e.g., Jscript, Visual Basic, C#, C++, IL Assembler) • .Net compilers generate Portable Executable code that incorporates MSIL (PE-MSIL) that looks like DLL or EXE • CLR uses a JIT to translate MSIL modules (assemblies) into native executable code 10 5 Java Platform vs. .Net • Java runs on any platform with JVM while C# only runs in MS Windows • Java is the primary language for the JVM while .Net allows unification of PLs under the .Net framework • Scripting languages are interpreted on the Java platform, while they are compiled on .Net • Resulting code is bytecode interpreted by JVM, while IL is always translated into native code that is not interpreted 11 Java Virtual Machine Write Once Run Anywhere (WORA) Architecture 12 6 Java Virtual Machine (JVM) (continued) • Byte Code Verifier • Class Loader (dynamic operation) • Runtime Execution Engine • Performance bottlenecks: • Byte Code Execution, garbage collection, thread management, dynamic operations (i.e., class loading, bounds checking, security measures, dynamic class loading, exception handling, reflection, and native method translation) • Just-in-time compiler • Reduces byte-code interpretation and causes the execution workload to shift to native compilation and caching of native methods. • Precompiler 13 Open JVM Interface (OJI) • Allows any Sun-Compliant JVM (implementing OJI) to become the default JVM for a browser • Supports Applet, Embed, and Object tags • Supports Java-JavaScript bidirectional communication • Supports RSA signed applet verification 14 7 .NET Framework Common Language Runtime (CLR) Accessible to any compiler that produced Microsoft Intermediate Language (IL) code Runtime Classes Visual Studio.Net (VS.Net) Includes VB.Net, VC.Net (C#), and Visual C++.Net 15 .Net Remoting (http://www.dotnetremoting.cc/) Native .Net Remote Object Invocation Allows Object Invocation and Communications Across Processes and Machines Wire Protocol and Format Independent Extensible via Custom Formatters (SOAP, Binary, etc.), Channels (HTTP, TCP, etc.), and Sink Chain (i.e., Channels + Formatters) Steps Flexible as Configuration can be Changed after Deployment with Little or no Code Changes Flexible (IIS not required on server) but more Complex than Web Services 16 8 .Net Remoting Vs. DCOM Not as Transparent as DCOM Has no COM Interop Involved Offers More Deployment Options Not Tied to a Specific Wire Protocol or Format Firewall Friendly Allows you to Specify which Objects are Remoted 17 .Net CLR and COM+ CLR Introduces a Newer and Easier Programming Model for COM+ The COM+ Services are still Available only at the OS/Unmanaged World Transitions Between Managed/Unmanaged Layers are Taken Care of by “System.EnterpriseServices” Namespace System.EnterpriseServices.ContextUtil class provides access to contexts (as did CoGetObjectContext) Services are Made Available to Components Using Attributes 18 9 .NET, Win32, COM, and COM+ .Net applications can call functions that reside in Win32 DLLs via the DllImport attribute of System.Runtime.InteropServices’ platform invocation (PInvoke) services .Net applications can call traditional COM components using Runtime Callable Wrappers (RCWs) which uses interop assemblies (i.e., .Net components) created via COM Interop using the TLBIMP utility COM+ services (transactions, object pooling, JIT activation) can be used from .Net (via System.EnterpriseServices namespace) .Net runtime uses COM+ to support some of its services (e.g., transactions for managed classes) 19 ContextUtil Class Useful Static Members ActivityId IsSecurityEnabled TransactionId DesactivateOnReturn MyTransactionVote Rich Set of Member Functions SetComplete SetAbort EnableCommit DisableCommit IsCallerInRole GetNamedProperty 20 10 .Net and ServicedComponent COM+ Class Derives from “ServicedComponent” [ComVisible(true)] [ObjectPooling(MinPoolSize=2, MaxPoolSize=5)] [Guid(“57F01F20-9C0C-4e63-9588-720D5D537E66)] [Transaction(TransactionOption.Required)] public class SVCCompClass : ServicedComponent In COM+ 1.0, the List of Services Are not Changed In COM+ 1.5 (Microsoft Windows XP Professional and .Net server), Newer Services are Available to Leverage CLR Features 21 MDA • OMG's MDA (Model-Driven Architecture) specification describes: – a PIM - platform-independent models (i.e. business design) – PSMs - the mapping of a PIM to one or more platform-specific model • MDA => Model Once, Generate Everywhere • Review MDA presentations: 22 – http://www io-software com 11 MDA UML Model (PIM) (continued)XMI Document (PSM) Auto <Auto> <Color> Red </Color> Color : String XMI Door : Integer <Door> 4 </Door> Engine : Integer <Engine> 2 </Engine> M O </Auto> X F M I IDL, Java… (PSM) XMI DTD, Schema (PSM) interface Auto { Class Auto <!Element Auto }; {public String color; (Color*, public int Door; Door*, public int Engine; Engine*)> } 23 The first level of automation ~ 30 Years (Platform independent to platform specific model projection) Programming IDEs (e.g. JBuilder, Visual Age, NetBeans) Environment •Higher level of expression PIM Programming Language •Easier to understand •Portable •Standardized •Dependable Generator, •Flexible Projection Compiler Engine •Configurable •Optimizing •Complete: Linker, Debugger, Etc. PSM Diverse HW/OS Platforms 24 12 MDA= New automation levels ~ Last 8 Years http://www.omg.org/mda Architectural IDEs Environment •Higher level of expression PIM Model (UML, BOM…) & •Easier to Modeling Style (J2EE, eEPC, COBOL, .NET…) understand •Portable •Standardized •Dependable Generator, •Flexible Generator Engine Projection •Configurable •Debuggable •Optimizing Models to Code •Complete Models to Models P-Stack: A Level of Automation PSM 25 Architectural IDEs http://www.io-software.com, The Unified Process Std. MDA Projections ArcStyler Core Modules J2EE/EJB, .NET BEA WebLogic Open MDA/UML/XML Repository MDA Cartridges Business Pattern UML MDA-Engine Build, IBM WAS NT, z/OS Object Refinement Refinement Engine Deploy & Test with
Load more

Recommended publications
  • Scripting for the Java Platform
    Scripting for the Java Platform Christopher M. Judd President/Consultant Judd Solutions, LLC Christopher M. Judd • President/Consultant of Judd Solutions • Central Ohio Java User Group (COJUG) coordinator Agenda • Java Scripting Overview •Examples –API – Script Shell – Java EE Debugging • Alternative Java Scripting Engines – Configuring –Creating • Closing Thoughts • Resources •Q&A Java is the greatest language ever invented Developer’s tools Every developer’s toolbox should contain a static typed language like Java or C# and a dynamically typed scripting language like JavaScript, Ruby or Groovy. Java Scripting • Java Scripting support added in Java SE 6 • JSR 223: Scripting for the Java Platform • Java Virtual Machine – Executes “language-neutral” bytecode – Rich class library Java JavaScript Groovy – Multi-platform JVM •Features JavaScript Groovy – API to evaluate scripts – Embedded JavaScript engine (Rhino 1.6R2) – Scripting engine discovery mechanism – Java Scripting command-line interpreter (jrunscript) Reasons for Scripting •Flexibility • Simplicity (Domain Specific Language) • Interpreted • Development productivity •Dynamic typing • Expressive syntax •FUN Scripting Uses • Configuration •Customization • Automation • Debugging • Templating •Unit Testing •Prototyping • Web Scripting • Data transport Scripting Options •JavaScript – Rhino – www.mozilla.org/rhino/ •Groovy (JSR-241) – groovy.codehaus.org •Python –Jython –www.jython.org •Ruby –JRuby–jruby.codehaus.org •TCL –Jacl–tcljava.sourceforge.net • Java (JSR-274) – BeanShell www.beanshell.org
    [Show full text]
  • Abkürzungs-Liste ABKLEX
    Abkürzungs-Liste ABKLEX (Informatik, Telekommunikation) W. Alex 1. Juli 2021 Karlsruhe Copyright W. Alex, Karlsruhe, 1994 – 2018. Die Liste darf unentgeltlich benutzt und weitergegeben werden. The list may be used or copied free of any charge. Original Point of Distribution: http://www.abklex.de/abklex/ An authorized Czechian version is published on: http://www.sochorek.cz/archiv/slovniky/abklex.htm Author’s Email address: [email protected] 2 Kapitel 1 Abkürzungen Gehen wir von 30 Zeichen aus, aus denen Abkürzungen gebildet werden, und nehmen wir eine größte Länge von 5 Zeichen an, so lassen sich 25.137.930 verschiedene Abkür- zungen bilden (Kombinationen mit Wiederholung und Berücksichtigung der Reihenfol- ge). Es folgt eine Auswahl von rund 16000 Abkürzungen aus den Bereichen Informatik und Telekommunikation. Die Abkürzungen werden hier durchgehend groß geschrieben, Akzente, Bindestriche und dergleichen wurden weggelassen. Einige Abkürzungen sind geschützte Namen; diese sind nicht gekennzeichnet. Die Liste beschreibt nur den Ge- brauch, sie legt nicht eine Definition fest. 100GE 100 GBit/s Ethernet 16CIF 16 times Common Intermediate Format (Picture Format) 16QAM 16-state Quadrature Amplitude Modulation 1GFC 1 Gigabaud Fiber Channel (2, 4, 8, 10, 20GFC) 1GL 1st Generation Language (Maschinencode) 1TBS One True Brace Style (C) 1TR6 (ISDN-Protokoll D-Kanal, national) 247 24/7: 24 hours per day, 7 days per week 2D 2-dimensional 2FA Zwei-Faktor-Authentifizierung 2GL 2nd Generation Language (Assembler) 2L8 Too Late (Slang) 2MS Strukturierte
    [Show full text]
  • Liferay Third Party Libraries
    Third Party Software List Liferay Portal 6.2 EE SP20 There were no third party library changes in this version. Liferay Portal 6.2 EE SP19 There were no third party library changes in this version. Liferay Portal 6.2 EE SP18 There were no third party library changes in this version. Liferay Portal 6.2 EE SP17 File Name Version Project License Comments lib/portal/monte-cc.jar 0.7.7 Monte Media Library (http://www.randelshofer.ch/monte) LGPL 3.0 (https://www.gnu.org/licenses/lgpl-3.0) lib/portal/netcdf.jar 4.2 NetCDF (http://www.unidata.ucar.edu/packages/netcdf-java) Netcdf License (http://www.unidata.ucar.edu/software/netcdf/copyright.html) lib/portal/netty-all.jar 4.0.23 Netty (http://netty.io) Apache License 2.0 (http://www.apache.org/licenses/LICENSE-2.0) Liferay Portal 6.2 EE SP16 File Name Version Project License Comments lib/development/postgresql.jar 9.4-1201 JDBC 4 PostgreSQL JDBC Driver (http://jdbc.postgresql.org) BSD Style License (http://en.wikipedia.org/wiki/BSD_licenses) lib/portal/commons-fileupload.jar 1.2.2 Commons FileUpload (http://commons.apache.org/fileupload) Apache License 2.0 (http://www.apache.org/licenses/LICENSE-2.0) This includes a public Copyright (c) 2002-2006 The Apache Software Foundation patch for CVE-2014-0050 and CVE-2016-3092. lib/portal/fontbox.jar 1.8.12 PDFBox (http://pdfbox.apache.org) Apache License 2.0 (http://www.apache.org/licenses/LICENSE-2.0) lib/portal/jempbox.jar 1.8.12 PDFBox (http://pdfbox.apache.org) Apache License 2.0 (http://www.apache.org/licenses/LICENSE-2.0) lib/portal/pdfbox.jar 1.8.12 PDFBox (http://pdfbox.apache.org) Apache License 2.0 (http://www.apache.org/licenses/LICENSE-2.0) lib/portal/poi-ooxml.jar 3.9 POI (http://poi.apache.org) Apache License 2.0 (http://www.apache.org/licenses/LICENSE-2.0) This includes a public Copyright (c) 2009 The Apache Software Foundation patch from bug 56164 for CVE-2014-3529 and from bug 54764 for CVE-2014-3574.
    [Show full text]
  • Programmers Guide
    JBossESB 4.6 Programmers Guide JBESB-PG-7/17/09 JBESB-PG-7/17/09 Legal Notices The information contained in this documentation is subject to change without notice. JBoss Inc. makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. JBoss Inc. shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. Java™ and J2EE is a U.S. trademark of Sun Microsystems, Inc. Microsoft® and Windows NT® are registered trademarks of Microsoft Corporation. Oracle® is a registered U.S. trademark and Oracle9™, Oracle9 Server™ Oracle9 Enterprise Edition™ are trademarks of Oracle Corporation. Unix is used here as a generic term covering all versions of the UNIX® operating system. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Copyright JBoss, Home of Professional Open Source Copyright 2006, JBoss Inc., and individual contributors as indicated by the @authors tag. All rights reserved. See the copyright.txt in the distribution for a full listing of individual contributors. This copyrighted material is made available to anyone wishing to use, modify, copy, or redistribute it subject to the terms and conditions of the GNU General Public License, v. 2.0. This program is distributed in the hope that it will be useful, but WITHOUT A WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
    [Show full text]
  • Accessing Application Context Listing
    19_1936_index.qxd 7/11/07 12:14 AM Page 503 INDEX A Ant BSF Support Example Accessing Application Context listing listing (7.12), 314 (10.2), 463 Ant task, Groovy, 132-133 Active File Example listing (8.20), 376 Ant Task That Compiles All Scripts Inside Active File Generator listing (8.22), 380 the Project listing (8.10), 357 active file pattern, 375 AntBuilder Example listing (7.14), 317 consequences, 375 any( ) method, Groovy, 175-177 problem, 375 any( ) Method listing (4.30), 175 sample code, 376-380 Apache Web servers, 62 solution, 375 BSF (Bean Scripting Framework), 94 Active File Template listing (8.21), 379 APIs (application programming ADD keyword, 5 interfaces), 49 addClassPath( ) method, 324 Java, 80-82 administration append( ) method, Groovy, 181-182 scripting, 328-334 append( ) Method listing (4.39), 182 scripting languages, 55-58 application scope, Web environments, 449 Administration Script Example application variable (Groovlet), 215 listing (7.17), 329 applications Advanced Ant BSF Support Example BSF (Bean Scripting Framework), 275 listing (7.13), 315 JSP (JavaServer Pages), 275-280 Advanced AntBuilder Example Xalan-J (XSLT), 280-287 listing (7.15), 320 Java, 79 Advanced Binding Example—Java web applications, 59, 61-67 Application listing (9.13), 408 ASP (Active Server Pages), 64 Advanced Groovy Programming Example games, 68-69 listing (5.22), 225 JavaScript, 65-67 AJAX (Asynchronous JavaScript And Perl, 61-62 XML), 66 PHP, 62-64 Ant build tools, 309-322 UNIX, 68 19_1936_index.qxd 7/11/07 12:14 AM Page 504 504 INDEX apply(
    [Show full text]
  • Another Tool
    Sr.N o. 3rd Party Software 3rd Party Files Provider URL License Type Reference to License License Link ANTLR – Another Tool for Copyright (c) 2005, Terence 1 Language Recognition antlr-2.7.6.jar http://www.antlr.org/ Parr, BSD License ANTLR_License.txt http://www.antlr2.org/license.html ASM - An all purpose Java bytecode manipulation and Copyright (c) 2000-2005 INRIA, 2 analysis framework asm.jar, asm-attrs.jar http://asm.ow2.org/ France Telecom BSD ASM.txt http://asm.ow2.org/license.html http://archive.apache.org/dist/avalon/avalon- 3 Apache Avalon Framework avalon-framework-cvs-20020806.jar http://avalon.apache.org/closed.html Apache License, Version 2.0 Apache2_License.txt framework/jars/LICENSE.txt 4 Apache Axis - Web Services axis.jar http://ws.apache.org/axis/ Apache License, Version 2.0 Apache2_License.txt http://www.apache.org/licenses/LICENSE-2.0.txt 5 Batik SVG Toolkit batik.jar http://xmlgraphics.apache.org/batik/faq.html Apache License, Version 2.0 Apache2_License.txt http://xmlgraphics.apache.org/batik/license.html Eclipse Public License, Version 6 bilki bliki-core-3.0.15.jar http://code.google.com/p/gwtwiki/downloads/list 1.0 EPL.txt http://www.eclipse.org/legal/epl-v10.html 7 Bean Scripting Framework (BSF) bsf.jar http://jakarta.apache.org/bsf/ Apache License, Version 2.0 Apache2_License.txt http://www.apache.org/licenses/LICENSE-2.0.txt GNU Lesser General Public 8 Bean Shell (BSH) bsh-1.2b7.jar http://www.beanshell.org/ License, Sun Public License BSH_License.txt http://www.gnu.org/licenses/lgpl-3.0.txt Apache/IBM Bean Scripting Framework (BSF) Adapter for GNU Lesser General Public 9 BeanShell bsh-bsf-2.0b4.jar http://www.beanshell.org/download.html License, Sun Public License BSH_License.txt http://www.gnu.org/licenses/lgpl-3.0.txt c3p0:JDBC Copyright (C) 2005 Machinery 10 DataSources/Resource Pools c3p0-0.9.1.2.jar http://sourceforge.net/projects/c3p0 For Change, Inc.
    [Show full text]
  • Okta Tools Third Party Licenses and Notices
    Okta Tools Third Party Licenses and Notices This document contains third party open source licenses and notices for the Okta Tools. Certain licenses and notices may appear in other parts of the product in accordance with the applicable license requirements. The Okta product that this document references does not necessarily use all the open source software packages referred to below and may also only use portions of a given package. Third Party Notices Almond Version (if any): 0.2.9 Brief Description: A minimal AMD API implementation for use after optimized builds. License: MIT or BSD 3-Clause, MIT selected Copyright (c) 2011-2014, The Dojo Foundation All Rights Reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
    [Show full text]
  • Performance Testing with Jmeter Second Edition
    [ 1 ] Performance Testing with JMeter Second Edition Test web applications using Apache JMeter with practical, hands-on examples Bayo Erinle BIRMINGHAM - MUMBAI Performance Testing with JMeter Second Edition Copyright © 2015 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: July 2013 Second edition: April 2015 Production reference: 1200415 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-78439-481-3 www.packtpub.com Credits Author Project Coordinator Bayo Erinle Kinjal Bari Reviewers Proofreaders Vinay Madan Simran Bhogal Satyajit Rai Safis Editing Ripon Al Wasim Joanna McMahon Commissioning Editor Indexer Pramila Balan Monica Ajmera Mehta Acquisition Editor Production Coordinator Llewellyn Rozario Arvindkumar Gupta Content Development Editor Cover Work Adrian Raposo Arvindkumar Gupta Technical Editors Tanvi Bhatt Narsimha Pai Mahesh Rao Copy Editors Charlotte Carneiro Pranjali Chury Rashmi Sawant About the Author Bayo Erinle is an author and senior software engineer with over 11 years of experience in designing, developing, testing, and architecting software.
    [Show full text]
  • TIBCO Software Inc. End User License Agreement
    1 TIBCO Software Inc. End User License Agreement TIBCO Software Inc. End User License Agreement READ THIS END USER LICENSE AGREEMENT CAREFULLY. BY All proprietary notices incorporated in or affixed to any Software, DOWNLOADING OR INSTALLING THE SOFTWARE, YOU AGREE Documentation or Materials shall be duplicated by Customer on all TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT AGREE copies of the Software, Documentation, or Material, as applicable, TO THESE TERMS, DO NOT DOWNLOAD OR INSTALL THE and shall not be altered, removed or obliterated. SOFTWARE AND RETURN IT TO THE VENDOR FROM WHICH IT WAS PURCHASED. Extraordinary Corporate Event. To the extent Licensee or its successors or assigns enters into an Extraordinary Corporate Event Upon your acceptance as indicated above, the following shall after the Order Form Effective Date, this Agreement shall not apply to govern your use of the Software except to the extent all or any those additional users, divisions or entities, which were added to portion of the Software (a) is subject to a separate written Licensee's organization as a result of the Extraordinary Corporate agreement, or (b) is provided by a third party under the terms set Event until those additional users, divisions or entities are added to forth in an Addenda at the end of this Agreement, in which case the this Agreement by way of a written amendment signed by duly terms of such addenda shall control over inconsistent terms with authorized officers of Licensor and Licensee. regard to such portion(s). Beta and Evaluation Licenses. Notwithstanding the foregoing, if the License Grant.
    [Show full text]
  • Unifier Licensing Information User Manual 16 R2
    Unifier Licensing Information User Manual 16 R2 September 2017 Contents Introduction............................................................................................. 7 Licensed Products, Restricted Use Licenses, and Prerequisite Products ................... 7 Primavera Unifier Project Controls License .......................................................... 7 Primavera Unifier Facilities and Real Estate Management ........................................ 8 Primavera Unifier Portal User License ................................................................ 9 Third Party Notices and/or Licenses ............................................................... 9 Annogen ................................................................................................... 9 Antelope .................................................................................................. 9 Antlr ..................................................................................................... 10 Apache Chemistry OpenCMIS ......................................................................... 10 Apache Commons IO ................................................................................... 10 Apache Commons Lang ................................................................................ 11 Apache Commons Text ................................................................................ 11 Apache Derby........................................................................................... 11 Apache ecs .............................................................................................
    [Show full text]
  • Scripting Your Java Application with BSF 3.0
    Scripting your Java Application with BSF 3.0 Felix Meschberger ApacheCon EU 09 About • Senior Developer at Day • [email protected] • http://blog.meschberger.ch • Apache Projects: – Sling – Felix – Jackrabbit Contents • Scope • BSF 3.0 • Scripting for the JavaTM Platform • OSGi Framework • Demo Scope • Scripting for the JavaTM Platform • Using BSF 3 • Not using BSF 2 API • Example: Apache Sling Contents • Scope • BSF 3.0 • Scripting for the JavaTM Platform • OSGi Framework • Demo About BSF • Bean Scripting Framework • http://jakarta.apache.org/bsf/ • Timeline – 1999 Sanjiva Weerawarana, IBM – 2002 Subproject of Jakarta (Version 2.3) – 2006 BSF 2.4 – 2007 BSF 3.0 beta2 – 2009 BSF 3.0 beta3 (right now!) BSF 3.0 • Java Scripting API (JSR-223) • Stable • Beta due to TCK issues Contents • Scope • BSF 3.0 • Scripting for the JavaTM Platform • OSGi Framework • Demo Scripting for the JavaTM Platform • JSR-223 • Approved November 2006 • Builds on BSF 2.4 and BeanShell • Included in Java 6 • BSF 3.0 for Java 1.4 and Java 5 Three Steps for Scripting 1. Get the ScriptEngineManager ScriptEngineManager mgr = new ScriptEngineManager(); 2. Get the ScriptEngine ScriptEngine eng = mgr.getEngineByExtension(„js“); 3. Evaluate the Script Object result = eng.eval(„'Hello World'“); Demo 1 • Scripting in Three Steps – Sample0.java – Call Class from Command Line Main API • javax.script.ScriptEngineManager – Manages ScriptEngineFactory – Provides access to ScriptEngine – Manages Global Scope • javax.script.ScriptEngineFactory – Registered with ScriptEngineManager
    [Show full text]
  • Graphdb Free Documentation Release 7.2
    GraphDB Free Documentation Release 7.2 Ontotext Oct 28, 2016 CONTENTS 1 General 1 1.1 About GraphDB...........................................2 1.2 Architecture & components.....................................2 1.2.1 Architecture.........................................2 Sesame............................................3 The SAIL API........................................4 1.2.2 Components.........................................4 Engine............................................4 Connectors..........................................5 Workbench..........................................5 1.3 GraphDB Free............................................5 1.3.1 Comparison of GraphDB Free and GraphDB SE......................6 1.4 Connectors..............................................6 1.5 Workbench..............................................6 1.5.1 How to use it........................................7 2 Quick start guide 9 2.1 Start the database...........................................9 2.1.1 Run GraphDB as a desktop installation...........................9 On Windows.........................................9 On Mac OS..........................................9 On Linux...........................................9 Configuring GraphDB....................................9 Stopping GraphDB...................................... 10 2.1.2 Run GraphDB as a stand-alone server........................... 10 Running GraphDB...................................... 10 Configuring GraphDB.................................... 11 Stopping the database...................................
    [Show full text]