Ticket #118 (closed enhancement: fixed)

Opened 12 years ago

Last modified 12 years ago

COLTT queries on persistence interfaces

Reported by: michelpons Owned by: Michael Halloran
Priority: minor Milestone: 2.2
Component: COLoggers Version: Development
Keywords: persistence Cc: michaelhalloran

Description

I am using PRO/II 8.2, in fact the material used a while ago for ticket #39. It involves also an old version of the COUSCOUS library (1.14). I am looking at the start of the log file. PRO/II queries in sequence about IPersistPropertyBag, IPersistStorage, IPersistStreamInit and IPersistStream. All queries, except the last one, return an error (0x800004002). Now the PME (PRO/II) knows that the UO supports only IPersistStream. COLTT is then releasing the PMC IPersistStream interface and then carries the same sequence of queries as the PME about the persistence interfaces. I wonder why there is not just a query on IPersistStream interface which has been found as present.

Attachments

proii_030912_154834.log (96.3 KB) - added by michelpons 12 years ago.
Log file obtained with COLTT 2.1 Development build
Unconnected.prz (24.1 KB) - added by michelpons 12 years ago.
PRO/II 8.2 input file
proii_072212_215854.zip (17.6 KB) - added by michaelhalloran 12 years ago.
PRO/II Load and Save example with COLTT-initiated entries corrected.

Change History

Changed 12 years ago by michelpons

Log file obtained with COLTT 2.1 Development build

Changed 12 years ago by michelpons

PRO/II 8.2 input file

Changed 12 years ago by michaelhalloran

PRO/II Load and Save example with COLTT-initiated entries corrected.

comment:1 Changed 12 years ago by michaelhalloran

  • Status changed from new to closed
  • Resolution set to fixed

Due to a coding error COLTT was reporting PME calls as COLTT calls on the IPersist interface after the first call to Release on the IPersistStream Interface. The latest version of COLTT 2.1 ahows that PRO/II is making repeated QueryInterface calls on persistence interface and that Save calls do not correspond to use of File>Save As but to the use of Load and Edit. I suspect that PRO/II maintains the saved state of a Unit in memory updating whenever there is an edit. The saved state is then written to file by PRO/II on File>Save without needing to call the PMC.

Note: See TracTickets for help on using tickets.