Issue 3252: usage of user defined catalogs unclear. (pss-ftf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: To my mind the usage and mapping of user defined catalogs is weakly specified. It is not clearly described what is generated and what has to be implemented by user. Furthermore it is unclear, how to get access to an catalog. Subsequently I consider C++ only. I guess, a new implementation class has to be defined for each catalog, inheriting from the mapped class of that catalog and from Session. This is necessary to use the operation create_basic_session() returning a Session. Further I guess, the parameter catalog_type_name of this operation denotes a catalog supported by a prior registered user implemented session factory. Furthermore chapter 6.2 does not sufficiently explain the parameter storage_home_id of operation find_storage_home() from CatalogBase. In particular the sentence "In the case of type-specific catalogs (declared in PSDL), the provide declarations define valid storage_home_id parameters." allows multiple interpretations. What is meant? Resolution: accepted Revised Text: Remove user-defined catalogs from the specification. See also issue 3228 Revised Text: See http://cgi.omg.org/pub/pss_ftf/proposals.pdf (color LIGHT GRAY) Actions taken: January 26, 2000: received issue October 3, 2001: closed issue Discussion: End of Annotations:===== From: "Bertram Neubauer" To: , Subject: issue for PSS FTF Date: Wed, 26 Jan 2000 16:37:07 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Content-Type: text/plain; charset="iso-8859-1" X-UIDL: JPCe98@@e9GF)!!8M+e9 concerning: usage of user defined catalogs unclear. To my mind the usage and mapping of user defined catalogs is weakly specified. It is not clearly described what is generated and what has to be implemented by user. Furthermore it is unclear, how to get access to an catalog. Subsequently I consider C++ only. I guess, a new implementation class has to be defined for each catalog, inheriting from the mapped class of that catalog and from Session. This is necessary to use the operation create_basic_session() returning a Session. Further I guess, the parameter catalog_type_name of this operation denotes a catalog supported by a prior registered user implemented session factory. Furthermore chapter 6.2 does not sufficiently explain the parameter storage_home_id of operation find_storage_home() from CatalogBase. In particular the sentence "In the case of type-specific catalogs (declared in PSDL), the provide declarations define valid storage_home_id parameters." allows multiple interpretations. What is meant? Regards, Bertram .................................... Bertram Neubauer Humboldt University Berlin