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 6029 - New From Template on group of files opens only one file in editor.
Summary: New From Template on group of files opens only one file in editor.
Status: CLOSED FIXED
Alias: None
Product: utilities
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P4 normal (vote)
Assignee: Tomas Pavek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-03-24 00:41 UTC by L Martinek
Modified: 2003-07-01 15:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Jaroslav Tulach 2000-06-28 15:58:59 UTC 
Can be changed by assigning special TemplateWizard.Iterator to the group
template which will return more objects from its "instantiate" method.
Comment 1 Marek Grummich 2000-07-25 09:18:59 UTC 
Priority is changed to P4 (normal).
Comment 2 L Martinek 2000-08-18 09:24:59 UTC 
Will it be fixed or not?
Comment 3 Tomas Pavek 2000-08-18 09:55:59 UTC 
It was fixed in the open source trunk only.
Comment 4 Jesse Glick 2000-10-19 10:48:59 UTC 
There is an interesting situation with this in the apisupport module. I have one
*.group file that has the new GroupShadow$GroupTemplateIterator set on it (I
guess because I marked it as template after your fix; the other *.group files do
not have this attribute). So now using this module:

- In stable30, every group opens only one file (the attribute is unrecognized).
OK.

- In boston, at startup with -Dnetbeans.debug.exceptions=true, a
ClassNotFoundException is printed to console (safely caught by
DefaultAttributes) as it tries to load the (nonexistent) iterator. Every group
opens only with one file.

- In the trunk, this one *.group opens correctly with all members, and others
open only with one file.

Is it safe to make this fix in Boston? If you do I will apply it to all *.group
in apisupport. In any case, it is not very important because nothing is really
broken.

Alternately, is it possible for GroupShadow in its constructor to check for
templateWizardAttr attribute and set it to GroupTemplateIterator if it was unset
(instead of in updateSheet as it currently is, which doesn't seem to work
reliably)? This would eliminate the need to have the attribute set in
templates.jar in the module itself; it would be set at runtime in builds that
support the iterator.
Comment 5 Tomas Pavek 2000-10-19 14:55:59 UTC 
I've slightly fixed using the GroupTemplateIterator - now it is attached to
GroupShadow when dataobject is created (and is a template) or when it is
changed to be a template. If the group is not (and was not changed from) a
template, it has not GroupTemplateIterator attached.
I think it is possible to make this fix also in Boston, so I'll do it soon (and
send a notification).
Comment 6 Tomas Pavek 2000-10-20 09:59:59 UTC 
Fix transerred to boston.
Comment 7 Quality Engineering 2003-07-01 15:31:17 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.