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.
Bugtraq number: 4615397 Bugtraq author: vijaya.mummaneni@sun.com Tested Env : Build011216, Win2000 FFJ automatically mounts the jar files that are in WEB_INF/lib direcotry. I have two jar files parser.xml and jaxp.jar files that came with petstore1.1.2. When I expanded the jar file and start navigating the sub directories of these jar files I see the exception. The exception picture is in the attachment.
Created attachment 4012 [details] error
This is not a jarpackager issue. The default is not within the jarpackager code. Additionally a full stack dump is needed. the picture send is cropped and of little value as the line numbers are not shown.
Roger, why do you think that this bug belongs to core? From the picture of the exceptions it's clear that the exc happened in the text module
I think that this is not a problem of the text module. The cause of the exception is the following: 1) The text module loader is trying to get an attribute named "org.netbeans.modules.text.IsTextFile" from the fileobject that is located in jar filesystem. As there are no restrictions on the name of the attribute in the FileSystem API, this is pretty fine. 2) The JarFileSystem implementation delegates getting of the fileobject attribute to getting of the attribute from the manifest. The manifest creates Attributes.Name(String attrName) but there are restrictions that prohibit having "." in the attribute name and the IAE is thrown. IMHO I think that JFS could either ignore such attribute or do some kind of name mangling so that the name is valid from the Attributes point of view. Reassigning to openide.
Fixed in release33 (JarFileSystem 1.60.2.3). Method readAttriubute catches IllegalArgumentException and return null if not permitted attribute-name appears (I also intend to add new test to extend test suite).
verified
Also cf. JDK docs bug: 4623202 (should show up on JDC shortly)
Resolved for 3.4.x or earlier, no new info since then -> closing.