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 94171 - Code generated for JSF RI dataTable are not deleted when data table itself is deleted
Summary: Code generated for JSF RI dataTable are not deleted when data table itself is...
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: _ deva
Depends on:
Reported: 2007-02-02 23:33 UTC by bugbridge
Modified: 2007-02-02 23:33 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2007-02-02 23:33:33 UTC
Original status: 5-Cause Known; Suggested Status: NEW

Original Target Release: mako_dev; Suggested Target Milestone : Dev

These items should be added to the Keywords: RELNOTE

Original submitter: wjprakash

After deleting the data table the code generated by insync are still left 
behind thus causing compilation error.

1. Add a data table
2. Bring up the Table Layout dialog
3. In the paging tab select enable pagind and select display paging button
4. Now delete the daa table
5. Note lots of squiggly red lines in the page source - lines left behind after
   data table is removed
xxx@xxxx 2004-05-24
xxx@xxxx 2004-05-24

Insync only removes its own code that references a deleted component, not user 
code. In this case, the code is component provided. So, this code should be 
cleaned up by the corresponding LiveBeanInfo that inserted it in the first 
xxx@xxxx 2004-05-24

Requesting bug be deferred. See comments.
xxx@xxxx 2004-05-26

I was requested to evaluate this further - and all that we told Matt before is 
true ;-)  We have to defer this until 1.1 - we will add a hook into Beans2 to 
allow this cleanup.  It doesn't exist today for this case with such a deeply 
nested compound component...
xxx@xxxx 2004-06-01

I am also making this an RFE - as it really is a feature request at this 
xxx@xxxx 2004-06-02

Evaluation (Entry 2):
Joe Silber xxx@xxxx has asked about this bug. I am requesting it be reassessed 
by Gregory Murphy, since it may point to a limitation in the designtime API. 
So reassigning to him.

My guess is that if this is not a case for augmenting the designtime API, then 
it would be deemed an insync bug if insync is not fulfilling its obligation 
for beanDeletedCleanup. In any case, unless there's a larger implication, this 
is probably a candidate for "will not fix," since it is a relatively minor bug 
in the old ri component set.

Evaluation (Entry 3):
This scenario is much easier to reproduce than the reported test case 
indicates: just drop a button, double click to add an action event handler, 
then delete the button. Insync does not remove the action handler method. This 
is probably a duplicate; passing to insync.

Remove the code manually.