Issue 26398 - Assertion appears while opens a new inserted entry
Summary: Assertion appears while opens a new inserted entry
Status: CLOSED FIXED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: mikhail.voytenko
QA Contact: issues@api
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-12 14:11 UTC by ocke.janssen
Modified: 2013-02-24 21:09 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description ocke.janssen 2004-03-12 14:11:44 UTC 
call
entry->storeToEntry(...)
and after that call
xEmbedFactory->createInstanceInitFromEntry(....)
for that entry without to commit it
Comment 1 mikhail.voytenko 2004-03-12 14:52:54 UTC 
The problem was that in case a new sub storage is created for writing, changed,
comminted, disposed, then reopened for reading, disposed, and after that
reopened for writing again, the latest opened for writing wersion does not
contain the commited changes.
Comment 2 mikhail.voytenko 2004-03-12 14:53:33 UTC 
The problem was that in case a new sub storage is created for writing, changed,
comminted, disposed, then reopened for reading, disposed, and after that
reopened for writing again, the latest opened for writing wersion does not
contain the commited changes.
Comment 3 mikhail.voytenko 2004-04-23 14:37:18 UTC 
set to fixed.
Comment 4 mikhail.voytenko 2004-07-12 13:07:54 UTC 
Now a different factory method is used to create an object, so the scenario is
probably is a little bit different. But the storage access should be pretty the
same, so if the bug had still beed there the problem would still appear. So I
set the bug to verified.
Comment 5 mikhail.voytenko 2005-01-24 10:12:08 UTC 
.