DOCSLIB.ORG

Using Eclipse Ganymede to Develop for the Desktop, Web and Mobile

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Using Eclipse Ganymede to Develop for the Desktop, Web and Mobile Using Eclipse Ganymede to develop for the desktop, Web and mobile devices, Part 2: Developing for the Rich Client Platform, the Ganymede way RAP: The new way to the Web Skill Level: Intermediate Suresh Krishna ([email protected]) Software Developer Freelance Developer Trebor Fenstermaker ([email protected]) Software Consultant Sunnyside Avenue Software, LLC 09 Sep 2008 The Ganymede release of the Eclipse IDE includes 24 separate projects, covering a wide range of technologies. Many of these projects are mature, and this release provides incremental improvements to those. But Ganymede also includes a number of new projects that introduce new technologies to the Eclipse platform. In this three-part "Using Eclipse Ganymede to develop for the desktop, Web and mobile devices" tutorial series, we will cover the following new Ganymede features: RCP, RAP, and eRCP, which allow you to develop software for the desktop, Web, and mobile platforms, respectively, with one common code base; Subversion for version control; and p2 for update and installation. Here in Part 2, we will take the personal organizer developed in Part 1 and modify it to use the new Rich Ajax Platform (RAP) to package and distribute the application on the Web. Section 1. Before you start Developing for the Rich Client Platform, the Ganymede way © Copyright IBM Corporation 1994, 2008. All rights reserved. Page 1 of 57 developerWorks® ibm.com/developerWorks This tutorial is for any Eclipse developer who wants to learn how to take code written using the mature Rich Client Platform (RCP) and modify it to use the new Rich Ajax Platform (RAP) to allow for a rich-client experience distributed over the Web. You should have an understanding of the Eclipse platform and some familiarity with the idea of Rich Internet Applications (RIAs). Also, you should have knowledge of how to configure a servlet container and deploy applications on it. About this series Part 1 provides an introduction to the new features of the RCP, the new Subversion Eclipse integration, and the p2 packaging and distribution system. Part 2 introduces the Rich Ajax Platform (RAP) to write applications for the Web. And Part 3 discusses how to use the embedded Rich Client Platform (eRCP) to develop an application for a mobile device. About this tutorial The Ganymede release of the Eclipse IDE bundles more than 20 new and existing projects under the Eclipse umbrella. In Part 1 of this three-part series, you looked at some features added to make development easier, including support for Subversion and a new distribution model for plug-ins called p2. You also saw some incremental improvements in the mature Rich Client Platform (RCP) by developing a simple personal task organizer plug-in application, then storing it in Subversion and deploying it via p2. Another exciting addition to Ganymede is the inclusion of the Rich Application Platform (RAP). RAP is a way to build rich client applications — stateful GUI applications similar to those developed for a desktop — and deploy them for use on the Web. RAP brings the Eclipse programming model to the Web, allowing you to reuse much of your existing RCP code when building RAP-based applications. This is done using Ajax, but Eclipse makes it simple to build on the knowledge you already have of developing desktop applications with the RCP. To demonstrate, you will modify the personal organizer developed in Part 1 to use RAP. Topics include: • How to download and install the RAP environment to Eclipse • How to migrate your existing RCP code to RAP • How to factor your code for the Web • How to package and deploy your code to a Web server Developing for the Rich Client Platform, the Ganymede way Page 2 of 57 © Copyright IBM Corporation 1994, 2008. All rights reserved. ibm.com/developerWorks developerWorks® System requirements Eclipse Ganymede Find Eclipse Ganymede at the Eclipse Foundation. Java 2 Standard Edition The Java™ 2 Standard Edition V5 or greater is available from Sun Microsystems. Eclipse RAP The Eclipse RAP plug-in is available in the Eclipse Foundation RAP section at Eclipse.org. Apache Tomcat For deploying the finished RAP application to a stand-alone servlet container, this tutorial uses Apache Tomcat. Download the latest stable version. Section 2. Getting started with RAP Before you can start developing with RAP, you need to download it from the Eclipse Web site and set up your target platform to use it. Developing with RAP RAP allows you to build Ajax-enabled Web applications using the Eclipse development model. If you're already familiar with developing desktop applications with the Eclipse RCP, you have the expertise to develop with RAP. In fact, much of the code written for an RCP application can be reused for RAP. This means you can use the full power of Java technology and the Eclipse APIs to develop Web-based applications. Your users can then experience a full GUI application with no page refreshes, like a typical Web application, but they can do so without having to download and install your application on their desktop. RAP achieves this by providing a special implementation of the Standard Widget Toolkit (SWT), JFace, and Workbench, and, as such, is actually a subset of RCP. Because the base architecture of the RCP and RAP are similar (see Figure 1), plug-in reuse is possible with minimal changes in the source code. RAP applications are accessed via standard browsers in the same way RCP applications are executed on the desktop environment. This is achieved by the RAP Widget Toolkit (RWT), a replacement for SWT used in RCP. Developing for the Rich Client Platform, the Ganymede way © Copyright IBM Corporation 1994, 2008. All rights reserved. Page 3 of 57 developerWorks® ibm.com/developerWorks Browser-side widget rendering is done with the qooxdoo Ajax library (see Resources). qooxdoo is a comprehensive Ajax framework leveraging the object-oriented JavaScript that enables users to build cross-browser applications. RAP abstracts the details about the JavaScript, allowing you to work with the Java APIs to build the Rich Internet Applications (RIAs). Custom widget developers need to have JavaScript, qooxdoo, and RAP knowledge. Client-side development allows for the embedding of client-side technologies like other JavaScript frameworks, Flash, and applets. Figure 1. Comparing RAP and RCP architectures Downloading RAP Because RAP is an RCP subset, it cannot co-exist in the same Eclipse instance as RCP; you must download and install the RAP environment for Eclipse separately. Point your browser to www.eclipse.org/rap/downloads (see Figure 2). Note: If you would like to migrate the RCP source code to RAP, a target platform download for RAP is recommended. This enables the existing RCP code to get compiled and run against the target RAP code. If you intend to develop new Web applications using RAP and would like to have the development platform, it's recommended to get the RAP SDK from the p2 update mechanism, covered in Part 1. Figure 2. The Eclipse RAP home page Developing for the Rich Client Platform, the Ganymede way Page 4 of 57 © Copyright IBM Corporation 1994, 2008. All rights reserved. ibm.com/developerWorks developerWorks® Select the V1.1rRelease with the words "target platform" in the filename and choose an appropriate mirror. Figure 3. The Eclipse RAP download page Download the ZIP file to a temporary directory on your local hard drive, one that is accessible to your Eclipse installation. Once transferred, unzip it in that temp Developing for the Rich Client Platform, the Ganymede way © Copyright IBM Corporation 1994, 2008. All rights reserved. Page 5 of 57 developerWorks® ibm.com/developerWorks directory. Open your instance of Eclipse Ganymede and ensure that your workspace points to where you've stored the personal-organizer project from Part 1, then open your Eclipse desktop to the plug-in development perspective. Open the Preferences panel for Eclipse. How you do this depends on your operating system — for example, on Windows®, it's Window > Preferences (see Figure 4); on Mac OS X, it's Eclipse > Preferences). Navigate to Plug-in Development > Target Platform. Figure 4. Specifying the target platform Change the value of the location box to the directory where you unzipped the download and click Reload. Figure 5. Making the target platform RAP Developing for the Rich Client Platform, the Ganymede way Page 6 of 57 © Copyright IBM Corporation 1994, 2008. All rights reserved. ibm.com/developerWorks developerWorks® This will load the plug-ins associated with the RAP and switch your target platform from the RCP. You're ready to start making the changes to the personal organizer to take advantage of RAP, which you'll do in the next section. Section 3. Moving from RCP to RAP Follow along to see how to migrate the personal-organizer example from RCP to RAP. And along the way, get a feel for some of the differences between the two environments. Follow the errors to spot the differences You may notice that since you've switched target platforms, Eclipse is complaining Developing for the Rich Client Platform, the Ganymede way © Copyright IBM Corporation 1994, 2008. All rights reserved. Page 7 of 57 developerWorks® ibm.com/developerWorks there are errors in your personal task-organizer code. Figure 6. Compiler errors for the personal organizer after switching to RAP One reason for this is because your existing project was meant to use RCP, but by switching targets, the plug-ins used to resolve some of the elements used in the personal organizer are now missing from your build path. Some of these have equivalents in RAP, but some do not. So you will have to do a few small modifications to get things to compile.
Load more

Recommended publications
  • Red Hat Fuse 7.5 Apache Karaf Transaction Guide
    Red Hat Fuse 7.5 Apache Karaf Transaction Guide Writing transactional applications for the Apache Karaf container Last Updated: 2020-02-21 Red Hat Fuse 7.5 Apache Karaf Transaction Guide Writing transactional applications for the Apache Karaf container Legal Notice Copyright © 2020 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Customizing Eclipse RCP Applications Techniques to Use with SWT and Jface
    Customizing Eclipse RCP applications Techniques to use with SWT and JFace Skill Level: Intermediate Scott Delap ([email protected]) Desktop/Enterprise Java Consultant Annas Andy Maleh ([email protected]) Consultant 27 Feb 2007 Most developers think that an Eclipse Rich Client Platform (RCP) application must look similar in nature to the Eclipse integrated development environment (IDE). This isn't the case, however. This tutorial will explain a number of simple techniques you can use with the Standard Widget Toolkit (SWT) and JFace to create applications that have much more personality than the Eclipse IDE. Section 1. Before you start About this tutorial This tutorial will explain a number of UI elements that can be changed in Eclipse RCP, JFace, and SWT. Along the way, you will learn about basic changes you can make, such as fonts and colors. You will also learn advanced techniques, including how to create custom wizards and section headers. Using these in conjunction should provide you the ability to go from a typical-looking Eclipse RCP application to a distinctive but visually appealing one. Prerequisites Customizing Eclipse RCP applications © Copyright IBM Corporation 1994, 2008. All rights reserved. Page 1 of 40 developerWorks® ibm.com/developerWorks You should have a basic familiarity with SWT, JFace, and Eclipse RCP. System requirements To run the examples, you need a computer capable of adequately running Eclipse V3.2 and 50 MB of free disk space. Section 2. Heavyweight and lightweight widgets Before diving into techniques that can be used to modify SWT, JFace, and Eclipse RCP in general, it's important to cover the fundamental characteristics of SWT and how they apply to the appearance of the widget set.
    [Show full text]
  • Recoder with Eclipse
    School of Mathematics and Systems Engineering Reports from MSI - Rapporter från MSI Recoder with Eclipse Saúl Díaz González Álvaro Pariente Alonso June MSI Report 09031 2009 Växjö University ISSN 1650-2647 SE-351 95 VÄXJÖ ISRN VXU/MSI/DA/E/--09031/--SE Abstract RECODER is a Java framework aimed at source code analysis and metaprogramming. It works on several layers to offer a set of semi-automatic transformations and tools, ranging from a source code parser and unparser, offering a highly detailed syntactical model, analysis tools which are able to infer types of expressions, evaluate compile-time constants and keep cross-reference information, to transformations of the very Java sources, containing a library of common transformations and incremental analysis capabilities. These make up an useful set of tools which can be extended to provide the basis for more advanced refactoring and metacompiler applications, in very different fields, from code beautification and simple preprocessors, stepping to software visualization and design problem detection tools to adaptive programming environments and invasive software composition. The core system development of RECODER started in the academic field and as such, it was confined into a small platform of users. Although a powerful tool, RECODER framework lacks usability and requires extensive and careful configuration to work properly. In order to overcome such limitations, we have taken advantage of the Eclipse Integrated Development Environment (Eclipse IDE) developed by IBM, specifically its Plugin Framework Architecture to build a tool and a vehicle where to integrate RECODER functionalities into a wide-used, well-known platform to provide a semi- automated and user-friendly interface.
    [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]
  • Virgo White Paper Introduction the Eclipse Virgo Project Provides a Modular Java Server Runtime and Is Part of the Eclipse Runtime (Eclipsert) Umbrella Project
    Eclipse Virgo A Technical Overview White Paper Version 1.2 June 2012 Table of Contents Introduction.......................................................................................................................................... 3 OSGi Introduction................................................................................................................................ 3 History.................................................................................................................................................. 4 Virgo Feature Summary........................................................................................................................4 Benefits.................................................................................................................................................5 Why Choose Virgo?..............................................................................................................................9 Success Stories................................................................................................................................... 10 A Warning........................................................................................................................................... 11 Technology......................................................................................................................................... 11 Virgo Runtime Deliverables..............................................................................................................
    [Show full text]
  • Netbeans RCP by John Kostaras Open Conference Crete 2012 Agenda
    NetBeans RCP By John Kostaras Open Conference Crete 2012 Agenda ∗ Introduction ∗ Module System ∗ Lookups ∗ Window System ∗ Explorer Views ∗ Nodes ∗ Action System ∗ Dialogs and Wizards ∗ Options & Settings ∗ FileSystem & DataSystem ∗ Visual Library ∗ Internationalisation ∗ Help System ∗ Hands on 15/9/2012 NetBeans RCP - John Kostaras - JavaCrete 2012 2 Prerequisites ∗ NetBeans 7.2 ( http://www.netbeans.org ) ∗ Todo app (http://netbeans.org/community/magazine/code/nb- completeapp.zip ) 15/9/2012 NetBeans RCP - John Kostaras - JavaCrete 2012 3 Introduction NetBeans RCP -John Kostaras -JavaCrete 2012 4 15/9/2012 What is NetBeans Rich Client Platform? ∗ Set of APIs and Libraries ∗ Framework and Module system ∗ Generic Desktop Application ∗ Platform modules + IDE Modules = NetBeans IDE ∗ Platform modules + your modules = Your Application ∗ Provides services that almost all Desktop Applications need ∗ Saves development time ∗ Allows you to concentrate on the actual business logic ∗ NetBeans RCP Application server for the desktop ∗ Improves development and maintainability through modularization 15/9/2012 NetBeans RCP - John Kostaras - JavaCrete 2012 5 Benefits ∗ Shorter development time ∗ Consistent User Interface ∗ Updateable (Update center / Webstart) ∗ Platform Independence (Swing + platform specific launchers) ∗ Modularity 15/9/2012 NetBeans RCP - John Kostaras - JavaCrete 2012 6 Hands-on NetBeans RCP - John Kostaras - JavaCrete 2012 7 15/9/2012 TodoRCP ∗ A todo list application: "A complete App using NetBeans 5" by Fernando Lozano http://netbeans.org/download/magazine/01/nb01_completeap
    [Show full text]
  • Introduction Background Scope
    Copyright Oracle Corporation and VMware Inc, 2010 Enterprise Modules Project (Gemini) Proposal The Enterprise Modules Project is a proposed open source project under the Eclipse Runtime Project. This project is in the Project Proposal Phase (as defined in the Eclipse Development Process). Introduction The intent of the "Enterprise Modules" project, nicknamed Gemini, is to provide a home for subprojects that integrate existing Java enterprise technologies into module-based platforms, and/or that implement enterprise specifications on module-based platforms. Gemini will be a parent ("container project" as defined by the Eclipse Development Process) for several subprojects ("operating projects" as defined by the Eclipse Development Process) that provide the specific implementations/integrations. Gemini will itself be a subproject of the Eclipse Runtime Project and will strive to leverage functionality of existing projects. We encourage and request additional participation and input from any and all interested parties in the Eclipse community. Background Enterprise applications are often complex, involving multiple layers and many actors. Even though every application has a different purpose and usage, there are a number of features and behavioral requirements in the underlying infrastructure that are common among many of those seemingly dissimilar applications. For a long time, not only did developers need to create the vertical business logic of the application, but they also had to create the platform plumbing on which the application could run. Enterprise Java standards made great strides in defining specifications describing how these layers could be implemented, exported and used. They have since become the assumed and ubiquitous underpinnings of the majority of enterprise Java systems.
    [Show full text]
  • An Empirical Evaluation of Osgi Dependencies Best Practices in the Eclipse IDE Lina Ochoa, Thomas Degueule, Jurgen Vinju
    An Empirical Evaluation of OSGi Dependencies Best Practices in the Eclipse IDE Lina Ochoa, Thomas Degueule, Jurgen Vinju To cite this version: Lina Ochoa, Thomas Degueule, Jurgen Vinju. An Empirical Evaluation of OSGi Dependencies Best Practices in the Eclipse IDE. 15th International Conference on Mining Software Repositories, May 2018, Gothenburg, Sweden. 10.1145/3196398.3196416. hal-01740131 HAL Id: hal-01740131 https://hal.archives-ouvertes.fr/hal-01740131 Submitted on 27 Mar 2018 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. An Empirical Evaluation of OSGi Dependencies Best Practices in the Eclipse IDE Lina Ochoa Thomas Degueule Jurgen Vinju Centrum Wiskunde & Informatica Centrum Wiskunde & Informatica Centrum Wiskunde & Informatica Amsterdam, Netherlands Amsterdam, Netherlands Amsterdam, Netherlands [email protected] [email protected] Eindhoven University of Technology Eindhoven, Netherlands [email protected] ABSTRACT that can be implemented and tested independently. This also fos- OSGi is a module system and service framework that aims to fill ters reuse by allowing software components to be reused from one Java’s lack of support for modular development. Using OSGi, devel- system to the other, or even to be substituted by one another pro- opers divide software into multiple bundles that declare constrained vided that they satisfy the appropriate interface expected by a client.
    [Show full text]
  • 154 Core Jetty
    #154 CONTENTS INCLUDE: n Jetty Architecture n Configuring Jetty n Basic Usage Jetty n Advanced Usage n Using with Web Frameworks A Lightweight, Open-Source Web Server and Servlet Container n Running Standalone By Jos Dirksen n Integration with Maven and more... Visit refcardz.com SelectChannelConnector Uses NIO buffers with a non-blocking threading ABOUT JETTY model. Threads are only allocated to connec- tions with requests. Use when there are many connections that have idle periods. Jetty, an open-source web server hosted by the Eclipse foundation, is a full-fledged HTTP server and Servlet container that can be easily SslSocketConnector SSL version of the SocketConnector configured to serve static and dynamic content. You can very easily SslSelectChannelConnector SSL version of the SelectChannelConnector embed Jetty into your own applications using Java or XML-based AJPConnector Use for connections from Apache modules: configuration or run Jetty directly from Maven. Additionally, you can use mod_proxy_ajp and mod_jk. Jetty in many different high-demand areas such as Yahoo Hadoop Cluster, HTTPSPDYServerConnector Supports the SPDY protocol and performs SPDY Google AppEngine, and Yahoo! Zimbra. to HTTP conversion. If SPDY is not negotiated, This RefCard refers primarily to Jetty 8; however, most of the configuration falls back to HTTPS. Get More Refcardz! Refcardz! Get More discussed will work on Jetty 7. Handler JETTY ARCHITECTURE The handler is the component that deals with requests received by a connector. There are three types of handlers in Jetty. It’s important to understand the architecture behind Jetty. The main • Coordinating handlers route requests to other handlers. architecture of Jetty consists out of the following four components.
    [Show full text]
  • Scaling JPA Applications with Toplink Grid
    <Insert Picture Here> @ TopLink Grid: Scaling JPA Applications with Coherence Shaun Smith, Principal Product Manager Oracle Server Technologies, TopLink Copyright © 2010 Oracle Java Persistence: The Problem Space Customer <customer id=“…”> <name>…</name> id: int JAXB/SDO … name: String </contact-info> creditRating: int </customer> Java XML JPA CUST ID NAME C_RATING JPA: Java Persistence API Relational JAXB: Java Architecture for XML Binding SDO: Service Data Objects EclipseLink Project • Provides JPA, JAXB, SDO, DBWS, and EIS persistence services • Open source Eclipse project • Project Lead by Oracle • Founded by Oracle with the contribution of full TopLink source code and tests • Based upon product with 12+ years of commercial usage EclipseLink JPA • JPA 1.0 compliant with advanced persistence • JPA 2.0 Reference Implementation (JSR 317) • Supports Java EE, Java SE, Web, Spring, and OSGi • Supports all leading RDMS with platform specific features • Best JPA for the Oracle Database—supporting advanced features • Extensible and pluggable • Key infrastructure: • Caching, Locking, Query Framework, Mapping, … • … plus many valuable advanced features Oracle TopLink 11gR1 • Oracle’s Enterprise Java Persistence Framework • Includes open source EclipseLink with Commercial Support • Certified on WebLogic and redistributed by Oracle as part of TopLink product • TopLink Grid: JPA integration with Coherence • Included in WebLogic Server • Tooling Support in JDeveloper and Eclipse Example JPA Client Code … Mechanics of a JPA Application Step 1 Step 2 Step 3 Application Logic Application Logic Application Logic Create/ Modify Entities JPA JPA JPA Read Insert/ Entities Update Entities JPA with Cache TX n TX n+1 Application Logic Application Logic Cache hits JPA avoid object build cost ReadTX Commit Entities Scaling Java Persistence Java Scaling Application Application JPA Application Application Application Application Application JPA Application Application Application .
    [Show full text]
  • Flexibility at the Roots of Eclipse
    6°ÊÈ >ʽäÇ Dynamic Wizard Modeling with GMF Introduction to the Using GMF to Build a Dynamic Wizard Generic Eclipse Framework and a Graphical Editor Modeling System Developing a Deploying the BIRT Graphical Modeling Viewer to JBoss Tool for Eclipse Disseminate Report Content to an Application Server Subversive The Eclipse Enabling Plug-In for Integration and Subversion Interoperability for Eclipse based Development An Introduction to the Corona Project Flexibility at the Roots of Eclipse Solving the GUI Dilemma: SWTSwing and Eclipse on Swing 6°ÊÈ >ʽäÇ Vol.6 January 2007 Dynamic Wizard Modeling with GMF Introduction to the Using GMF to Build a Dynamic Wizard Generic Eclipse Table of Contents Framework and a Graphical Editor Modeling System Developing a Deploying the BIRT Graphical Modeling Viewer to JBoss Tool for Eclipse Disseminate Report Content to an Application Server Subversive The Eclipse Enabling Plug-In for Integration and Subversion FEATURES Interoperability for Eclipse based Development An Introduction to the Corona Project Flexibility at the Roots of Eclipse 29 Flexibility at the Roots of Eclipse Solving the GUI Dilemma: SWTSwing and Eclipse on Solving the GUI Dilemma: Swing SWTSwing and Eclipse on Swing No trench in the world of Java is deeper then that between SWT and Swing or Eclipse and Sun. Unity is only found in the knowledge that everybody suff ers from this argument. But how to end this almost religious battle over the righteous GUI-toolkit? How to bang their heads together if they only know DEPARTMENT one point of view—for them or against them! Th e sister projects SWTSwing and Eclipse on Swing News & Trends (EOS) achieve this trick.
    [Show full text]
  • CICS TS for Z/OS: Java Applications in CICS Chapter 1
    CICS Transaction Server for z/OS 5.4 Java Applications in CICS IBM Note Before using this information and the product it supports, read the information in “Notices” on page 277. This edition applies to the IBM CICS® Transaction Server for z/OS® Version 5 Release 4 (product number 5655-Y04) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 1974, 2020. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this PDF.....................................................................................................vii Chapter 1. CICS and Java...................................................................................... 1 Java support in CICS....................................................................................................................................1 The OSGi Service Platform..................................................................................................................... 3 JVM server runtime environment...........................................................................................................4 JVM profiles............................................................................................................................................ 6 Structure of a JVM.................................................................................................................................. 7
    [Show full text]