DOCSLIB.ORG

Software Lifecycle, Libraries, and Apis CSC216

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Software Lifecycle, Libraries, and Apis CSC216 12/27/2012 Software Lifecycle, Libraries, and APIs CSC216 CSC216: Programming Concepts © Sarah Heckman 1 CSC216: Programming Concepts © Sarah Heckman 2 1 12/27/2012 Software Process •Software Process Development Phases – Requirements/Analysis –Design – Implementation/Code –Testing –Integration – Maintenance •Software Artifacts: any document, file, or tangible creation related to the software or its creation or maintenance. CSC216: Programming Concepts © Sarah Heckman 3 Requirements/Analysis •Goal: Understand customer requirements for the software system •Very difficult to “get right” the first time through • Requirements may evolve over the course of developing a software system. •Software Artifacts: requirements documents, use cases, user stories CSC216: Programming Concepts © Sarah Heckman 4 2 12/27/2012 Design •Goal: decide the structure of the software and the hardware configurations that support it. •How individual classes and software components work together in the software system –Small programs: ~ 10 classes and interfaces –Medium programs: 1000s of classes and interfaces •Design for single user applications different from web applications and mobile applications •Software Artifacts: design documents, class diagrams, other UML diagrams CSC216: Programming Concepts © Sarah Heckman 5 Implementation/Code •Goal: translating design into a concrete system (i.e. code) •Can use any language, but some languages are better suited to certain types of programs than others •Software Artifacts: source code, documentation, configuration files, media, executables, bug database, source code repository CSC216: Programming Concepts © Sarah Heckman 6 3 12/27/2012 Testing •Goal: Execute software with intent of finding errors • While you can’t test until there is code to run, you can start planning testing when your analyzing the requirements •Software Artifacts: test code (including test harnesses, scaffolding, etc.), bug database, test database, test inputs and outputs, documentation CSC216: Programming Concepts © Sarah Heckman 7 Integration •Goal: to bring the entire software system together • Individual programmers or pairs work together on parts of the system. Integration brings all the pieces together into a working whole •Software Artifacts: APIs, interfaces, integration documentation CSC216: Programming Concepts © Sarah Heckman 8 4 12/27/2012 Maintenance •Goal: upgrade and fix the software after delivery •Just because you deliver your software doesn’t mean you’re done with it –Work on the next version –Fix bugs in the current version •Software Artifacts: all! CSC216: Programming Concepts © Sarah Heckman 9 Software Models •Software Models are generalized approaches to software development that incorporate the phases in different ways –Waterfall –Spiral – Iterative CSC216: Programming Concepts © Sarah Heckman 10 5 12/27/2012 The Waterfall Model of the Software Life Cycle Notice back/ feedback arrows. CSC216: Programming Concepts © Sarah Heckman 11 Spiral Model Determine objectives, Evaluate alternatives, alternatives, & constraints identify & resolve risks Risk analysis Risk analysis Risk analysis P1 Prototype3 Prototype2 Prototype1 Requirements Concept of plan operation Software System Requirements Product Detailed Design Design Development Requirements plan validation P2 Code Integration Design plan validation Unit Test Develop & verify Plan next phase next level product Integration & Test A prototype is released Acceptance each “circuit.” Some Test prototypes are specifications. Part of circuit n is CSC216:evaluating Programming Concepts circuit © Sarah Heckman n‐1. 12 6 12/27/2012 Iterative Model Iterative fundamentally means “redo.” Output from an iteration is examined for modification. CSC216: Programming Concepts © Sarah Heckman 13 Libraries •A library is a 3rd party collection of code that can be used in other programs –Promotes code reuse –Don’t need to “reinvent the wheel” to complete common tasks –Example: Java API –Example: JUnit CSC216: Intro to Java Programming © Sarah Heckman 14 7 12/27/2012 Using Libraries • Download the Library • Install the Library –An executable (Java Libraries) –A jar executable to download rest of library (JAXB) –A jar file (JUnit, Apache libraries, etc.) • Include Library on path when compiling and executing your application CSC216: Intro to Java Programming © Sarah Heckman 15 Classpaths •The path(s) where Java looks for libraries (i.e., referenced code) when compiling and running a program •Use the –cp argument to the java command • Separate directories/jars with a semi‐colon (;) •Each jar should be listed individually – You cannot specify a directory of jars • Alternatively, you can update the System’s PATH environment variable –Make sure you restart your terminal so the new path will be available CSC216: Intro to Java Programming © Sarah Heckman 16 8 12/27/2012 Using Libraries on the Command Line • Command to compile and run – Assumption is that the project is set up in directory structure like Eclipse project eos% javac -d bin -sourcepath src -sourcepath test -cp path1;path2;path3 src/pack/age1/*.java src/pack/age2/*.java test/pack/age2/*.java eos% java -cp ./bin;path1;path2;path3 pack.age1.ClassName CSC216: Intro to Java Programming © Sarah Heckman 17 Creating a User Library in Eclipse •Right‐click on your project, select Build Path > Configure Build Path • Select Add Library … > User Library > User Libraries…. • Select New and give your library a name. You do NOT need to add your library to the system path –But if you do add it to the system path, you can use it from the command line • Select your library and press the Add Jars button. Brows your file system and select the *.jar files appropriate for your library. Press OK. Press Finish. Press OK. CSC216: Intro to Java Programming © Sarah Heckman 18 9 12/27/2012 Creating a User Library in Eclipse (2) •If working with a partner, you should agree on a library name (case matters) • Each partner will create a local version of the library that points to the jar(s) on their system •The project must have the library name associated with it •If there are build path errors, the project icon will be highlighted with a big red explanation point! CSC216: Intro to Java Programming © Sarah Heckman 19 Other Library Setups •Some projects store all relevant *.jar files in a lib/ directory –Jars are added to lib in file system –In Eclipse, select the Add Jar option and add the jar(s) • Building applications, like Maven, will download the required jar(s) from online repositories • Building applications, like Ant and Maven, simplify compilation and running when using the command line rather than an IDE CSC216: Intro to Java Programming © Sarah Heckman 20 10 12/27/2012 APIs •API: Application Programming Interface –Series of webpages –Describe the public classes, interfaces, and methods of Java class libraries –Describe what functionality is available for you, the client, of the libraries to use •Example of abstraction –API tells you what a class can do, but doesn’t tell you how the class does it •Java 1.6 API: http://java.sun.com/javase/6/docs/api/ CSC216: Programming Concepts © Sarah Heckman 21 API Layout • Packages: Upper left • Classes: Lower left • Details: Main frame –List of packages and descriptions –List of classes and descriptions –List of class members and descriptions • Inheritance hierarchy • Public fields and constants • Constructors • Methods CSC216: Programming Concepts © Sarah Heckman 22 11 12/27/2012 Creating Our Own APIs • Sometimes we’re the client of a library –Java API –3rd Party Libraries – JFreeChart, JUnit, JAXB, etc. • Sometimes we’re writing code that others will use – Need to provide an API for those clients • Sometimes we’re working with a large team and other members of the team may need to know what we’re doing – Need to provide high level details CSC216: Programming Concepts © Sarah Heckman 23 Javadoc • Javadoc comments are used to generate API pages • Javadoc comments are processed by a doclet –A Doclet is a Java program that generates documentation with a standard format from comments in your source code. • Command to create Javadoc % javadoc [comma-separated list of source files] •See CSC Style Guidelines for directions on how to Javadoc your code • Eclipse will write a lot of Javadoc for you •All classes, methods, and fields MUST be Javadoced for projects –This includes test classes and methods! –You will also generate Javadoc and submit that with your zipped Eclipse project to Moodle! CSC216: Programming Concepts © Sarah Heckman 24 12 12/27/2012 Javadoc Comments •Start with /** and end with */ –There are 2 *s after the initial / • Javadoc comments are placed immediately before whatever they are commenting –No additional new lines! • Javadoc tags start with @ and specify additional information about code that is handled in a specific way CSC216: Programming Concepts © Sarah Heckman 25 Javadoc – Class Level import java.util.Scanner; /** * A description of what the class * does. The more detailed the * better * @author Author Name * @version 1.0 */ public class MyClass { … } CSC216: Programming Concepts © Sarah Heckman 26 13 12/27/2012 Javadoc – Method Level /** * Describe what the method does * at the top. If it returns * something, start with “Returns * …”. * @param paramName1 param desc. * @param paramName2 param desc. * @return description of return */ public <return> myMethod(<type> paramName1, <type> paramName2) { … } CSC216: Programming Concepts © Sarah Heckman 27 Javadoc – Instance Fields public class MyClass { /** Describe field */ private <type> myField; /** * Describe field */ private <type> myField2; … } CSC216: Programming Concepts © Sarah Heckman 28 14 12/27/2012 References • http://www.di.net.au/blog/index.php/2009/05/ the‐lighter‐side‐of‐the‐software‐process/ •Laurie Williams, Process Models slides: http://agile.csc.ncsu.edu/SEMaterials/ProcessM odels.pdf CSC216: Programming Concepts © Sarah Heckman 29 15.
Load more

Recommended publications
  • Java Programming Standards & Reference Guide
    Java Programming Standards & Reference Guide Version 3.2 Office of Information & Technology Department of Veterans Affairs Java Programming Standards & Reference Guide, Version 3.2 REVISION HISTORY DATE VER. DESCRIPTION AUTHOR CONTRIBUTORS 10-26-15 3.2 Added Logging Sid Everhart JSC Standards , updated Vic Pezzolla checkstyle installation instructions and package name rules. 11-14-14 3.1 Added ground rules for Vic Pezzolla JSC enforcement 9-26-14 3.0 Document is continually Raymond JSC and several being edited for Steele OI&T noteworthy technical accuracy and / PD Subject Matter compliance to JSC Experts (SMEs) standards. 12-1-09 2.0 Document Updated Michael Huneycutt Sr 4-7-05 1.2 Document Updated Sachin Mai L Vo Sharma Lyn D Teague Rajesh Somannair Katherine Stark Niharika Goyal Ron Ruzbacki 3-4-05 1.0 Document Created Sachin Sharma i Java Programming Standards & Reference Guide, Version 3.2 ABSTRACT The VA Java Development Community has been establishing standards, capturing industry best practices, and applying the insight of experienced (and seasoned) VA developers to develop this “Java Programming Standards & Reference Guide”. The Java Standards Committee (JSC) team is encouraging the use of CheckStyle (in the Eclipse IDE environment) to quickly scan Java code, to locate Java programming standard errors, find inconsistencies, and generally help build program conformance. The benefits of writing quality Java code infused with consistent coding and documentation standards is critical to the efforts of the Department of Veterans Affairs (VA). This document stands for the quality, readability, consistency and maintainability of code development and it applies to all VA Java programmers (including contractors).
    [Show full text]
  • Exceptions and Libraries
    9/7/2016 Exceptions and Libraries RS 9.3, 6.4 Some slides created by Marty Stepp http://www.cs.washington.edu/143/ Edited by Sarah Heckman CSC216: Programming Concepts –Java © NC State CSC216 Faculty 1 Exceptions • exception: An object representing an error or unusual condition. – unchecked exceptions: One that does not have to be handled for the program to compile – checked exception: One that must be handled for the program to compile. • What are some unchecked and checked exceptions? • What may cause unchecked or checked exceptions? • For any checked exception, you must either: –also throw that exception yourself – catch (handle) the exception CSC216: Programming Concepts –Java © NC State CSC216 Faculty 2 1 9/7/2016 Throwing an exception public type name(params) throws type { • throws clause: Keywords on a method's header that states that the method may generate an exception. – You only need to list the checked exceptions for compilation – Good form to list all exceptions (including unchecked exceptions) –Example: public class ReadFile { public static void main(String[] args) throws FileNotFoundException { } "I hereby announce that this method might throw an exception, and the caller must accept the consequences if it happens." CSC216: Programming Concepts –Java © NC State CSC216 Faculty 3 Catching an exception try { statement(s); } catch (ExceptionType name) { code to handle the exception } – The try code executes – at least one statement should potentially cause an exception • A method call that throws an exception – If the exception
    [Show full text]
  • Perspectives on Free and Open Source Software.Pdf
    Perspectives on Free and Open Source Software Perspectives on Free and Open Source Software edited by Joseph Feller, Brian Fitzgerald, Scott A. Hissam, and Karim R. Lakhani The MIT Press Cambridge, Massachusetts London, England © 2005 Massachusetts Institute of Technology All rights reserved. No part of this book may be reproduced in any form by any electronic or mechanical means (including photocopying, recording, or information storage and retrieval) without permission in writing from the publisher. MIT Press books may be purchased at special quantity discounts for business or sales promotional use. For information, please e-mail [email protected] or write to Special Sales Department, The MIT Press, 5 Cambridge Center, Cambridge, MA 02142. This book was set in Stone sans and Stone serif by SNP Best-set Typesetter Ltd., Hong Kong. Printed and bound in the United States of America. Library of Congress Cataloging-in-Publication Data Perspectives on free and open source software / edited by Joseph Feller . [et al.]. p. cm. Includes bibliographical references and index. ISBN 0-262-06246-1 (alk. paper) 1. Shareware (Computer software) 2. Open source software. 3. Computer software—Development. I. Feller, Joseph, 1972– QA76.76.S46P47 2005 005.36—dc22 2004064954 10987654321 My love, thanks and humble apologies go to my very patient and supportive family: Carol, Caelen, Damien, and Dylan. JF Arís as Gaeilge: Buíochas mór le mo chlann, Máire, Pól agus Eimear. Is mór agam an iarracht a rinne sibh ar mo shon. BF With heartfelt warmth, I dedicate this book to my wife, Jacqueline, and my two sons, Derek and Zachery, who bring meaning to everything I do.
    [Show full text]
  • This Hands-On Book Shows Readers Why and How Common Java Development Problems Can Be Solved by Using New Aspect-Oriented Program
    AspectJ Cookbook By Russell Miles Publisher: O'Reilly Pub Date: December 2004 ISBN: 0-596-00654-3 Pages: 354 Table of • Contents • Index • Reviews Reader This hands-on book shows readers why and how common Java • Reviews development problems can be solved by using new Aspect-oriented • Errata programming (AOP) techniques. With a wide variety of code recipes for • Academic solving day-to-day design and coding problems using AOP's unique approach, AspectJ Cookbook demonstrates that AOP is more than just a concept; it's a development process that will benefit users in an immediate and visible manner. AspectJ Cookbook By Russell Miles Publisher: O'Reilly Pub Date: December 2004 ISBN: 0-596-00654-3 Pages: 354 Table of • Contents • Index • Reviews Reader • Reviews • Errata • Academic Copyright Preface Audience About This Book Assumptions This Book Makes Conventions Used in This Book Using the Code Examples We'd Like to Hear from You Safari Enabled Acknowledgments Chapter 1. Aspect Orientation Overview Section 1.1. A Brief History of Aspect Orientation Section 1.2. AspectJ Section 1.3. A Definition of Aspect Orientation Section 1.4. Where to Go for More Information Chapter 2. Getting Started with AspectJ Introduction Recipe 2.1. Installing AspectJ Recipe 2.2. Developing a Simple Aspect Recipe 2.3. Compiling an Aspect and Multiple Java Files Recipe 2.4. Weaving Aspects into Jars Recipe 2.5. Weaving Aspects at Load Time Recipe 2.6. Generating Javadoc Documentation Recipe 2.7. Compiling an AspectJ Project Using Eclipse Recipe 2.8. Selecting the Aspects That Are Woven in a Build Within Eclipse Recipe 2.9.
    [Show full text]
  • JDK 9 Outreach JDK 9 Outreach
    JDK 9 Outreach JDK 9 Outreach JDK 9 Outreach Introduction Caveat Lector JDK 9 Features The Little Things JDK 9 Early Access Builds Look for unrecognized VM options Run jdeps on your code Update your dependencies Cross compilation for older platform versions Testing Your Code JDK 9 changes that may affect your code Added OCSP Stapling for TLS Multi-Release JAR Files Parser API for Nashorn Prepare for v53 class files Prepare JavaFX UI Controls & CSS APIs for Modularization Validate JVM Command-Line Flag Arguments XML Catalogs Platform-Specific Desktop Features Changed Arrays.asList(x).toArray() returns Object[] Create PKCS12 Keystores by Default Disable SHA-1 Certificates Enable GTK 3 on Linux Encapsulate Most Internal APIs HarfBuzz Font-Layout Engine Indify String Concatenation Make G1 the Default Garbage Collector Marlin Graphics Renderer Modular Run-Time Images New Version-String Scheme Unified GC Logging Unified JVM Logging Use CLDR Locale Data by Default UTF-8 Property Files Removed Remove apple script engine code in jdk repository Remove GC Combinations Deprecated in JDK 8 Remove HTTP Proxy implementation from RMI Remove Launch-Time JRE Version Selection Remove java-rmi.exe and java-rmi.cgi Remove the JVM TI hprof Agent Remove the jhat Tool Removed API references to java.awt.peer and java.awt.dnd.peer packages Removed Packer/Unpacker addPropertyChangeListener and removePropertyChangeListener methods Removed LogManager addPropertyChangeListener and removePropertyChangeListener methods Removed com.sun.security.auth.callback.DialogCallbackHandler
    [Show full text]
  • BOF1932-JAX-RS-REST-Services-And-Angular.Js-Too
    JAX-RS and AngularJS Tools for even beer experience Mar0n Mares So4ware developer Oracle September 30, 2014 Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Safe Harbor Statement The following is intended to outline our general product direc0on. It is intended for informaon purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or func0onality, and should not be relied upon in making purchasing decisions. The development, release, and 0ming of any features or func0onality described for Oracle’s products remains at the sole discre0on of Oracle. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. 4 Program Agenda 1 Decide if this BoF is for You 2 JAX-RS and AngularJS 3 Day by day TOI (documentaon) 4 Do not change your API (DTO support) 5 Few more notes Copyright © 2014, Oracle and/or its affiliates. All rights reserved. 5 About this presentaon Primary audience, presentaon style and content • So4ware development team leader – Developer who is responsible for project development phase and final design dessign – Not project manager • We will browse the code – Sources, console, browser – (I have a lot of slides, too) • Series of introduc0on level descrip0on of various tools – Star0ng with JAX-RS and AgularJS – why it well fits together – Demonstraon of other tools – JAVA TOOLS Copyright © 2014, Oracle and/or its affiliates. All rights reserved. 6 About this presentaon Mo@va@on – few lines of philosophy • Java and JavaScript – Same name and so different styles • Stac - dynamic type language • Refactor every day – never refactor – Must cooperate: Accept differences and define gray zone • Java and JavaScript developers – Do you have 2in1 in your team? Good for you but it is probably not true – Find same paerns in gray zone – Leverage from unique style Copyright © 2014, Oracle and/or its affiliates.
    [Show full text]
  • Design of a Jmldoclet for Jmldoc in Openjml
    University of Central Florida STARS Electronic Theses and Dissertations, 2004-2019 2016 Design of a JMLdoclet for JMLdoc in OpenJML Arjun Mitra Reddy Donthala University of Central Florida Part of the Computer Sciences Commons Find similar works at: https://stars.library.ucf.edu/etd University of Central Florida Libraries http://library.ucf.edu This Masters Thesis (Open Access) is brought to you for free and open access by STARS. It has been accepted for inclusion in Electronic Theses and Dissertations, 2004-2019 by an authorized administrator of STARS. For more information, please contact [email protected]. STARS Citation Donthala, Arjun Mitra Reddy, "Design of a JMLdoclet for JMLdoc in OpenJML" (2016). Electronic Theses and Dissertations, 2004-2019. 5132. https://stars.library.ucf.edu/etd/5132 DESIGN OF A JMLDOCLET FOR JMLDOC IN OPENJML by ARJUN MITRA REDDY DONTHALA B.S. GITAM University, 2014 A thesis submitted in partial fulfillment of the requirements for the degree of Master of Science in the Department of Computer Science in the College of Engineering and Computer Science at the University of Central Florida Orlando, Florida Summer Term 2016 © 2016 ARJUN MITRA REDDY DONTHALA ii ABSTRACT The Java Modeling Language (JML) is a behavioral interface specification language designed for specifying Java classes and interfaces. OpenJML is a tool for processing JML specifications of Java programs. To facilitate viewing of these specifications in a user-friendly manner, a tool JMLdoc was created. The JMLdoc tool adds JML specifications to the usual Javadoc documentation. JMLdoc is an enhancement of Javadoc that adds to the Javadoc documentation the JML specifications that are present in the source code.
    [Show full text]
  • Integrations
    Integrations Version 2.9 October 2014 This document applies to Ehcache Version 2.9 and to all subsequent releases. Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions. Copyright © 2014 Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors. The name Software AG and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA Inc. and/or its subsidiaries and/or its affiliates and/or their licensors. Other company and product names mentioned herein may be trademarks of their respective owners. Detailed information on trademarks and patents owned by Software AG and/or its subsidiaries is located at hp://documentation.softwareag.com/legal/. Use of this software is subject to adherence to Software AG's licensing conditions and terms. These terms are part of the product documentation, located at hp://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s). This software may include portions of third-party products. For third-party copyright notices and license terms, please refer to "License Texts, Copyright Notices and Disclaimers of Third Party Products”. This document is part of the product documentation, located at hp://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s). Document ID: EHC-INT-29-20141015 M Table of Contents Table of Contents Using Ehcache with Hibernate.......................................................................................................5 About Using Ehcache with Hibernate.........................................................................................6 Downloading and Installing Ehcache for Hibernate..................................................................
    [Show full text]
  • Javadoc Tool What For?
    JavaDoc Tool Vishnu Kotrajaras Extraction from Java Documentation What for? • Making HTML documentation – allows you to generate documentation for source files whose code is incomplete or erroneous. – So we can generate documentation before all debugging and troubleshooting is done. – classes you create must either be loaded as an extension or in the Javadoc tool's class path. 1 Default page creation • Basic Content Pages – One class or interface page (classname.html) for each class or interface it is documenting. – One package page (package-summary.html) for each package it is documenting. The Javadoc tool will include any HTML text provided in a file named package.html in the package directory of the source tree. – One overview page (overview-summary.html) for the entire set of packages. This is the front page of the generated document. The Javadoc tool will include any HTML text provided in a file specified with the - overview option. Note that this file is created only if you pass into javadoc two or more package names. • Cross-Reference Pages – One class hierarchy page for the entire set of packages (overview-tree.html). To view this, click on "Overview" in the navigation bar, then click on "Tree". – One class hierarchy page for each package (package- tree.html) To view this, go to a particular package, class or interface page; click "Tree" to display the hierarchy for that package. – One "use" page for each package (package-use.html) and a separate one for each class and interface (class- use/classname.html). Given a class or interface A, its "use" page includes • subclasses of A • fields declared as A • methods that return A • and methods and constructors with parameters of type A.
    [Show full text]
  • IDE Users Guide
    IDE Users Guide Common IDE Tasks BEA Workshop for WebLogic Platform (Workshop for WebLogic) is a full-featured IDE for enterprise application development (SOA, J2EE, web applications). Workshop for WebLogic is based on the Eclipse framework. Topics Included in This Current Release Information: Section ● What's New Tutorial: Getting Started with BEA ● Upgrading to 10.0 Workshop for WebLogic Platform Introductory tutorial that takes you Useful Links: through the basics of the IDE: navigation, features, help, as well as the process of ● Tutorials creating and testing a "Hello, world!" application. ● Tips and Tricks Applications and Projects Other Resources: Description of how to assemble enterprise ● Online Docs applications from projects/modules. ● Dev2Dev Managing Project Dependencies ● Discussion Forums Description of how to set up dependencies between EAR projects and their web and ● Development Blogs EJB/utility projects. Understanding the Build Process Discussion of how to build your files before deployment. Before you Begin: Setting Up the Server Description of how to set up a server for development and testing. Managing Servers Description of how to manage development/testing servers. Deploying, Running, and Debugging Applications Explanation of how to deploy, run and debug enterprise applications. Setting up Logging Discussion of WebLogic Server message logging. file:///F|/depot/dev/src/workshop/product/plugins/com.bea....shop.product.wl.doc/html/ideuserguide/navIDEUserGuide.html (1 of 2)1/26/2007 2:42:51 PM IDE Users Guide Working with Source Control Description of how to check workspaces and projects into source control. Exporting Archives Description of how to export projects as EARs, WARs, or JARs.
    [Show full text]
  • Siebel Database Reorganization
    A Javadoc Primer Prepared by Jeff Hunter, Sr. DBA 03-SEP-2002 Overview Traditionally, when you write a program you must write a separate document recording how the program works. When the program changes, the separate documentation must change as well. For large programs that are constantly being changed and improved, it is a tedious and error-prone task to keep the documentation consistent with the actual code. Javadoc is a tool from Sun Microsystems for generating API documentation in HTML format from what are known as doc comments in the source code. Javadoc will describe (by default) all public and protected classes, nested classes (but not anonymous inner classes), interfaces, constructors, methods, and fields. This article provides a brief overview of the Javadoc tool, common conventions as well as several common examples. Description You can run the Javadoc tool on entire packages, individual source files, or both. In the first case, you pass in as an argument to javadoc a series of package names. In the second case you pass in a series of source “.java” filenames. Examples are given at the end of this document. Javadoc can only be run on source files and packages. Once you have run Javadoc and want to view the generated HTML, the topmost page is named packages.html (in Javadoc 1.1) or index.html (in Javadoc 1.2 and later). NOTE - When you pass in package names to the Javadoc tool, it currently processes all “.java” classes in the specified package directories, even if the “.java” files are code examples or other classes that are not actually members of the specified packages.
    [Show full text]
  • ARCHIVED: Pooled JVM in CICS Transaction Server V3
    Front cover ARCHIVED: Pooled JVM in CICS Transaction Server V3 Archived IBM Redbooks publication covering ‘Pooled JVM’ in CICS TS V3 'Pooled JVM’ was superseded by CICS ‘JVM server’ in CICS TS V4 ‘Pooled JVM’ infrastructure was removed in CICS TS V5 Chris Rayns George Burgess Scott Clee Tom Grieve John Taylor Yun Peng Ge Guo Qiang Li Qian Zhang Derek Wen ibm.com/redbooks International Technical Support Organization ARCHIVED: Pooled JVM in CICS Transaction Server V3 June 2015 SG24-5275-04 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. Fifth Edition (June 2015) This edition applies to Version 3, Release 2, CICS Transaction Server . © Copyright International Business Machines Corporation 2015. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . .x Preface . xi The team that wrote this book . xi Become a published author . xiv Comments welcome. xiv Summary of changes. .xv June 2015, Fifth Edition . .xv Part 1. Overview . 1 Chapter 1. Introduction. 3 1.1 z/OS . 5 1.2 CICS Transaction Server Version 3 . 7 1.3 Java overview . 8 1.3.1 Java language. 8 1.3.2 Java Virtual Machine. 10 1.3.3 Java on z/OS . 10 1.3.4 Runtime Environment and tools . 11 1.4 CICS Transaction Server for z/OS 3.2 enhancements for Java . 13 1.4.1 Usability enhancements . 13 1.4.2 Java Virtual Machines management enhancements . 14 1.4.3 Continuous Java Virtual Machines versus resettable Java Virtual Machines .
    [Show full text]