Browse Prior Art Database

Extending the concepts of suite and application beans to the J2EE framework

IP.com Disclosure Number: IPCOM000015284D
Original Publication Date: 2002-Jan-29
Included in the Prior Art Database: 2003-Jun-20
Document File: 1 page(s) / 38K

Publishing Venue

IBM

Abstract

The basic concept described in this disclosure is to expand on the concept of a meta-installer. By taking advantage of the concepts offered by the J2EE standard, the base concepts of a Java meta-installer can be opened up into a more robust and natural fit for installation of distributed applications by converting a standard serialized Java object into an Enterprise Java Bean (EJB).

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 1

Extending the concepts of suite and application beans to the J2EE framework

    The basic concept described in this disclosure is to expand on the concept of a meta-installer. By taking advantage of the concepts offered by the J2EE standard, the base concepts of a Java meta-installer can be opened up into a more robust and natural fit for installation of distributed applications by converting a standard serialized Java object into an Enterprise Java Bean (EJB).

Current architecture of an existing Toolkit limits the product beans reusability by enforcing a rigid containment mechanism known as the Suite Bean. Additionally, the suite bean and product bean architecture is based on a proprietary set of properties known only to the consumer classes contained within the ISIT toolkit. The means of transport of the suite bean itself is accomplished through yet another proprietary authentication and transport mechanism, contained and known only by the toolkit and client. However, the information and contents that actually make up the product and suite bean is in itself inherently open, and could be consumed by any process if not so tightly coupled .

J2EE is a much more natural environment in which to store installation binaries, packaging, and configuration variables. It allows any application to use an application server to access the product/suite beans and their methods contained within (to populate the variables or binaries) in an open-standard way. Additionally, it provid...