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 98022 - Tags are not removed after undo
Summary: Tags are not removed after undo
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: _ sandipchitale
Depends on:
Reported: 2007-03-15 18:16 UTC by Roman Mostyka
Modified: 2007-07-30 18:13 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Roman Mostyka 2007-03-15 18:16:02 UTC
1. Create Visual Web Project.
2. Add Tree component to the page.
3. Add action event hadler for TreeNode.
4. Do undo (I did Ctrl+Z) several times (for undo everything that concerning Tree).
5. Run project.

Result: Get error:

"executePhase(RENDER_RESPONSE 6,com.sun.faces.context.FacesContextImpl@150a3dc)
threw exception
org.apache.jasper.JasperException: javax.faces.FacesException:
javax.faces.el.PropertyNotFoundException: javax.el.PropertyNotFoundException:
The class 'webapplication1.Page1' does not have the property 'tree1'."

Then look into JSP code of a web page, tags for Tree and TreeNode are still
here, though there is no any tree component in Designer View.
Comment 1 Peter Zavadsky 2007-03-15 18:17:40 UTC
Undo redo impl belongs to insync.
Comment 2 _ sandipchitale 2007-03-23 22:05:39 UTC
This has been a known issue with the way undo/redo works in VW (from the days 
of Creator). The undos performed while in Java tab that affect what was added 
through the designer can result in the Java source being out of sink with the 
jsp. In other words the undo/redos are assumed be performed in the editor in 
which the change was created. This may be hard for the user keep track of 
though. There are two possible solutions.

1. Clear the undo stack when the user switches between the editor sub-tabs 
i.e. Designer, JSP Editor, Java Editor. This is implementable.

2. Make sure that the Undo events are correctly synchronized and performed in 
all editors. This is a desirable solution.
Comment 3 _ sandipchitale 2007-07-30 18:13:19 UTC
Insync was designed that way from the begining. To support a unified Undo stack is considered an enhancement. We will 
look at it in the future.