DOCSLIB.ORG

A Peek Under the Hood of Apache Geronimo

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC Apache Geronimo: A Peek Under the Hood Bruce Snyder Jailey Solutions, LLC Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 1 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC What Is Apache Geronimo? It is Not… It is… Yet another lightweight Designed for long container running servers Yet another web Designed to tolerate framework partial component Yet another AOP failures framework System oriented An MVC framework services Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 2 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC From the Ground on Down Open Source Enterprise Infrastructure Highly modular architecture Initial manifestation as a J2EE Server Other possible configurations ¾Native Spring Integration ¾Bi-directional PicoContainer Integration ¾Native Portlet Integration ¾Native Web Services Integration ¾Deployment Chaining ¾and many more … Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 3 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC Geronimo Kernel Fundamental Core ¾Small memory consumption ~150KB code ¾Component Configuration ¾Component Registration ¾Integrated Repository ¾Lifecycle Control ¾Dependency Manager Components are called GBeans ¾Simple object, plus some metadata Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 4 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC What Are GBeans? A J2EE managed object (MBeans) Used to bridge JSR-77 lifecycle requirements GBean wrappers allow just about anything to be plugged in to Geronimo Implement the GBeanLifecycle interface public interface GBeanLifecycle { void doStart() throws WaitingException, Exception; void doStop() throws WaitingException, Exception; void doFail(); } Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 5 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC What Are GBeans? (Continued) Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 6 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC GBean Archive A JAR file containing: ¾Persisted GBean instances ¾GBean metadata ¾Required Java classes reside: • Either in the jar, or • As dependencies from a central repository Must have a unique ID Can be signed for distribution Can be executable Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 7 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC GBean Descriptor Example Provides IoC configuration for a GBean <gbean> elements can be placed in any descriptor - usually geronimo-application.xml <gbean name="geronimo.system:role=LogAppender,type=ConsoleAppender" class="org.apache.geronimo.system.logging.log4j.appender.ConsoleAppenderService"> <attribute name="threshold" type="java.lang.String">INFO</attribute> <attribute name="layoutPattern" type="java.lang.String"> %d{ABSOLUTE} %-5p [%c{1}] %m%n </attribute> <attribute name="target" type="java.lang.String">System.out</attribute> </gbean> Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 8 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC Demo (Time Permitting) Demonstrate simple GBean wrapper Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 9 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC Repository Structured collection of jars ¾Designed to work in conjunction with Maven • Pluggable implementation ¾Every jar has a unique group and artifact ID, e.g. • geronimo-spec • geronimo-j2ee-1.4-RC2 Default repository is local file system ¾Others allow auto-download Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 10 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC Basic Configuration Builder Deployers are J2EE specific ¾JSR-88 Builders are Geronimo specific ¾Create configuration objects containing GBeans ¾Serialized to a file upon shutdown From a pure GBean configuration ¾Very raw – used to bootstrap a server ¾You specify GBeans in an XML descriptor ¾Not intended for end users Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 11 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC Application Builders Two stages make up deployment (JSR-88) ¾Deployment • Read the ear file and the server config(s) ¾Distribution • Send the ear file and server config(s) to the server Geronimo handles both stages in single step for the user Application-specific configurations Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 12 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC Application Builders (Continued) Most complex Builder is J2EE deployer ¾Implements JSR-88 deployment specification ¾Take EJB-jars, wars, rars ¾Add in a deployment plan (XML) ¾Output a Geronimo Configuration ARchive (.car) Can produce very complex GBean definitions ¾e.g. entire EJB gets mapped to a GBean Allows for deploy-time optimizations ¾e.g. Precompile EJBQL, MessageSelectors, etc. Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 13 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC Configurations EAR EJB WAR Local Environment Hot (DataSources, etc.) RAR Pico Pico Spring App Swap J2EE Configuration Pico Spring (Jetty, OpenEJB, ActiveMQ) Config Config System Services (Logging, URL Handler, XML Catalog) Cold Swap Geronimo Kernel (Lifecycle, Config Manager, Repository) Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 14 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC Running the Server $ java –jar bin/server.jar <config> $ java –jar bin/server.jar <config> is a specific configuration to boot With M2, default is to restart all configurations that were running on last clean shutdown Maven Geronimo deploy plugin simplifies this greatly Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 15 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC Geronimo Community Geronimo MX4J JOTM ActiveMQ OpenEJB cglib Jetty TranQL ActiveCluster Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 16 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC Jetty Well established web container Implements Servlet 2.4 specification Designed for embedding and high performance Why not Apache Tomcat yet? ¾No real reason, just hasn’t been done yet Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 17 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC OpenEJB Well established EJB container Upgraded from 1.1 to 2.1 specification ¾No, it doesn’t do EJB3 (yet) Fully integrated into Geronimo Optimized for highly concurrent workloads Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 18 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC ActiveMQ Yes, it’s another JMS implementation ¾Looked at OpenJMS and JORAM ¾Needed BSD, JMS1.1 and JCA1.5 Designed for performance ¾NIO ¾Content based routing ¾Rules based routing (drools) Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 19 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC TranQL Framework for Persistence Frameworks Common data model across frameworks Multiple front ends: ¾EJB CMP, JDO, Castor, JDBC, Groovy DO Multiple back ends: ¾SQL92, SQL03, XML, LDAP, JCA Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 20 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC MX4J Well established JMX implementation Fully compliant JMX and JMX Remote API (JSR-160) Highly robust Widely used Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 21 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC ObjectWeb JOTM Java Open Transaction Manager Well established transaction manager Implements the JTA API ¾Full XA support • RMI/JRMP • RMI/IIOP Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 22 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC ActiveCluster Framework for creating cluster-based applications Small, simple implementation Pluggable service providers ¾Sockets ¾JMS ¾JGroups ¾Jabber Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 23 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC cglib High performance code generation library Well established class enhancer Provides runtime byte code manipulation Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 24 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC Security Built in at low level ¾Secure network protocols ¾Support security manager (sandbox) JAAS and JACC ¾Possible pluggable policy providers • HIPPA • SOX Kerberos integration (including .NET) Apache Directory integration (LDAP) Bruce Snyder — Apache Geronimo: A Peek Under the Hood Page 25 Colorado Software Summit: October 24 – 29, 2004 © Copyright 2004, Jailey Solutions, LLC Transactions Lightweight Transaction Manager ¾XA Coordinator ¾XATerminator for JCA transaction import ¾Logging (HOWL) and basic recovery Future is
Recommended publications
  • Testing and Deploying IBM Rational HATS® Applications on Apache Geronimo Server

    Testing and Deploying IBM Rational HATS® Applications on Apache Geronimo Server

    Testing and Deploying IBM Rational HATS® 8.5 Applications on Apache Geronimo Server 3.1 Royal Cyber Inc. Modernized e-business solutions Testing and Deploying IBM Rational HATS® Applications on Apache Geronimo Server Overview This white paper explains how to run, test and deploy IBM Host Access Transformation Service® (HATS) web application on Apache Geronimo Application server. Part 1 - Introduction In the 'Introduction' part the overview of the White Paper is provided. Basic introduction to the IBM Host Access Transformation Service (HATS) and Apache Geronimo Server are provided in this part. Part 2 - Deploying and Installing Apache Geronimo Server In the 'Deploying and Installing Geronimo Server' part, the entire process of deploying the Geronimo Server is explained. Along with that using IBM HATS projects in the Geronimo Server are also explained Part 3 - Benefits In the 'Benefits' part, the overall benefits of the combination IBM HATS-Apache Geronimo Server are discussed. Testing and Deploying IBM Rational HATS® Applications on Apache Geronimo Server PART 1- INTRODUCTION Application server is a very important component in the overall scheme of the web systems as it provides platform for launching or executing applications. It manages all the involved resources like Hardware, OS, Network, etc. It is not just mere hosting of the application, an application server acts as a stage for the deployment and development of Enterprise JavaBeans (EJBs), Web services, etc. In short, Application server interacts between the front end (end users) and system resources at backend. There are various Application servers available in market both paid and unpaid. However, for working with IBM HATS, Apache's Geronimo server is one of the top Application server choices.
  • California State University, Northridge the Design And

    California State University, Northridge the Design And

    CALIFORNIA STATE UNIVERSITY, NORTHRIDGE THE DESIGN AND IMPLEMENTATION OF A SMALL TO MEDIUM RESTAURANT BUSINESS WEB APPLICATION A graduate project submitted in partial fulfillment of the requirements for the degree of Master of Science in Computer Science By Edward Gerhardstein May 2011 The graduate project of Edward Gerhardstein is approved: John Noga , Ph.D. Date Robert McIlhenny , Ph.D. Date Jeff Wiegley , Ph.D., Chair Date California State University, Northridge ii Table of Contents Signature page ii Abstract vi 1 Overview of Pizza Application 1 2 Open Source Licenses Servers 2 2.1 Open Source License Definition . .2 2.2 Ubuntu . .2 2.3 Apache Tomcat . .2 2.4 MySQL . .4 3 Selected Concepts and Terminologies 6 3.1 Model-View-Controller (MVC) . .6 3.2 JavaScript . .7 3.3 Ajax . .7 3.4 XML . .7 3.5 DTD . .7 3.6 XML Schema . .7 3.7 CSS . .8 4 J2EE Concepts 9 4.1 J2EE Overview . .9 4.2 JavaBean . .9 4.3 Enterprise JavaBeans (EJB) . .9 4.4 Other J2EE APIs and Technologies . .9 4.5 Servlets . 10 4.6 JavaServer Pages (JSP) . 11 4.6.1 Scriptlet . 11 5 Apache Struts Framework 13 5.1 Apache Struts Overview . 13 5.2 ActionServlet . 13 5.3 Struts Config . 13 6 Pizza Application Overview 15 6.1 Design Layout . 15 6.2 Workflow . 15 6.3 JSP Page formats - Index.jsp/Templates . 17 6.4 JSP Page Divisions . 18 7 ClockIn/Clockout and Logon Functionality 21 7.1 ClockIn/Clockout Functionality . 21 iii 7.2 Logon Functionality . 21 8 Administrator Functionality 24 8.1 Administrator Functionality Description .
  • Talend Open Studio for Big Data Release Notes

    Talend Open Studio for Big Data Release Notes

    Talend Open Studio for Big Data Release Notes 6.0.0 Talend Open Studio for Big Data Adapted for v6.0.0. Supersedes previous releases. Publication date July 2, 2015 Copyleft This documentation is provided under the terms of the Creative Commons Public License (CCPL). For more information about what you can and cannot do with this documentation in accordance with the CCPL, please read: http://creativecommons.org/licenses/by-nc-sa/2.0/ Notices Talend is a trademark of Talend, Inc. All brands, product names, company names, trademarks and service marks are the properties of their respective owners. License Agreement The software described in this documentation is licensed under the Apache License, Version 2.0 (the "License"); you may not use this software except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.html. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. This product includes software developed at AOP Alliance (Java/J2EE AOP standards), ASM, Amazon, AntlR, Apache ActiveMQ, Apache Ant, Apache Avro, Apache Axiom, Apache Axis, Apache Axis 2, Apache Batik, Apache CXF, Apache Cassandra, Apache Chemistry, Apache Common Http Client, Apache Common Http Core, Apache Commons, Apache Commons Bcel, Apache Commons JxPath, Apache
  • Apache Harmony Project Tim Ellison Geir Magnusson Jr

    Apache Harmony Project Tim Ellison Geir Magnusson Jr

    The Apache Harmony Project Tim Ellison Geir Magnusson Jr. Apache Harmony Project http://harmony.apache.org TS-7820 2007 JavaOneSM Conference | Session TS-7820 | Goal of This Talk In the next 45 minutes you will... Learn about the motivations, current status, and future plans of the Apache Harmony project 2007 JavaOneSM Conference | Session TS-7820 | 2 Agenda Project History Development Model Modularity VM Interface How Are We Doing? Relevance in the Age of OpenJDK Summary 2007 JavaOneSM Conference | Session TS-7820 | 3 Agenda Project History Development Model Modularity VM Interface How Are We Doing? Relevance in the Age of OpenJDK Summary 2007 JavaOneSM Conference | Session TS-7820 | 4 Apache Harmony In the Beginning May 2005—founded in the Apache Incubator Primary Goals 1. Compatible, independent implementation of Java™ Platform, Standard Edition (Java SE platform) under the Apache License 2. Community-developed, modular architecture allowing sharing and independent innovation 3. Protect IP rights of ecosystem 2007 JavaOneSM Conference | Session TS-7820 | 5 Apache Harmony Early history: 2005 Broad community discussion • Technical issues • Legal and IP issues • Project governance issues Goal: Consolidation and Consensus 2007 JavaOneSM Conference | Session TS-7820 | 6 Early History Early history: 2005/2006 Initial Code Contributions • Three Virtual machines ● JCHEVM, BootVM, DRLVM • Class Libraries ● Core classes, VM interface, test cases ● Security, beans, regex, Swing, AWT ● RMI and math 2007 JavaOneSM Conference | Session TS-7820 |
  • Open Source Software Licenses, Notices, and Information

    Open Source Software Licenses, Notices, and Information

    Intergraph InPursuit® WebRMS 03.06.1909 Open Source Software Licenses, Notices, and Information This information is provided for Intergraph InPursuit® WebRMS, a software program of Intergraph® Corporation D/B/A Hexagon Safety & Infrastructure® (“Hexagon”). Source Code Access Intergraph InPursuit WebRMS may include components licensed pursuant to open source software licenses with an obligation to offer the recipient source code. Please see below the list of such components and the information needed to access the source code repository for each. In the event the source code is inaccessible using the information below, please email [email protected]. Component, version Link to download repository Hibernate ORM https://github.com/hibernate/hibernate-orm/releases/tag/3.6.10.Final 3.6.10.Final javassist 3.12.0.GA https://github.com/jboss-javassist/javassist/releases/tag/rel_3_12_0_ga wsdl4j 1.6.1 https://sourceforge.net/projects/wsdl4j/files/WSDL4J/1.6.1/ aspectj 1.8.4 http://git.eclipse.org/c/aspectj/org.aspectj.git/tag/?h=V1_8_4 displaytag 1.2.9 https://github.com/hexagonSI-RMS/displaytag-hexagon Open Source Software Components Intergraph InPursuit WebRMS may include the open source software components identified below. This document provides the notices and information regarding any such open source software for informational purposes only. Please see the product license agreement for Intergraph InPursuit WebRMS to determine the terms and conditions that apply to the open source software. Hexagon reserves all other rights. Component, version URL Copyright License link ActiveMQ KahaDB, version http://activemq.apache.org/kahadb.html © 2005-2012 Apache Software Foundation License 1 5.5.1 ActiveMQ, version 5.5.1 http://activemq.apache.org/ © 2005-2012 Apache Software Foundation License 1 Activiti, version 5.14.0 https://www.activiti.org/ © 2010-2016 Alfresco Software, Ltd.
  • Java Management Extension Didier DONSEZ

    Java Management Extension Didier DONSEZ

    http://www-adele.imag.fr/users/Didier.Donsez/cours JMX Java Management eXtension Didier DONSEZ Université Joseph Fourier –Grenoble 1 PolyTech’Grenoble LIG/ADELE [email protected], [email protected] 19/02/2008 Outline Motivation Architecture MBeans Standard, Dynamic Monitor Notification Utilities Remote Management Connector & Adaptor API Tools JSR Bibliography (c)Donsez,JMX Didier 2003-2008, 2 19/02/2008 Under Translation Motivations fr->en Service d’administration d’applications Ressources matérielles accessibles depuis une JVM Ressources logiciels s’exécutant sur une JVM S’inspire de SNMP Instrumentations des ressources au moyen de composants appelés MBean (Manageable Bean) Adopté initialement par J2EE et maintenant J2SE 1.5 (c)Donsez,JMX Didier 2003-2008, 3 19/02/2008 Usage Get and set applications configuration (Pull) Collect statistics (Pull) Performance Ressources usage Problems Notify events (Push) Faults State changes (c)Donsez,JMX Didier 2003-2008, 4 19/02/2008 JMX 3-Level Architecture JMX Web SNMP Specific Browser Console Console Console JConsole HTML/HTTP SNMP Remote RMI HTTP/SOAP Management Level C C’ A A’ Agent MBeanServer Level Probe MBean1 MBean2 MXBean3 (c)Donsez,JMX Didier 2003-2008, Level 5 19/02/2008 JMX 3-Level Architecture JMX Web SNMP Specific Browser Console Console Console JConsole HTML/HTTP SNMP Remote RMI HTTP/SOAP Management Level Connector Connector’ Adaptor Adaptor’ Agent MBeanServer Level Standard Dynamic Probe MXBean3 (c)Donsez,JMX Didier 2003-2008, Level MBean1 MBean2 For Wikipedia 6 19/02/2008 JMX 3-Level Architecture Probe level JMX Web SNMP Specific Browser Console Console Console Resources,JConsole such as applications, devices, or services, are instrumentedHTML/HTTP using JavaSNMP objects called Managed Beans (MBeans).
  • TLC 7.3.0 Use of Third Party Libraries

    TLC 7.3.0 Use of Third Party Libraries

    TLC 7.3.0 Use of Third Party Libraries Name Selected License Apache.NMS 1.5.1 (Apache 2.0) Apache License 2.0 Apache.NMS.ActiveMQ 1.5.6 (Apache 2.0) Apache License 2.0 activemq-broker 5.13.2 (Apache-2.0) Apache License 2.0 activemq-client 5.13.2 (Apache-2.0) Apache License 2.0 activemq-client 5.14.2 (Apache-2.0) Apache License 2.0 activemq-jms-pool 5.13.2 (Apache-2.0) Apache License 2.0 activemq-kahadb-store 5.13.2 (Apache-2.0) Apache License 2.0 activemq-openwire-legacy 5.13.2 (Apache-2.0) Apache License 2.0 activemq-pool 5.13.2 (Apache-2.0) Apache License 2.0 activemq-protobuf 1.1 (Apache-2.0) Apache License 2.0 activemq-spring 5.13.2 (Apache-2.0) Apache License 2.0 activemq-stomp 5.13.2 (Apache-2.0) Apache License 2.0 awaitility 1.7.0 (Apache-2.0) Apache License 2.0 cglib 2.2.1-v20090111 (Apache 2.0) Apache License 2.0 commons-daemon-windows 1.0.10 (Apache-2.0) Apache License 2.0 commons-io 2.0.1 (Apache 2.0) Apache License 2.0 commons-io 2.1 (Apache 2.0) Apache License 2.0 commons-io 2.4 (Apache 2.0) Apache License 2.0 commons-lang 2.6 (Apache-2.0) Apache License 2.0 commons-logging 1.1 (Apache 2.0) Apache License 2.0 commons-logging 1.1.3 (Apache 2.0) Apache License 2.0 commons-pool 1.6 (Apache 2.0) Apache License 2.0 commons-pool2 2.4.2 (Apache-2.0) Apache License 2.0 geronimo-j2ee-management_1.1_spec 1.0.1 (Apache-2.0) Apache License 2.0 geronimo-jms_1.1_spec 1.1.1 (Apache-2.0) Apache License 2.0 geronimo-jta_1.0.1B_spec 1.0.1 (Apache-2.0) Apache License 2.0 google-guice 3.0 (Apache 2.0) Apache License 2.0 google-guice 4.0 (Apache
  • Coremedia Operations Basics Coremedia Operations Basics |

    Coremedia Operations Basics Coremedia Operations Basics |

    CoreMedia 6 //Version 5.3.27 CoreMedia Operations Basics CoreMedia Operations Basics | CoreMedia Operations Basics Copyright CoreMedia AG © 2012 CoreMedia AG Ludwig-Erhard-Straße 18 20459 Hamburg International All rights reserved. No part of this manual or the corresponding program may be reproduced or copied in any form (print, photocopy or other process) without the written permission of CoreMedia AG. Germany Alle Rechte vorbehalten. CoreMedia und weitere im Text erwähnte CoreMedia Produkte sowie die entsprechenden Logos sind Marken oder eingetragene Marken der CoreMedia AG in Deutschland. Alle anderen Namen von Produkten sind Marken der jeweiligen Firmen. Das Handbuch bzw. Teile hiervon sowie die dazugehörigen Programme dürfen in keiner Weise (Druck, Fotokopie oder sonstige Verfahren) ohne schriftliche Genehmigung der CoreMedia AG reproduziert oder vervielfältigt werden. Unberührt hiervon bleiben die gesetzlich erlaubten Nutzungsarten nach dem UrhG. Licenses and Trademarks All trademarks acknowledged. 12.Feb 2013 CoreMedia Operations Basics 2 CoreMedia Operations Basics | 1. Introduction ...................................................................... 1 1.1. Audience ................................................................ 2 1.2. Typographic Conventions ........................................... 3 1.3. Change Chapter ....................................................... 4 2. System Requirements .......................................................... 5 2.1. Hardware Requirements ...........................................
  • Open Source Acknowledgements

    Open Source Acknowledgements

    This document acknowledges certain third‐parties whose software is used in Esri products. GENERAL ACKNOWLEDGEMENTS Portions of this work are: Copyright ©2007‐2011 Geodata International Ltd. All rights reserved. Copyright ©1998‐2008 Leica Geospatial Imaging, LLC. All rights reserved. Copyright ©1995‐2003 LizardTech Inc. All rights reserved. MrSID is protected by the U.S. Patent No. 5,710,835. Foreign Patents Pending. Copyright ©1996‐2011 Microsoft Corporation. All rights reserved. Based in part on the work of the Independent JPEG Group. OPEN SOURCE ACKNOWLEDGEMENTS 7‐Zip 7‐Zip © 1999‐2010 Igor Pavlov. Licenses for files are: 1) 7z.dll: GNU LGPL + unRAR restriction 2) All other files: GNU LGPL The GNU LGPL + unRAR restriction means that you must follow both GNU LGPL rules and unRAR restriction rules. Note: You can use 7‐Zip on any computer, including a computer in a commercial organization. You don't need to register or pay for 7‐Zip. GNU LGPL information ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You can receive a copy of the GNU Lesser General Public License from http://www.gnu.org/ See Common Open Source Licenses below for copy of LGPL 2.1 License.
  • Apache Geronimo Uncovered a View Through the Eyes of a Websphere Application Server Expert

    Apache Geronimo Uncovered a View Through the Eyes of a Websphere Application Server Expert

    Apache Geronimo uncovered A view through the eyes of a WebSphere Application Server expert Skill Level: Intermediate Adam Neat ([email protected]) Author Freelance 16 Aug 2005 Discover the Apache Geronimo application server through the eyes of someone who's used IBM WebSphere® Application Server for many years (along with other commercial J2EE application servers). This tutorial explores the ins and outs of Geronimo, comparing its features and capabilities to those of WebSphere Application Server, and provides insight into how to conceptually architect sharing an application between WebSphere Application Server and Geronimo. Section 1. Before you start This tutorial is for you if you: • Use WebSphere Application Server daily and are interested in understanding more about Geronimo. • Want to gain a comparative groundwork understanding of Geronimo and WebSphere Application Server. • Are considering sharing applications between WebSphere Application Server and Geronimo. • Simply want to learn and understand what other technologies are out there (which I often do). Prerequisites Apache Geronimo uncovered © Copyright IBM Corporation 1994, 2008. All rights reserved. Page 1 of 23 developerWorks® ibm.com/developerWorks To get the most out of this tutorial, you should have a basic familiarity with the IBM WebSphere Application Server product family. You should also posses a general understanding of J2EE terminology and technologies and how they apply to the WebSphere Application Server technology stack. System requirements If you'd like to implement the two technologies included in this tutorial, you'll need the following software and components: • IBM WebSphere Application Server. The version I'm using as a base comparison is IBM WebSphere Application Server, Version 6.0.
  • Full-Graph-Limited-Mvn-Deps.Pdf

    Full-Graph-Limited-Mvn-Deps.Pdf

    org.jboss.cl.jboss-cl-2.0.9.GA org.jboss.cl.jboss-cl-parent-2.2.1.GA org.jboss.cl.jboss-classloader-N/A org.jboss.cl.jboss-classloading-vfs-N/A org.jboss.cl.jboss-classloading-N/A org.primefaces.extensions.master-pom-1.0.0 org.sonatype.mercury.mercury-mp3-1.0-alpha-1 org.primefaces.themes.overcast-${primefaces.theme.version} org.primefaces.themes.dark-hive-${primefaces.theme.version}org.primefaces.themes.humanity-${primefaces.theme.version}org.primefaces.themes.le-frog-${primefaces.theme.version} org.primefaces.themes.south-street-${primefaces.theme.version}org.primefaces.themes.sunny-${primefaces.theme.version}org.primefaces.themes.hot-sneaks-${primefaces.theme.version}org.primefaces.themes.cupertino-${primefaces.theme.version} org.primefaces.themes.trontastic-${primefaces.theme.version}org.primefaces.themes.excite-bike-${primefaces.theme.version} org.apache.maven.mercury.mercury-external-N/A org.primefaces.themes.redmond-${primefaces.theme.version}org.primefaces.themes.afterwork-${primefaces.theme.version}org.primefaces.themes.glass-x-${primefaces.theme.version}org.primefaces.themes.home-${primefaces.theme.version} org.primefaces.themes.black-tie-${primefaces.theme.version}org.primefaces.themes.eggplant-${primefaces.theme.version} org.apache.maven.mercury.mercury-repo-remote-m2-N/Aorg.apache.maven.mercury.mercury-md-sat-N/A org.primefaces.themes.ui-lightness-${primefaces.theme.version}org.primefaces.themes.midnight-${primefaces.theme.version}org.primefaces.themes.mint-choc-${primefaces.theme.version}org.primefaces.themes.afternoon-${primefaces.theme.version}org.primefaces.themes.dot-luv-${primefaces.theme.version}org.primefaces.themes.smoothness-${primefaces.theme.version}org.primefaces.themes.swanky-purse-${primefaces.theme.version}
  • Meaningful Method Names

    Meaningful Method Names

    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by NORA - Norwegian Open Research Archives Meaningful Method Names Doctoral dissertation by Einar W. Høst Submitted to the Faculty of Mathematics and Natural Sciences at the University of Oslo in partial fulfillment of the requirements for the degree Philosophiae Doctor in Computer Science November 2010 © Einar W. Høst, 2011 Series of dissertations submitted to the Faculty of Mathematics and Natural Sciences, University of Oslo No. 1044 ISSN 1501-7710 All rights reserved. No part of this publication may be reproduced or transmitted, in any form or by any means, without permission. Cover: Inger Sandved Anfinsen. Printed in Norway: AIT Oslo AS. Produced in co-operation with Unipub. The thesis is produced by Unipub merely in connection with the thesis defence. Kindly direct all inquiries regarding the thesis to the copyright holder or the unit which grants the doctorate. Abstract We build computer programs by creating named abstractions, aggregations of be- haviour that can be invoked by referring to the name alone. Abstractions can be nested, meaning we can construct new, more powerful abstractions that use more primitive abstractions. Thus we can start from tiny blocks of behaviour and build ar- bitrarily complex systems. For this to work, however, the abstractions must be sound — in other words, the names must suit the behaviour they represent. Otherwise our tower of abstractions will collapse. Hence we see the crucial importance of naming in programming. Despite this importance, programmers almost completely lack tools to assist them. The computer treats names as arbitrary, allowing for sloppy and inconsistent naming.