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 164701 - delete a component in Visual Designer causes excetion
Summary: delete a component in Visual Designer causes excetion
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: All Linux
: P3 blocker (vote)
Assignee: _ deva
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-07 15:51 UTC by frankye
Modified: 2009-05-08 16:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
delete exception log (4.16 KB, text/plain)
2009-05-07 15:52 UTC, frankye
Details

Note You need to log in before you can comment on or make changes to this bug.
Description frankye 2009-05-07 15:51:41 UTC
Tried with following env
changeset 129873:faf64164d54e path http://hg.netbeans.org/web-main
changeset 129910:1a3cbce60154 path http://hg.netbeans.org/main-silver
as well as nb6.7beta 

JAVA_HOME=/usr/java/jdk1.5.0_17/bin/java
OS: SUSE 11g 2.6.25.20-0.1-pae #1 SMP

1) create Java Web|Web Application project, with JavaEE5 version, and
Glassfish 2.1 server, all other options default
2) add Visual Web JSF Page to web pages folder
3) drop two buttons
4) safe with context menu on page tab
5) close the page by cross on the tab
6) reopen
7) delete one of buttons
8) exception from insync
Comment 1 frankye 2009-05-07 15:52:15 UTC
Created attachment 81742 [details]
delete exception log
Comment 2 frankye 2009-05-07 15:53:57 UTC
work around is that to build the project before the step 5, where before open the page, build the project first. The
exception is gone. 
Comment 3 Sergey Petrov 2009-05-08 08:02:55 UTC
ok, thanks

from issue 128930 it may be libraries problem, do you have standard glassfish, java, netbeans, path or have own j2ee
libraries somewhere (may be in java/ext etc)?
It may have sense to attach complete message.log to the issue.
Comment 4 frankye 2009-05-08 16:26:57 UTC
yes, it is related libraries configurations. using Tomcat 6.0, same steps working fine.
However, since jsf 1.2_04 has a few problems in run time. So Glassfish v2 is frequently being updated to a newer jsf 1.2
minor release. This is the root cause.

Is any documentation for this type of Exceptions for Visual Web Cluster?