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 7527 - jar objects without jarcontent could be recognized by a special loader
Summary: jar objects without jarcontent could be recognized by a special loader
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: jarpackager (show other bugs)
Version: 3.x
Hardware: All All
: P4 enhancement (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-08-29 17:12 UTC by Petr Jiricka
Modified: 2003-07-02 17:17 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 Petr Jiricka 2000-08-29 17:12:45 UTC 
Currently, JAR objects which do not have jarcontent file, are recognized
as "default" objects, for which no special actions are available. It is
understandable that indeed, the "main" action for jar files - Manage JAR - can
not be implemented if jarcontent is not available. However, some other actions
may make sense, such as "mount as filesystem" action.

There is a concrete example of a situation when this would be very useful: when
the user mounts a J2EE web module as a filesystem, it typically contains WEB-
INF/lib directory, which contains jar files used as libraries by this web
module. These libraries need to be in the classpath, which can be accomplished
by mounting them as filesystems. So the user would find the option to mount the
jar files useful.
Comment 1 Milos Kleint 2002-05-02 09:39:19 UTC 
implemented in main trunk. If you use a special dataloader for jars,
make sure it's loaded before
org.netbeans.modules.jarpackager.SimpleJardataLoader
Comment 2 Quality Engineering 2003-07-02 16:49:47 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verify
Comment 3 Quality Engineering 2003-07-02 17:17:31 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.