This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 85436 - BPEL sources sometimes disappear when editing
Summary: BPEL sources sometimes disappear when editing
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Denis Anisimov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-21 13:10 UTC by Mikhail Kondratyev
Modified: 2006-09-29 20:10 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
video to reproduce (382.35 KB, application/octet-stream)
2006-09-21 13:18 UTC, Mikhail Kondratyev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail Kondratyev 2006-09-21 13:10:29 UTC
Sometimes when you edit BPEL code sources disappear without any visible reason.
Many engineers here have seen this but exact scenario is not known.
Steps to reproduce (with this steps bug can be reproduced with relatively high
probability):
 - create new sync sample
 - switch to sources
 - do the following quick:
 - type <assign>, then type </assign>
 - after assign type <copy wait a bit  - <copy will disappear
The attached flash demo shows this scenario
Comment 1 Mikhail Kondratyev 2006-09-21 13:18:24 UTC
Created attachment 34305 [details]
video to reproduce
Comment 2 Alexey Yarmolenko 2006-09-21 16:14:01 UTC
Could this bug have the same root cause with IZ 82295?
 
Comment 3 Michael Frisino 2006-09-21 16:16:05 UTC
bug 82295
Comment 4 Denis Anisimov 2006-09-22 10:46:26 UTC
This was a problem in validation logic.

Validators used start/endTransaction() methods for locking OM while they
are performed validation.
The problem that endTransaction() always flushes OM into document.
So when validation was performed while editing it flushes its last state to 
swing document. It looks like lost changes in editor.

Not situation is corrected via obtian READ lock on OM.
This lock is never flush OM into document so there no any problem with 
described behavior.
Comment 5 Mikhail Kondratyev 2006-09-29 08:57:08 UTC
Verified in build from 2006.09.27
Could not reproduce the bug
Comment 6 Mikhail Kondratyev 2006-09-29 12:15:09 UTC
changing the state to Verified