Technical note: using the San Francisco frameworks with visualage for Java
IBM1
TL;DR: This technical note describes the advantages of using the VisualAgeTM for JavaTM (VAJ) integrated development environment when working with the IBM San Francisco frameworks.
Abstract: This technical note describes the advantages of using the VisualAgeTM for JavaTM (VAJ) integrated development environment when working with the IBM San FranciscoTM frameworks. It also discusses minimum system requirements, how to get started, and tips for using VAJ to exploit the frameworks. To fully utilize the material, the reader should be familiar with Java programming and with the basic concepts of integrated development environments.
Citations
More filters
IBM1
TL;DR: The paper outlines the development-time benefits of using VisualAge for Java and introduces the IBM VisualAge® for JavaTM product, a robust, visual suite of tools designed for rapid prototyping and enterprise application development.
Abstract: This paper introduces the IBM VisualAge® for JavaTM product, a robust, visual suite of tools designed for rapid prototyping and enterprise application development. The paper outlines the development-time benefits of using VisualAge for Java.
48 citations
TL;DR: A generic framework for the development of software components and an interconnection language, COMPILE, for the specification of software systems from components is proposed and a late binding mechanism between components based on meta-protocols is required.
Abstract: Software modeling based on the assembly of reusable components to support software development has not been successfully implemented on a wide scale. Several models for reusable software components have been suggested which primarily address the wiring-level connectivity problem. While this is considered necessary, it is not sufficient to support an automated process of component assembly. Two critical issues that remain unresolved are (1) semantic modeling of components, and (2) deployment process that supports automated assembly. The first issue can be addressed through domain-based standardization that would make it possible for independent developers to produce interoperable components based on a common set of vocabulary and understanding of the problem domain. This is important not only for providing a semantic basis for developing components but also for the interoperability between systems. The second issue is important for two reasons: (a) eliminate the need for developers to be involved in the final assembly of software components, and (b) provide a basis for the development process to be potentially driven by the user. To resolve the above remaining issues (1) and (2), a late binding mechanism between components based on meta-protocols is required. In this paper we address the above issues by proposing a generic framework for the development of software components and an interconnection language, COMPILE, for the specification of software systems from components. The computational model of the COMPILE language is based on late and dynamic binding of the components' control, data, and function properties [1] through the use of adapters. The use of asynchronous callbacks for method invocation allows control binding among components to be late and dynamic. Data exchanged between components is defined through the use of a meta-language that can describe the semantics of the information but without being bound to any specific programming language type representation. Late binding to functions is accomplished by maintaining domain-based semantics as component meta-information. This information allows clients of components to map generic requested service to specific functions.
9 citations
Patent•
13 Feb 2002
TL;DR: In this paper, a distributed computing system is provided in which developer computers (100) have stored within their memories an extended class loader (102) and a virtual machine program (12).
Abstract: A distributed computing system is provided in which developer computers (100) have stored within their memories an extended class loader (102) and a virtual machine program (12). When an application is run utilising the virtual machine program (12) the virtual machine program (12) causes the extended class loader (102) to be activated whenever a reference to a class is to be processed. The extended class loader (102) initially determines whether the referenced class is stored in the memory of the developer computer (100) and if this is not the case, interrupts processing to download an archive file (9.1-9.n) including the referenced class prior to continuing processing.
3 citations
TL;DR: Two years ago, the IBM Systems Journal published an issue containing papers on the content and use of the IBM SanFranciscoTM product, and this essay provides a brief review of some of these changes and introduces the papers in this issue related to the San Francisco theme.
Abstract: Two years ago, the IBM Systems Journal published an issue containing papers on the content and use of the IBM SanFranciscoTM product. Since that time we have seen changes: in the product, in how customers are using the product, and in the marketplace in general. This essay provides a brief review of some of these changes and introduces the papers in this issue related to the SanFrancisco theme.
Cites methods from "Technical note: using the San Franc..."
...A technical note explained how to use SanFrancisco together with VisualAge* for Java** to build applications.(5) Other papers discussed these questions and speculated on how the product would be used to build applications....
[...]