Issue 3155: PdmContext is insufficient as a TraversalCriteria                                                                                                                                                       (pdm-rtf)
Source: Hewlett-Packard (Mr. Duane Silkworth, nobody duane.silkworth@eds.com)
Nature: Revision
Severity: Critical
Summary: The CosGraphs module specifies that Traversals are be created by the 
TraversalFactory::create_traversal_on() operation, which returns a Traversal
and takes 3 input parameters: a root Node, a TraversalCriteria, and a mode flag.

In the PDM Enablers PdmViews module, it is specified that PdmContext is a subtype of 
TraversalCriteria, and thus a PdmContext can be used to create a Traversal.  The 
PdmContext is effective as a filter to specify that only the items of interest to the client
are returned.  However, it is insufficient to create an effective Traversal object.
Nowhere is there defined a traversal path name, algorithm or strategy which indicates
which roles and relationships to follow.

As a possible solution, it is sugggested that the PdmContext not inherit
TraversalCriteria.  Rather a TraversalCriteria should be created by a new interface's
operation, which takes as input both a PdmContext and some definition of a
PDM Enablers-specific traversal path.
Resolution: Duplicate of 3154. Closed
Revised Text: 
Actions taken:
October 10, 2000: closed issue
Discussion: 

End of Annotations:=====
Date: Mon, 20 Dec 1999 16:35:59 -0500 (EST)
Message-Id: <199912202135.QAA11174@emerald.omg.org>
From: duane.silkworth@omg.org
To: juergen@omg.org, web-incoming@omg.org
Subject: Issue Report
Content-Type: text
X-UIDL: c$0!!?a<!!]f+!!JkS!!

Name: Duane Silkworth
Company: Metaphase Technology Group / SDRC
mailFrom: duane.silkworth@omg.org
Notification: No
Specification: PDM Enablers
Section: 2.5.3.4
Formal #: mfg/98-02-02
Version: 1.2
Revision_Date: 11/19/99
Page: 104
Nature: Revision
Severity: Critical
full_desc: PdmContext is insufficient as a TraversalCriteria

The CosGraphs module specifies that Traversals are be created by the 
TraversalFactory::create_traversal_on() operation, which returns a
Traversal
and takes 3 input parameters: a root Node, a TraversalCriteria, and a
mode flag.

In the PDM Enablers PdmViews module, it is specified that PdmContext
is a subtype of 
TraversalCriteria, and thus a PdmContext can be used to create a
Traversal.  The 
PdmContext is effective as a filter to specify that only the items of
interest to the client
are returned.  However, it is insufficient to create an effective
Traversal object.
Nowhere is there defined a traversal path name, algorithm or strategy
which indicates
which roles and relationships to follow.

As a possible solution, it is sugggested that the PdmContext not
inherit
TraversalCriteria.  Rather a TraversalCriteria should be created by a
new interface's
operation, which takes as input both a PdmContext and some definition
of a
PDM Enablers-specific traversal path.
submit: Submit Issue Report