|
Project: stp | |||||||
PREV NEXT | FRAMES NO FRAMES |
See:
Description
Packages | |
---|---|
com.ibm.rational.wvcm.stp | Extensions to the generic interfaces and infrastructure of the Workspace Versioning and Configuration Management (WVCM) API used in all domains. |
com.ibm.rational.wvcm.stp.cc | ClearCase-specific extensions to IBM Rational CM API and WVCM. |
com.ibm.rational.wvcm.stp.cq | Extensions to the Workspace Versioning and Configuration Management (WVCM) API providing access to ClearQuest repositories. |
javax.wvcm | The specification for the JSR-147 Workspace Versioning and Configuration Management (WVCM) API. |
An API through which programs may access IBM Rational requirements, change and configuration management services.
This CM API is a unified collection of Java interfaces and classes specifying a public API through which programming clients can interact with IBM Rational team products providing requirements, change and configuration management services. Such clients would typically be graphical or command-line user iterfaces or custom scripts or programs needing such services.
To access services through this API, the client invokes
javax.wvcm.ProviderFactory.createProvider
to
instantiate one of the provider classes named in the
StpProvider
,
CqProvider
, or
CcProvider
interfaces.
In this release one StpProvider class is available,
PROVIDER_CLASS
,
which provides access to ClearQuest databases and ClearCase
Remote Client servers through the properly installed and licensed IBM Rational
products for these resource repositories. Note that this provider does not
implement the CqProvider or CqProvider interfaces, but it does contain links
to component objects that do.
Future releases will provide provider classes for obtaining similar
services via other means.
The performance characteristics of this API may vary from operation to operation, although, currently, there is no way for the client to ask the provider which operations are expensive and which are not.
The API is partitioned into a number of packages. In addition to the packages
for standard and shared interfaces, there is one package for each
domain type
, which
includes proxy interfaces for each resource type supported by the
domain and a Provider interface extension that defines factory methods
for each of these proxy classes.
Clients of this API will use these packages:
javax.wvcm
-- WVCM: The Workspace Versioning and Configuration
Management API
(
JSR 147)
com.ibm.rational.wvcm.stp
--
Extensions to the WVCM infrastructure specific to this API and common to all
domains.com.ibm.rational.wvcm.stp.cq
--
Extensions to WVCM supporting the ClearQuest object modelcom.ibm.rational.wvcm.stp.cc
--
Extensions to WVCM supporting the ClearCase Remote Client object modelFor an overview of the API, continue with "core package overview".
StpLocation
.
The various forms of constructors for Selector have been moved to StpProvider as
factory methods for the new StpLocation objects. StpLocations can be used both
as javax.wvcm.Location objects and to examine and manipulate the various schemes
used to specify a location.
nest(...)
methods have been added to PropertyNameList.PropertyName, which generate a
NestedPropertyName.
StpResource.initMetaProperty()
, which stores (unchecked) a clean value
for a specified meta-property into a proxy.
This method will throw an exception if...
Valid values for this string are obtainable from an existing proxy using a StpResource.proxyType() method. This is sufficient mechanism for clients to use to reconstruct proxies they have persisted. The static method StpProvider.proxyType() is also defined, which maps a Class object for a CM API interface into the proxy-type string used by buildProxy to construct a proxy for that implements that interface.
ClearQuest record types, for example, are located in the "record" namespace, but record type names also appear in the "field" and "action" namespaces to disambiguate the simple names used for actions and fields in different record types. Thus "cq.record:Defect@7.0.0/SAMPL" is the location of the record type named "Defect". In addition, "cq.action:Defect/Submit@7.0.0/SAMPL" is the location of the action named "Submit" for record type "Defect" and "cq.field:Defect/Headline@7.0.0/SAMPL" is the location of the field definition for the "Headline" field of record type "Defect".
In the initial release, both "cq.action:Defect@7.0.0/SAMPL" and "cq.field:Defect/@7.0.0/SAMPL" could also be used to access the record type resource named "Defect". In this release, these locations to not address a record type resource, but address a folder resource, which contains either the actions or fields of the named record type, depending on the namespace used in the location. These folders will have their own unique RESOURCE_IDENTIFIERS.
|
Generated Sun 26-Oct-2008 10:17 AM | |||||||
PREV NEXT | FRAMES NO FRAMES |