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 8660 - "Install New JavaBean" doesn't install first component
Summary: "Install New JavaBean" doesn't install first component
Status: CLOSED WONTFIX
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: Other Windows 95/98
: P4 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords:
: 14931 16365 17649 18961 (view as bug list)
Depends on:
Blocks:
 
Reported: 2000-11-30 05:21 UTC by rpmyers1
Modified: 2003-06-30 18:25 UTC (History)
0 users

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 rpmyers1 2000-11-30 05:21:27 UTC 
When using Tools->Install New JavaBean on Jars from BDK1.1, the first bean in
the manifest is not apparently seen. If only one bean is present, receive
the "Selected Jar file does not contain any JavaBeans Components" error box.
For other files, the top one in the manifest is not in the "select JavaBean"
dialog box.

Examples (all JARS from BDK1.1)
 buttons.jar:
Manifest:

Manifest-Version: 1.0
Name: sunw/demo/buttons/OurButton.class
Java-Bean: True
Created-By: 1.2.2 (Sun Microsystems Inc.)

Name: sunw/demo/buttons/OrangeButton.ser
Java-Bean: True

Name: sunw/demo/buttons/BlueButton.ser
Java-Bean: True

Name: sunw/demo/buttons/ExplicitButton.class
Java-Bean: True

Select JavaBeans Dialog:
OrangeButton
BlueButton
ExplicitButton

EventMonitor.jar
Manifest:
Manifest-Version: 1.0
Name: sunw/demo/encapsulatedEvents/EventMonitor.class
Java-Bean: True
Created-By: 1.2.2 (Sun Microsystems Inc.)

This generated the "Selected Jar file does not contain any JavaBeans
Components" error

This problem existed in several builds, all using J2SE 1.3
3.0 (Win 98)
3.1 Build 16 (Win 98)
Forte CE Update 2 (Win 2K)
Comment 1 Tomas Pavek 2000-12-20 17:12:59 UTC 
I think this is caused by one of these two things:
- the manifest is in wrong format, and/or
- there's a bug in java.util.jar.Manifest (which processes the manifest file).
It works if you add an empty line after first line "Manifest-Version: 1.0".
Each section for a bean must begin with "Name: ..." line; sections are
delimited by empty line. This is the way how Manifest class recognizes entries
in the file...
Comment 2 Tomas Pavek 2001-10-12 10:28:03 UTC 
*** Issue 16365 has been marked as a duplicate of this issue. ***
Comment 3 Tomas Pavek 2001-11-14 10:04:08 UTC 
*** Issue 17649 has been marked as a duplicate of this issue. ***
Comment 4 Tomas Pavek 2002-01-02 14:21:36 UTC 
*** Issue 18961 has been marked as a duplicate of this issue. ***
Comment 5 Tomas Pavek 2002-01-16 10:54:55 UTC 
*** Issue 14931 has been marked as a duplicate of this issue. ***
Comment 6 Quality Engineering 2003-06-30 18:20:24 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 7 Quality Engineering 2003-06-30 18:25:42 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.