Persistent State Service Avatar
  1. OMG Specification

Persistent State Service — Open Issues

  • Acronym: PSS
  • Issues Count: 28
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
PSS-47 Eliminate PID_DA definition PSS 1.0b1 open
PSS-46 PDS_DA::DAObjectID PSS 1.0b1 open
PSS-45 PDS_DA DDL should exclude type Any PSS 1.0b1 open
PSS-44 SD interface PSS 1.0b1 open
PSS-48 Support for DAObject interface PSS 1.0b1 open
PSS-43 PO::delete and POM::delete PSS 1.0b1 open
PSS-42 PO::store/restore PSS 1.0b1 open
PSS-41 PO::disconnect and POM::disconnect parameters PSS 1.0b1 open
PSS-40 PO::connect and POM::connect exception needed PSS 1.0b1 open
PSS-37 PIDFactory::create_PID* definitions PSS 1.0b1 open
PSS-36 PID derivation PSS 1.0b1 open
PSS-39 PO::p attribute should be readonly PSS 1.0b1 open
PSS-38 Returning PDS from PO::connect PSS 1.0b1 open
PSS-33 PID attributes should be readonly PSS 1.0b1 open
PSS-32 PID additional attributes PSS 1.0b1 open
PSS-31 Factory interface should be specified PSS 1.0b1 open
PSS-30 Issue POS 2.0 RFP PSS 1.0b1 open
PSS-35 Typo in PID section PSS 1.0b1 open
PSS-34 PID vs. OID definition PSS 1.0b1 open
PSS2-8 PSDL Grammar problems: Page 3-33 PSS 1.0 open
PSS2-7 PSDL Grammar problems: Page 3-31 PSS 1.0 open
PSS2-9 PSDL Grammar problems: Page 3-28 PSS 1.0 open
PSS2-10 Unable to find the refrence to the ConnectorRegistry from the appendix A.1 PSS 1.0 open
PSS2-3 existence of a ConnectorRegistry in the CosPeristentState module PSS 1.0 open
PSS2-5 PSS FTF: Sequence should be added in the PSDL state types PSS 1.0 open
PSS2-2 The connectorRegistry interface is removed from spec. but still used PSS 1.0 open
PSS2-4 PSDL Grammar problems: Page 3-33 PSS 1.0 open
PSS2-6 PSDL Grammar problems: Page 3-29 PSS 1.0 open

Issues Descriptions

Eliminate PID_DA definition

  • Key: PSS-47
  • Legacy Issue Number: 43
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The definition for the PID_DA should be eliminated and the old attribute moved to the base PID definition. This will provide an invariant and abstract representation for all persistence state.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PDS_DA::DAObjectID

  • Key: PSS-46
  • Legacy Issue Number: 42
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: typedef string DAObjectID should be typedef sequence<octet> DAObjectID. This will allow more flexibility in the PDS_DA implementation without breaking any functionality.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PDS_DA DDL should exclude type Any

  • Key: PSS-45
  • Legacy Issue Number: 41
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The inclusion of type Any in object definitions should be eliminated, because it makes schema evolution completely unmanageable.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

SD interface

  • Key: PSS-44
  • Legacy Issue Number: 40
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: It is unclear how SD object implementations get intially connected to the POS implementation.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

Support for DAObject interface

  • Key: PSS-48
  • Legacy Issue Number: 44
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: pg. 5-24, paragraph 1, section 5.10.2 states that "a data object is not require to support this interface." If so, there is not a way to free the storage for a data object or generate a PID.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PO::delete and POM::delete

  • Key: PSS-43
  • Legacy Issue Number: 39
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The delete operation should not have a PID parameter – what does it mean if the PID specified is not the currently connected PID?

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PO::store/restore

  • Key: PSS-42
  • Legacy Issue Number: 38
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Because para. 3, pg. 5-12 states that a PO can only have a single connection at a time, all behavior of these operations would need to be provided by the POM, which is difficult to do interoperably.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PO::disconnect and POM::disconnect parameters

  • Key: PSS-41
  • Legacy Issue Number: 37
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The PID parameter is extraneous, as the specification states that a PO can only have a single connection at a time.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PO::connect and POM::connect exception needed

  • Key: PSS-40
  • Legacy Issue Number: 36
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: An exception is needed to inform of an invalid connection (DDL type, protocol, etc.).

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PIDFactory::create_PID* definitions

  • Key: PSS-37
  • Legacy Issue Number: 33
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The definition should not contain "...key that identifies a particular PID implementation." Overall these definitions contains a lot of confusion about PID identity.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PID derivation

  • Key: PSS-36
  • Legacy Issue Number: 32
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The PID interface derivation usage in the PID_DA and other examples in the specification limit the ability of the protocol to be decoupled from the datastore as intended.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PO::p attribute should be readonly

  • Key: PSS-39
  • Legacy Issue Number: 35
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: This attribute should simply reflect the currently connected PID, to avoid placing an additional burden on the PO implementation which is not needed.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

Returning PDS from PO::connect

  • Key: PSS-38
  • Legacy Issue Number: 34
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The PDS reference should not be returned from the PO::connect operation, as this creates a number of implementation problems.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PID attributes should be readonly

  • Key: PSS-33
  • Legacy Issue Number: 29
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Attributes of the PID interface should be readonly and only settable through their initial creation by the PIDFactory and the service implementation.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PID additional attributes

  • Key: PSS-32
  • Legacy Issue Number: 28
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The PID should add attributes for the Datastore object reference and an opaque PersistentStateIdentifier. This allows maximum flexibility without the need to subclass the PID interface.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

Factory interface should be specified

  • Key: PSS-31
  • Legacy Issue Number: 27
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The Factory interfaces should be specified for all service component interfaces to provide for integration with the Lifecycle Service.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

Issue POS 2.0 RFP

  • Key: PSS-30
  • Legacy Issue Number: 26
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: TRC has found several issues that cannot be addressed within this forum and which would need to be addressed in a new POS 2.0 spec.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

Typo in PID section

  • Key: PSS-35
  • Legacy Issue Number: 31
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: pg. 5-9, paragraph 6, remove extra p from "the ppersistent object..."

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PID vs. OID definition

  • Key: PSS-34
  • Legacy Issue Number: 30
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The last sentence of para. 4 on pg. 5-9 is not implementable. How is the new storage allocation and location determined?

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PSDL Grammar problems: Page 3-33

  • Key: PSS2-8
  • Legacy Issue Number: 5504
  • Status: open  
  • Source: INRIA ( Philippe Merle)
  • Summary:

    paragraph 3.2.5.6 : There is two mistakes : "abstract_storagehome" and
    "abstract""storagehome" are referenced instead of "abstract
    storagehome

  • Reported: PSS 1.0 — Mon, 15 Jul 2002 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:09 GMT

PSDL Grammar problems: Page 3-31

  • Key: PSS2-7
  • Legacy Issue Number: 5503
  • Status: open  
  • Source: INRIA ( Philippe Merle)
  • Summary:

    paragraph 3.2.5.1 : the production <abstract_storage_type_member> refers
    to
    <abstract_storage_type_dcl> which is defined in production 10 as
    <psdl_state_dcl>.
    Pick one or the other and changes references as required

  • Reported: PSS 1.0 — Mon, 15 Jul 2002 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:09 GMT

PSDL Grammar problems: Page 3-28

  • Key: PSS2-9
  • Legacy Issue Number: 5501
  • Status: open  
  • Source: INRIA ( Philippe Merle)
  • Summary:

    Production 19 : "abstract_storagehome" is not correct. Replace it with
    "abstract storagehome".

  • Reported: PSS 1.0 — Mon, 15 Jul 2002 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:09 GMT

Unable to find the refrence to the ConnectorRegistry from the appendix A.1

  • Key: PSS2-10
  • Legacy Issue Number: 4801
  • Status: open  
  • Source: Anonymous
  • Summary:

    Chapter 1.5 mentions the ConnectorRegistry object. From the code sample I assume that it should be part of the CosPersistentState module. Hoveever, I am unable to find the refrence to the ConnectorRegistry from the appendix A.1, "Complete IDL" (shouldn't it be "Complete PSDL" instead?)

    the ConnectorRegistry is present also in the appendix B, "Example: An Implementation of the Naming Service"

  • Reported: PSS 1.0 — Fri, 4 Jan 2002 05:00 GMT
  • Updated: Sat, 7 Mar 2015 06:09 GMT

existence of a ConnectorRegistry in the CosPeristentState module

  • Key: PSS2-3
  • Legacy Issue Number: 7968
  • Status: open  
  • Source: EsotericSystems, Inc. ( David Knox)
  • Summary:

    The referenced page cites the existence of a ConnectorRegistry in the CosPeristentState module. But there is no such interface in the IDL. Perhaps I've missed something?

  • Reported: PSS 1.0 — Fri, 3 Dec 2004 05:00 GMT
  • Updated: Sat, 7 Mar 2015 06:09 GMT

PSS FTF: Sequence should be added in the PSDL state types

  • Key: PSS2-5
  • Legacy Issue Number: 6698
  • Status: open  
  • Source: National Lab, Distributed Process, China ( Deng Bo)
  • Summary:

    In the PSDL state type grammar, the state member can't be a sequence type as the following text:
    formal/02-06-05 on page 3-8
    <psdl_state_type_spec> ::= <base_type_spec>

    <string_type>
    <wide_string_type>
    <abstract_storagetype_ref_type>
    <scoped_name>
    ...
    <scoped_name> must denote a previously declared [abstract or local] interface,
    struct, union, type, [abstract] valuetype, or a previously defined abstract storagetype.
    ...

    It's very useful if the sequence type be a state member, which is currently not possible.

    Resolution:

    Replace the following text in formal/02-06-05 on page 3-8
    <psdl_state_type_spec> ::= <base_type_spec>

    <string_type>
    <wide_string_type>
    <abstract_storagetype_ref_type>
    <scoped_name>

    with
    <psdl_state_type_spec> ::= <base_type_spec>

    <sequence_type>
    <string_type>
    <wide_string_type>
    <abstract_storagetype_ref_type>
    <scoped_name>
  • Reported: PSS 1.0 — Tue, 16 Dec 2003 05:00 GMT
  • Updated: Sat, 7 Mar 2015 06:09 GMT

The connectorRegistry interface is removed from spec. but still used

  • Key: PSS2-2
  • Legacy Issue Number: 6683
  • Status: open  
  • Source: National Lab, Distributed Process, China ( Deng Bo)
  • Summary:

    1. formal/02-09-06 on page 1-6 import org.omg.*; CORBA.ORB myOrb = CORBA.ORB.init(); CosPersistentState.ConnectorRegistry connectorRegistry = CosPersistentState.ConnectorRegistryHelper.narrow( myOrb.resolve_initial_references("PSS") ); CosPersistentState.Connector connector = connectorRegistry.find_connector(""); ... 2. formal/02-09-06 on page B-6 public class NamingServer { public static void main(String[] args)

    { // initializes ORB CORBA.ORB myOrb = CORBA.ORB.init(args); // get connector registry CosPersistentState.ConnectorRegistry registry = CosPersistentState.ConnectorRegistryHelper. narrow( myOrb.resolve_initial_references("PSS") ); // get connector ... }

    Resolution:

    1. Remove the following text in formal/02-09-06 on page 1-6

    CosPersistentState.ConnectorRegistry connectorRegistry = CosPersistentState.ConnectorRegistryHelper.narrow( myOrb.resolve_initial_references("PSS") ); CosPersistentState.Connector connector = connectorRegistry.find_connector("");

    2. Remove the following text in formal/02-09-06 on page B-6

    // get connector registry CosPersistentState.ConnectorRegistry registry = CosPersistentState.ConnectorRegistryHelper. narrow( myOrb.resolve_initial_references("PSS") );

  • Reported: PSS 1.0 — Sat, 6 Dec 2003 05:00 GMT
  • Updated: Sat, 7 Mar 2015 06:09 GMT

PSDL Grammar problems: Page 3-33

  • Key: PSS2-4
  • Legacy Issue Number: 5505
  • Status: open  
  • Source: INRIA ( Philippe Merle)
  • Summary:

    paragraph 3.2.6.4 : The <absract_storagehome_header> is not correctly
    defined.
    The production [<primary_key_dcl>] is missing. Add it.

  • Reported: PSS 1.0 — Mon, 15 Jul 2002 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:09 GMT

PSDL Grammar problems: Page 3-29

  • Key: PSS2-6
  • Legacy Issue Number: 5502
  • Status: open  
  • Source: INRIA ( Philippe Merle)
  • Summary:

    Production 27 : a double quote is missing : {" instead of "{". Add the
    double quote.
    Production 45 : an underscore is missing in the name of the rule.
    Replace <abstract storagehome_name> with <abstract_storagehome_name>
    Production 48: there is a redundancy : square brackets are not
    useful.Remove them

  • Reported: PSS 1.0 — Mon, 15 Jul 2002 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:09 GMT