计算机编程类外文翻译

计算机编程类外文翻译内容摘要：

vironment (PDE) supplies tools that automate the creation, manipulation, debugging, and deploying of plugins. The PDE is part of the Eclipse SDK and is not a separately launched tool. In line with the general Eclipse platform philosophy, the PDE provides a wide variety of platform contributions (., views, editors, wizards, launchers, etc.) that blend transparently with the rest of the Eclipse workbench and assist the developer in every stage of plugin development while working inside the Eclipse workbench. PDE perspective. A specialized perspective includes views and shortcuts to mands used most frequently during plugin development. Host Versus Runtime workbench. The workbench that you are running as you develop your plugin is the host workbench. After you are happy with your plugin and want to test it, you can launch another workbenchthe runtime workbench. This will utilize the same plugins as the host workbench, but it will also run the plugins you were working on in the host workbench. Debugging plugins. The Java debugger enables plete control while testing plugins in the runtime workbench. Packaging plugins. Tools for packaging plugins and features for distribution to users via an update site are provided. This book does not address plugin development specifically, but all Eclipse capabilities described here are applicable to the PDE. Other books in this series describe patterns for plugin development (Gamma and Beck, 2020) and cover the details of building mercialquality plugins (Clayberg and Rubel, 2020). Web Tools Platform The Web Tools Platform (WTP) project was formally approved by the Eclipse Board in June 2020 and received initial open source code contributions from IBM and Object Web. At the time this book was written, those contributions were being reviewed and assimilated into the first milestone integration build. This project is of great importance to the Eclipse munity and is 山东建筑大学毕业设计外文文献及译文 8 likely of interest to most readers of this book. It is still in a formative stage。 noheless, here we review the project39。 s charter and summarize its expected integration into the Eclipse IDE. The mission of the Web Tools Platform project is to provide a generic, extensible, and standardsbased tool platform that builds on the Eclipse platform and other core Eclipse technologies. The project will deliver a mon foundation of frameworks and services upon which software providers can create specialized, differentiated offerings for J2EE and Webcentric application development. Key objectives are to enable product innovation with adherence to vendorneutral standards and technologies while delivering practical solutions to real development concerns. The WTP project is posed of two parts. The Web Standard Tools subproject will provide a mon infrastructure targeting Webenabled applications. This includes tools for developing threetier applications (presentation, business, and data logic) and publishing the resulting system artifacts to servers. Tools provided by this subproject will include the following: Standard languages. Support will be provided for HTML/XHMTL, XML, XML Schema, Web Services, XQueries, SQL, and other languages used by Webcentric applications. Editors. Editors will be provided for supported languages, including consistent features for outlines, Content Assist, templates, and formatting. Validators. Languages based on XML will be validated against associated schemas and other semantics from the specifications. Server publication. The workbench will provide mands and views for starting, stopping, publishing, and running applications on multiple target servers. The J2EE Standard Tools subproject will provide mon infrastructure for developing applications based on J2EE specifications targeting J2EEpliant application servers. Deliverables include generic J2EE tools for other Eclipsebased projects and products, and IDE workbench plugins that support developing, deploying, testing, and debugging J2EE applications on JCPpliant servers. The J2EE workbench will support use cases such as developing a JSP page, enhancing the Pet Store blueprint application, and exposing an EJB session bean as a Web Service. Tools provided by this subproject will include the following: 山东建筑大学毕业设计外文文献及译文 9 J2EE artifacts. Tools will support EJB, Servlet, JSP, JCA, JDBC, JTA, JMS, JMX, JNDI, and Web Services. JSP editor. The editor will support mixed HTML and JSP tags, including JSP tag libraries, plus outline, Content Assist, templates, and formatting. JSP refactoring. Java refactoring (., renaming a class, method, or package) will find and refactor dependencies within JSP pages. Search facilities. Search criteria are aware of syntax for JSP, XML, and other document types. For example, searching for a method name includes cases where that name is used as a method, but not when used in other text strings. Comparison of syntax. Comparing two JSP or XML files considers syntax while identifying logical code constructs, such as when viewing differences between two versions of a JSP file in a repository. Details and downloads are available on the Web Tools project Web site, . Rich Client Platform The Eclipse Rich Client Platform (RCP) is more notable for what it doesn39。 t have than for what it has. Although the Eclipse platform is designed to serve as an open tools platform, it is architected so that its ponents could be used to build just about any client application. The minimal set of plugins needed to build a rich client application is collectively known as the Rich Client Platform. These rich applications are still based on a dynamic plugin model, and the UI is built using the same toolkits and extension points. The layout and function of the workbench is under finegrained control of the plugin developer. When con。