Browse Prior Art Database

Hierarchical and Object-Oriented Message Facility for Reuse

IP.com Disclosure Number: IPCOM000117103D
Original Publication Date: 1995-Dec-01
Included in the Prior Art Database: 2005-Mar-31
Document File: 2 page(s) / 73K

Publishing Venue

IBM

Related People

Hlava, A: AUTHOR

Abstract

Disclosed is a hierarchical and object-oriented message facility that allows easy reuse by different software products. This facility allows reuse of message facility code while making it easy to customize for unique product requirements. This is done by selecting the appropriate "level" in the object containment hierarchy to customize by subclassing or replacing the class at that level.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 53% of the total text.

Hierarchical and Object-Oriented Message Facility for Reuse

      Disclosed is a hierarchical and object-oriented message
facility that allows easy reuse by different software products.  This
facility allows reuse of message facility code while making it easy
to customize for unique product requirements.  This is done by
selecting the appropriate "level" in the object containment hierarchy
to customize by subclassing or replacing the class at that level.

      The message facility disclosed here consists of a class
containment hierarchy which matches the typical structure of
messages.  Normally, messages consist of:
  o  A message catalog which contains the translatable messages
  o  The message text, including special characters which indicate
      where data will be inserted at run-time.
  o  The run-time insert data

      The class hierarchy in the disclosed facility is shown in the
Figure.  The following describes each class shown in the Figure:
  (1) Insert: This class encapsulates a single variable data insert
in
       a message.  This includes the formatting characters for the
       insert (e.g., %1$s) and the variable insert data itself (e.g.,
       /var/pd).  This class would be subclassed by the reusing
product
       if it has non-standard data types which need to be inserted in
       messages.
  (2) InsertList: This class encapsulates the list of Insert objects
       which are to be merged with a message.  This class would
normally
       be used as-is by the reusing product.
  (3) InsertString: This class encapsulates the complete formatting
       string of a message (e.g., Error opening file %1$s) along with
       the InsertList object containing the variable data to be
merged
       with the message.
  (4) Messa...