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 176551 - Validation error messages from the XML Literal Editor are persistent
Summary: Validation error messages from the XML Literal Editor are persistent
Status: CLOSED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Mapper (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Vladimir Yaroslavskiy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-11 08:40 UTC by terrybraun
Modified: 2010-11-24 12:54 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Screenshot of verification (66.73 KB, image/jpeg)
2010-11-24 12:52 UTC, senthilprabhu 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description terrybraun 2009-11-11 08:40:04 UTC 
Using the XML Literal Editor in "XML Subelement" mode, when the user enters invalid XML code and "Ok" the editor correctly generates and displays an error message. If the user makes major changes, like deleting all code or even  switching to "Text" mode, the error persists at the bottom of the editor. This persistence of the original error message is annoying and misleading.

Steps:
a) Bring up XML Literal Editor in "XML Subelement" mode
b) Enter:  abc
c) Click "Ok" - "Content is not allowed in prolog." is displayed
d) Make any change to the code, or mode of the editor.

The message persists.
Comment 1 Vladimir Yaroslavskiy 2009-11-12 02:45:51 UTC 
Error message (red font) is duplicated: if user enters invalid xml literal, error dialog is shown and ti is enough. Therefore, I hide error message (with red font) at all.
Comment 2 senthilprabhu 2010-11-24 12:52:34 UTC 
Created attachment 103279 [details]
Screenshot of verification
Comment 3 senthilprabhu 2010-11-24 12:54:31 UTC 
The error messages are not shown anymore. 
The screenshot of the error dialog is attached.

This issue is verified to work correctly in the CAPS M5 (20101103-1248) build. This issue can be closed.