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 161238 - jnlp extension element support broken(?)
Summary: jnlp extension element support broken(?)
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Java Webstart (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Somol
URL:
Keywords:
: 187682 (view as bug list)
Depends on:
Blocks: 212668
  Show dependency tree
 
Reported: 2009-03-26 11:49 UTC by marcopar
Modified: 2012-05-23 09:36 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
A NB simple project that produces the error (3.34 MB, application/octet-stream)
2010-06-17 21:25 UTC, juliosergio
Details

Note You need to log in before you can comment on or make changes to this bug.
Description marcopar 2009-03-26 11:49:51 UTC
I've enabled java web start and i've also customised the master-application.jnlp to add a nativelib.
I've added a library to my project, jhall.jar (JavaHelp), this jar appears to be signed and since i sign my application
as well this jar should be added to its own jnlp and treated as an extension otherwise the application won't start.

The IDE appears to recognize that that jar has to be treated specially and creates an additional jnlp for it but in the
main jnlp the jar is added normally with the "jar" element while an "extension" element is never used.

A workaround i can see if this bug is confirmed is repacking the signed jar in an unsigned jar but this can lead to
license violations.
Otherwise i need to remember to manually edit the generated jnlp to fix it every time i make a release.
Comment 1 Antonin Nebuzelsky 2010-01-11 04:29:24 UTC
Changing the default component owner to tzezula.
Comment 2 Tomas Zezula 2010-06-17 21:12:53 UTC
*** Bug 187682 has been marked as a duplicate of this bug. ***
Comment 3 juliosergio 2010-06-17 21:25:47 UTC
Created attachment 100184 [details]
A NB simple project that produces the error

I detected the same bug, and the issue was marked as duplicate. So I'm attaching the NB project that produces the error.
Comment 4 Jesse Glick 2012-05-18 15:17:57 UTC
"Version" should be left untouched, or at most moved backwards, unless its original value was mistaken - this is not thought to be a regression in 7.2.
Comment 5 Petr Somol 2012-05-22 12:22:23 UTC
fixed issue 161238 and issue 212668 in jetmain:
http://hg.netbeans.org/jet-main/rev/4525d183679f

The fix repairs faulty jnlp external component generation and referencing, and improves detection of dependent JARs signed by a different signer. Now if signing is on, dependent JARs are treated as follows: the unsigned ones are signed and referred to by <jar> jnlp element, those signed by a different signer (than that used to sign the main JAR) get external jnlp components and are referred to by <extension> jnlp element, and those signed by a signer of equal name as the main JAR are referred to by <jar> element. In case of self-signing each generated signer used to be named "nb-jws" before the fix, what led to problems with recognizing the need to use external jnlp components instead of direct <jar> reference. Now self-signing generates a signer name dependent on the name of the project.
Comment 6 Quality Engineering 2012-05-23 09:36:51 UTC
Integrated into 'main-golden', will be available in build *201205230300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/4525d183679f
User: Petr Somol <psomol@netbeans.org>
Log: #161238 and #212668 correct external jnlp components for differently signed jars