DOCSLIB.ORG

Eclipse and Its Corona: Inside a Large Scale Open Source Project

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Eclipse and Its Corona: Inside a Large Scale Open Source Project Eclipse and its Corona Inside a Large Scale Open Source Project - What Can we Learn From Open Source Aldo Eisma Consulting IT Specialist IBM Global Services [email protected] © 2004 IBM Corporation What is Eclipse? © 2004 IBM Corporation What is Eclipse? • Eclipse - an open extensible IDE for anything and nothing in particular… + out-of-box function and quality to attract developers a development environment for itself + endorsement (i.e, products) by some major tool vendors + open-source and supports open source development ¾ industry standard tools platform © 2004 IBM Corporation Why Should You Care? • as a tool developer… – seamless tool integration – you no longer have to start from scratch – everybody can become a tool smith ¾ Eclipse changes the way tools are built • as a Java developer… – you get a state-of-the-art Java IDE that you can tweak ¾ but Eclipse is more than a Java IDE • as a user… • you get tools from different suppliers to make a tool environment the way you want it ¾ freedom of choice © 2004 IBM Corporation The Way to Eclipse 1997 1998 19992000 2001 2002 2003 2004 VisualAge/Java VisualAge Micro Edition Eclipse June Oct Nov June March June Tech 1.0 Open 2.0 2.1 3.0 Preview Source announcement © 2004 IBM Corporation Goals • Provide open platform for application development tools – run on a wide range of operating systems – GUI and non-GUI • Language-neutral – permit unrestricted content types – HTML, Java, C/C++, JSP, EJB, XML, GIF, … • Facilitate seamless tool integration – add new tools to existing installed products • Attract community of tool developers – including independent software vendors (ISVs) – capitalize on popularity of Java for writing tools © 2004 IBM Corporation Why Open Source? • Full life cycle tool support requires contributions from partners • Options: 1. proprietary APIs 2. defined APIs plus Open Source • Partners want Open Source – less dependency on IBM – freedom of action for partners: • complement IBM products • implement their own products ¾ Platform rule: the more ISVs - the more relevant is the platform © 2004 IBM Corporation eclipse.org • Eclipse Project – builds the Platform – adapt, evolve to meet needs of the community • Eclipse Tools Project – best of breed tools • Eclipse Technology Project – research, incubation, education • Web Tools Platform Project – build tooling for enterprise applications © 2004 IBM Corporation – just forming… eclipse.org • Eclipse Project Project – Platform – JDT: Java Development Tools Subprojects – PDE: Plug-in Development Environment • Eclipse Tools – GEF: Graphical Editing Framework – EMF, VE, UML2: Modeling frameworks and tools – Hyades: Test, Trace and Monitoring tools – CDT, Cobol: programming tools • Technology – AJDT: Aspect-oriented Java development tools – Equinox: new more dynamic plug-in architecture © 2004 IBM Corporation – … Eclipse Community • Open Source is a “community thing” – an active community is the major asset of an OS project • OS project gives and takes: – OS developer gives: • listen to feedback and react • demonstrate continuous progress • transparent development – OS developer takes: • answer user questions so that developers do not have to do it • report defects and feature requests • validate technology by writing plug-ins • submit patches and enhancements • Give and take isn’t always balanced – community isn’t shy and is demanding © 2004 IBM Corporation Community (Cont’d) • Increase the knowledge-level of the community • Requires intense communication – mailing list, newsgroups • news group now mostly self supporting – user maintained wiki • Community events – code camps – work with committers on your projects – “sprints” – committers meet to work on the OS project – EclipseCon – tech community conference © 2004 IBM Corporation Growth of a Community • Vendors are committing to Eclipse –Over 175 vendors including significant commitments from Rational, TogetherSoft, Serena, QNX, Merant – C/C++ IDE plug-in for Linux being led by QNX with RedHat, Rational, and MontaVista •Over 600 open source or freeware plug-in projects available – 450+ plug-ins at: www.eclipse-plugins.info – 150+ plug-ins at: www.eclipse-workbench.com • 50 Eclipse Innovation Grants Approved © 2004 IBM Corporation Open Source Questions • Impact of transition to Open Source? • Is Open Source chaotic? • What are the contributions? • Open Source and quality? • Planning an Open Source project? • Open Source and business? © 2004 IBM Corporation Transitioning to Open Source • Challenges – transparency • the community has to be able to observe what is going on to participate – educate community ¾ this takes time and conflicts with the IBM “shipping software” goal • not all developers enjoy Open Source exposure – loss of the product support “firewall” • developers interact with customers directly ¾ initial slow-down due to community engagement but increased transparency © 2004 IBM Corporation Adopting Open Source Tools • Open Source projects use a common set of tools • Software development: – version configuration management: CVS – build system: Ant – unit testing: JUnit ¾ Integrate OS tools into Eclipse • Collaboration: – bug tracking: Bugzilla – newsgroups/mailing list – user collaboration: Wiki Web •FAQ © 2004 IBM Corporation Open Source Tools (Cont’d) • Open Source tools are Open Source – high quality – validated for distributed development • Transition to OS tools was (surprisingly) smooth © 2004 IBM Corporation Chaotic? • OS projects are highly structured – with explicit rules • Commit right rules: public “meritocracy” – only a small number of developers can modify the source base – key architecture defined by a small team of lead developers – peer pressure among committers – continuous reviewing – contributions from outside (patches) have to be reviewed by committers © 2004 IBM Corporation Contributions? Who is Reporting Bugs? • Eclipse 2.1 (6 months) – Consortium organizations: 7100 defects (= 1185 / m) month) • 341 reporters – Open source community: 3560 defects (= 595 / m) • 1212 reporters © 2004 IBM Corporation Contributions? Code • Eclipse 2.1 – 42 contributions • Expectation level for contributions is high – platform contributions have to have product quality – conforming to all the conventions is difficult • Larger contributions usually start as independent plug-ins • Products can introduce certification process for external plug-ins – Example: “Ready for WebSphere Studio Software plug-in ” © 2004 IBM Corporation Quality? Continuous Integration • Fully automated build process – Ant based • Build quality verified by JUnit tests – for a successful Eclipse build > 10’000 JUnit tests have to pass • Staged builds – nightly builds, weekly integration builds, monthly mile stone builds • “Eat your own dog food” © 2004 IBM Corporation Planning Product requirements suggest improvements Eclipse Products Committers commit to plan Project Management Committee posts draft plan ¾plans start in embryonic form PlanPlan and are revised throughout the Community release cycle ¾milestones/time boxes enhancements are fixed early on feature requests bug votes © 2004 IBM Corporation Business? • Business opportunities – support – services and education – enhancements, e.g., easy install, better documentation – customization • Who are those guys? – BCG study of 678 Open Source Developers • 58% professional IT programmers • 30% Open Source is their job! © 2004 IBM Corporation Extending Eclipse for Fun and Profit… Commercial Development Environments IBM SAP Websphere Studio family NetWeaver Developer Studio Eclipse SDK Eclipse SDK Commercial Add-Ons IBM SAP Websphere Studio family NetWeaver Developer Studio Eclipse SDK Eclipse SDK © 2004 IBM Corporation Instantiations, Borland, Sitraka, SlickEdit… Business? Complementary Products Generate Revenue Enterprise Developer • Enterprise XDE development Rational Rational Application Developer – Integration Edition organizations • Advanced • Web services J2EE based Application Developer developers enterprise modernization • J2EE • Flow developers composition • Enterprise Site Developer modeling and • Visual • Relational RAD • Professional Web, Java, and DB tools adapter Device Developer creation Web services developers • Embedded • Java, XML, Rich media, and WebSphere • Business Web services Application rule support Server WebSphere Studio Workbench IBM’s commercially supported version of the Eclipse Workbench © 2004 IBM Corporation Is it Paying Off? • Internal: tool strategies have aligned – all IBM tools build on top of Eclipse • Perception: Eclipse has a significant impact – “IBM is cool” • Products: a complete set of integrated tools is now available – enterprise application development – modeling (Rational) –C/C++ IDE ⇒ not built by IBM ¾ 175 tool vendors are providing plug-ins for Eclipse • Community: a growing asset – testing, feedback, contributions • Costs: fixed cost ⇒ IBM needs such a platform anyways© 2004 IBM Corporation So? (easy…) • Join the Eclipse community and use Eclipse as… – … your tools platform • vendor support available if desired • “now any Joe Engineer can take the Eclipse product and be productive” – CIO Magazine Apr 15 ¾listen to your top developers – … a platform for building your own products • CPL license allows shipping commercial products • freedom about adding to WS studio or build your own tools –… a Rich Client Platform for your own applications • leverage the proven Eclipse architecture and UI for your own rich client applications ¾ don’t be afraid of Open Source products © 2004 IBM Corporation
Load more

Recommended publications
  • IMS Connector for Java User's Guide and Reference
    IBM VisualAge® for Java™,Version3.5 IMSConnectorforJava User’s Guide and Reference Note! Before using this information and the product it supports, be sure to read the general information under Notices. Edition notice This edition applies to Version 3.5 of IBM VisualAge for Java and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 1998, 2000. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. Understanding IMS Connector for Java ...........1 Prerequisites for using IMS Connector for Java .............3 IMS Connector for Java concepts and terms ..............4 Chapter 2. Preparing to use IMS Connector for Java ..........17 Preparing your VisualAge for Java Environment .............17 Preparing your WebSphere Studio Environment .............21 Preparing your WebSphere Application Server Environment ........22 Chapter 3. Building Java applications and servlets ..........31 Building Java Applications and Servlets for Conversational Transactions ....32 Chapter 4. Building a Java Application to Run an IMS Transaction ....35 Chapter 5. Building a Java Application to Run a Navigator .......53 Chapter 6. Building a Java Application for an IMS Transaction with Multi-Segment Output Messages.................69 Chapter 7. Building a Java Application for an IMS Transaction with Multi-Segment Input Messages .................75 Chapter 8. Building an Application to Run an IMS Transaction with Synchronization Level Confirm .................81 Chapter 9. Building the Graphical User Interface ...........87 Chapter 10. Building a Java Servlet to Run an IMS Transaction .....95 Chapter 11. Building a Web Application that Uses One Servlet to Run an IMS Conversation ......................107 Chapter 12.
    [Show full text]
  • Eclipse Project Briefing Materials
    [________________________] Eclipse project briefing materials. Copyright (c) 2002, 2003 IBM Corporation and others. All rights reserved. This content is made available to you by Eclipse.org under the terms and conditions of the Common Public License Version 1.0 ("CPL"), a copy of which is available at http://www.eclipse.org/legal/cpl-v10.html The most up-to-date briefing materials on the Eclipse project are found on the eclipse.org website at http://eclipse.org/eclipse/ 200303331 1 EclipseEclipse ProjectProject 200303331 3 Eclipse Project Aims ■ Provide open platform for application development tools – Run on a wide range of operating systems – GUI and non-GUI ■ Language-neutral – Permit unrestricted content types – HTML, Java, C, JSP, EJB, XML, GIF, … ■ Facilitate seamless tool integration – At UI and deeper – Add new tools to existing installed products ■ Attract community of tool developers – Including independent software vendors (ISVs) – Capitalize on popularity of Java for writing tools 200303331 4 Eclipse Overview Another Eclipse Platform Tool Java Workbench Help Development Tools JFace (JDT) SWT Team Your Tool Plug-in Workspace Development Debug Environment (PDE) Their Platform Runtime Tool Eclipse Project 200303331 5 Eclipse Origins ■ Eclipse created by OTI and IBM teams responsible for IDE products – IBM VisualAge/Smalltalk (Smalltalk IDE) – IBM VisualAge/Java (Java IDE) – IBM VisualAge/Micro Edition (Java IDE) ■ Initially staffed with 40 full-time developers ■ Geographically dispersed development teams – OTI Ottawa, OTI Minneapolis,
    [Show full text]
  • Eclipse (Software) 1 Eclipse (Software)
    Eclipse (software) 1 Eclipse (software) Eclipse Screenshot of Eclipse 3.6 Developer(s) Free and open source software community Stable release 3.6.2 Helios / 25 February 2011 Preview release 3.7M6 / 10 March 2011 Development status Active Written in Java Operating system Cross-platform: Linux, Mac OS X, Solaris, Windows Platform Java SE, Standard Widget Toolkit Available in Multilingual Type Software development License Eclipse Public License Website [1] Eclipse is a multi-language software development environment comprising an integrated development environment (IDE) and an extensible plug-in system. It is written mostly in Java and can be used to develop applications in Java and, by means of various plug-ins, other programming languages including Ada, C, C++, COBOL, Perl, PHP, Python, Ruby (including Ruby on Rails framework), Scala, Clojure, and Scheme. The IDE is often called Eclipse ADT for Ada, Eclipse CDT for C/C++, Eclipse JDT for Java, and Eclipse PDT for PHP. The initial codebase originated from VisualAge.[2] In its default form it is meant for Java developers, consisting of the Java Development Tools (JDT). Users can extend its abilities by installing plug-ins written for the Eclipse software framework, such as development toolkits for other programming languages, and can write and contribute their own plug-in modules. Released under the terms of the Eclipse Public License, Eclipse is free and open source software. It was one of the first IDEs to run under GNU Classpath and it runs without issues under IcedTea. Eclipse (software) 2 Architecture Eclipse employs plug-ins in order to provide all of its functionality on top of (and including) the runtime system, in contrast to some other applications where functionality is typically hard coded.
    [Show full text]
  • Visualage Generator: User's Guide
    VisualAge Generator User’s Guide Ve r s i o n 4 .5 SH23-0268-01 Note Before using this document, read the general information under “Notices” on page xi. Third Edition (April 2001) This edition applies to the following licensed programs: v IBM VisualAge Generator Developer for OS/2 and Windows NT Version 4.5 v IBM VisualAge Generator Server for OS/2, AIX, Windows NT, HP-UX, and Solaris Version 4.5 v IBM VisualAge Generator Server for AS/400 Version 4 Release 4 v IBM VisualAge Generator Server for MVS, VSE, and VM Version 1.2 Order publications by phone or fax. IBM Software Manufacturing Solutions takes publication orders between 8:30 a.m. and 7:00 p.m. eastern standard time (EST). The phone number is (800) 879-2755. The fax number is (800) 445-9269. Faxes should be sent Attn: Publications, 3rd floor. You can also order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address below. IBM welcomes your comments. You can send your comments in any one of the following methods: Electronically, using the online reader comment form at the address listed below. Be sure to include your entire network address if you wish a reply. v http://www.ibm.com/software/ad/visgen By mail to the following address: IBM Corporation, Attn: Information Development, Department G7IA Building 503, P.O. Box 12195, Research Triangle Park, NC 27709-2195. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
    [Show full text]
  • Visualage Pacbase: CODASYL DATABASE DESCRIPTION
    VisualAge Pacbase CODASYL DATABASE DESCRIPTION Ve r s i o n 3.5 VisualAge Pacbase CODASYL DATABASE DESCRIPTION Ve r s i o n 3.5 Note Before using this document, read the general information under “Notices” on page v. You may consult or download the complete up-to-date collection of the VisualAge Pacbase documentation from the VisualAge Pacbase Support Center at: http://www.ibm.com/support/docview.wss?rs=37&uid=swg27005477 Consult the Catalog section in the Documentation home page to make sure you have the most recent edition of this document. First Edition (September 2007) This edition applies to the following licensed programs: v VisualAge Pacbase Version 3.5 Comments on publications (including document reference number) should be sent electronically through the Support Center Web site at: http://www.ibm.com/software/awdtools/vapacbase/support.html or to the following postal address: IBM Paris Laboratory 1, place Jean–Baptiste Clément 93881 Noisy-le-Grand, France. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1983,2007. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . .v DM4 Schema (DDL)/type M4: Screens . .84 DM4 Schema (DDL) / M4 Type: Generated Trademarks . vii Description . .90 DM4 Schema (DMCL) / M2 Type: Screens . .92 Chapter 1. Introduction . .1 DM4 Schema (DMCL) / M2 Type: Generated VisualAge Pacbase Module . .1 Description . .98 Introduction to the Database Description DM4 Sub-schema / M3 Type: Screens .
    [Show full text]
  • Visualage for Java, Enterprise Edition
    Installation and migration guide This Installation and Migration guide contains the following information: ● Hardware and software prerequisites for VisualAge(R) for Java(TM), Professional and Enterprise Editions ● How to install VisualAge for Java, Professional and Enterprise Editions ● Prerequisites and supported platforms for the team repository server (EMSRV) ● How to install the team repository server (EMSRV) ● How to prepare for the team development environment ● Limitations and known problems with installation ● How to migrate from a previous version of VisualAge for Java (both general and component-specific information) A PDF version of this guide is also available in the pdf directory on the product CD. Where to find more information about VisualAge for Java This file does not include detailed information about the specific components and features of VisualAge for Java, Enterprise Edition. For that information, you should refer to the product Release Notes which you can access by selecting Start > Programs > VisualAge for Java > Release Notes. For all languages other than English, the release notes can be found on the Web at http://www.ibm.com/vadd. This file does not contain information about using VisualAge for Java. Refer to the Getting Started guide and to the online help for that information. Some of the online help has been grouped into PDF documents which you can view and print using Adobe Acrobat Reader (available from http://www.adobe.com/). Not all PDFs are available in all languages. The PDF files are available from the "pdf' directory. This can be found on the product CD or your temporary directory (where you extracted your parts to) if you have an electronic version of VisualAge for Java.
    [Show full text]
  • Parte-4 TC [Modo De Compatibilidade]
    Curso: Análise e Desenvolvimento de Sistemas Disciplina Algoritmos e Programação (Características fundamentais de Codificação de programas) Prof. Wagner Santos C. de Jesus [email protected] Histórico sobre (Java) A linguagem Java se tornou oficial a todo o mundo em 1995, depois que a Netscape a licenciou para o uso do navegador Navigator. Atualmente existem outras opções para a Web mais quando a linguagem Java foi criada ela revolucionou a natureza de páginas na web. Os (Applets) Java. Essa linguagem e um produto criado pela empresa norte americana Sun Microsystem. 2 Direitos da empresa Oracle Larry Ellison, diretor-executivo da Oracle , no evento Oracle Open World, em setembro de 2008 (Anunciou a compra da Sun Microsystems). 3 http://g1.globo.com/Noticias/Tecnologia/0,,MUL1091457-6174,00-ORACLE+ANUNCIA+COMPRA+DA+SUN+POR+MAIS+DE+US+BILHOES.html Principais Características da Linguagem Java • Multiplataforma; • Recursos de Rede - Possui extensa biblioteca de rotinas que facilitam a cooperação com protocolos TCP/IP, como HTTP e FTP ; • Sintaxe similar a Linguagem C/C++ e principalmente, a C#. • É distribuída com um vasto conjunto de (APIs); • Desalocação de memória automática por processo de coletor de lixo (garbage collector ); 4 As ferramentas de programação Rad (Desenvolvimento Rápido de Aplicações) para Java. • JDK, JSDK (Sun) FreeWare (*) • Jbuilder empresa (Borland) • Forte empresa (Sun) FreeWare • Eclipse • Geany • EditPlus • NetBeans • VisualAge for Java (IBM) 5 Introdução a Programação em Java 6 Um programa Java atinge essa independência através de um recurso denominado como Máquina Virtual Java(JVM). Exemplo : Um programa tradicional Compilado.(Delphi) Seu Código(Delphi) Compilador Windows Arquivo Binário Windows ---------- Compilador ------ Mact.
    [Show full text]
  • Portable Document Format (PDF)
    Kristopher Johnson E-mail: [email protected] Web Site: http://undefinedvalue.com/ Summary Over 28 years of experience developing distributed systems and user applications for the transportation engineering, lottery/gaming, and enterprise mobile software testing industries, including service as lead developer for multiple projects. Experienced with iOS and Android development, Microsoft Windows, macOS and UNIX software development in C#, Objective-C, Swift, C++, Java, JavaScript and other programming languages, with relational database technology, embedded systems, and distributed systems. Skills Operating Systems iOS, Android, Windows, macOS, Linux, Solaris/SunOS, AT&T System V UNIX, QNX Neutrino, VxWorks, OpenVMS, OS/2 Programming Languages C#, C++, C, Objective-C, Swift, Java, JavaScript, TypeScript, Python, Perl, Ruby, Visual Basic, Forth, Bash Development Tools Microsoft Visual Studio, Apple Xcode, Android Studio, Eclipse, Java SDK, GNU compilers and toolchains, Borland C++ Builder, IBM VisualAge C++ Distributed Systems REST services, web services, CORBA, DCOM, RPC, Technologies .NET Remoting, sockets, TCP/IP Component Technologies .NET, Java EE, ActiveX/OLE/COM, Dynamic Link Libraries and Shared Objects Database Systems PostgreSQL, Oracle, SQL Server, SQLite, MySQL, InfluxDB, Microsoft Access/Jet, Paradox Experience Feb 2015-Present Involved in design, development, maintenance, and Senior Software Developer support of a suite of enterprise mobile application Kobiton, Inc. testing products for iOS and Android. Using macOS, Atlanta, GA iOS, Swift, Objective-C, Xcode, Windows, Visual Studio .NET, Android Studio, C#, C++, Java, (Formerly Mobile Labs LLC, JavaScript, TypeScript, .NET, Mono, CMake, HTML, before its acquisition by CSS, PostgreSQL, and InfluxDB. Kobiton in October 2020) Development tasks include reverse-engineering of undocumented protocols, file formats, and operating system libraries, and maintaining compatibility with older versions of iOS and Android.
    [Show full text]
  • Bachelor's Final Work
    MINISTRY FOR DEVELOPMENT OF INFORMATION TECHNOLOGIES AND COMMUNICATIONS OF THE REPUBLIC OF UZBEKISTAN TASHKENT UNIVERSITY OF INFORMATION TECHNOLOGIES «Allowed to Defense» Head of the Department Abdurahmanova Yu.M. ____________ «____» ____________ 2015 y. BACHELOR'S FINAL WORK Theme: "Creating Android Application of "Higher Education Institutions of Uzbekistan"" Graduate __________ M.N.Muhiddinov Supervisor __________ Yo.Q.Aliqulov Reviewer __________ R.M.Irmuhamedova SVA and E consultant __________ S.M.Abdullayeva Tashkent – 2015 6 MINISTRY FOR DEVELOPMENT OF INFORMATION TECHNOLOGIES AND COMMUNICATIONS OF THE REPUBLIC OF UZBEKISTAN TASHKENT UNIVERSITY OF INFORMATION TECHNOLOGIES Faculty: Software Engineering Department: Algorithmic and mathematical modeling Direction: 5330200 – “Informatics and Information Technologies A P P R O V E D Head of the Department Abdurahmanova Yu.M. ____________________ «___ » ___________ 2015 y. Muhiddinov Muhriddin Nuriddin o'g'li BACHELOR'S FINAL WORK T A S K 1. The theme of the work: “Creating Android application of Higher Education Institutions of Uzbekistan”. 2. The theme approved by order of the University on «22» January 2015 y. № 80-16 3. Completion of the finished work: ___.___.20___y 7 4. Source data to work: Android OS, Intellij IDEA 13.0.2 platform, Genymotion Emulator, Java programming language, SQLite database. 5. Contents of the settlement explanatory note (list of questions to be development): Actuality of the topic, goals of the final work and identifying necessary questions and problems for implementation, analyzing “Higher Education Institutions of Uzbekistan” and similar Android applications, designing Android application of “Higher Education Institutions of Uzbekistan” and SQLite database, Creating Android application of “Higher Education Institutions of Uzbekistan”.
    [Show full text]
  • Building AS/400 Client/Server Applications with Java
    Building AS/400 Client/Server Applications with Java Bob Maatta, Dan Murphy International Technical Support Organization http://www.redbooks.ibm.com SG24-2152-02 International Technical Support Organization SG24-2152-02 Building AS/400 Client/Server Applications with Java July 1999 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix D, “Special Notices” on page 413. Third Edition (July 1999) This edition applies to OS/400 Version 3, Release Number 2 and later. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JLU Building 107-2 3605 Highway 52N Rochester, Minnesota 55901-7829 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1997, 1998, 1999. All rights reserved Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Contents ..................................................... iii Figures ......................................................ix Tables ......................................................xvii Preface ..................................................... xix The Team That Wrote This Redbook . ..................................xix CommentsWelcome..............................................
    [Show full text]
  • IBM Visualage for Java, Professional and Enterprise Editions Version 4.0, Assists Developers in the Creation of Java-Based E-Business Applications
    Software Announcement June 26, 2001 IBM VisualAge for Java, Professional and Enterprise Editions Version 4.0, Assists Developers in the Creation of Java-based e-business Applications Overview • Deploy EJBs at the 1.1 specification level to WebSphere At a Glance VisualAge for Java is a Version 4.0 (code to EJB 1.0 + comprehensive Java development extensions) Both editions comprise a cross-platform, object-oriented, tool that helps developers quickly: • Team management Java language application • Deliver their first e-business • ET/400 and ET/390 toolkits development tool for extending application current information technology assets to the Web and support: • Grow their e-business Key Prerequisites applications by using features • Incremental rapid Java • such as team capabilities, Windows 98, Windows NT application development Enterprise JavaBeans (EJB) Version 4.0 (with Service Pack 4, creation wizards, and testing on or later), or Windows 2000 • Powerful and robust server-side the WebSphere Test Java programming environment • TCP/IP communications protocol Environment inside the configured and running • WebSphere Test Environment integrated development environment (IDE) • A frames-capable browser • Tool Integrator API • Differentiate their business by • Planned Availability Dates Enhanced links to VisualAge connecting to legacy applications TeamConnection , Merant and data • Program package: July 27, 2001 PVCS, Microsoft SourceSafe, and Rational ClearCase VisualAge for Java, Professional • Electronic distribution: products Edition
    [Show full text]
  • Integration Kit for BEA Weblogic IBM Visualage for Java
    BEA WebLogic Integration Kit for IBM VisualAge for Java User Guide BEA WebLogic Integration Kit for IBM VisualAge for Java, Version 3.5 Document Edition 1.1 February 2001 Copyright Copyright © 2001 BEA Systems, Inc. All Rights Reserved. Restricted Rights Legend This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems License Agreement and may be used or copied only in accordance with the terms of that agreement. It is against the law to copy the software except as specifically allowed in the agreement. This document may not, in whole or in part, be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine readable form without prior consent, in writing, from BEA Systems, Inc. Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the BEA Systems License Agreement and in subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause at FAR 52.227-19; subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, subparagraph (d) of the Commercial Computer Software--Licensing clause at NASA FAR supplement 16-52.227-86; or their equivalent. Information in this document is subject to change without notice and does not represent a commitment on the part of BEA Systems. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA Systems DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE OR WRITTEN MATERIAL IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE.
    [Show full text]