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 179227 - Update tag not closed in jnlp file
Summary: Update tag not closed in jnlp file
Status: VERIFIED FIXED
Alias: None
Product: javafx
Classification: Unclassified
Component: Deployment (show other bugs)
Version: 6.x
Hardware: PC All
: P1 normal (vote)
Assignee: Adam Sotona
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-05 09:30 UTC by jgonca
Modified: 2010-02-04 03:09 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 jgonca 2010-01-05 09:30:07 UTC 
When building a javafx project, the jnlp files created have the update tag open. (<update check="background">)
When reading the jnlp files with a xml parser, it will throw a warning or an exception because the opening tag doesn't match the closing tag.

The solution simple because it is only needed to add a "/" before the ">".
<update check="background" />
Comment 1 Adam Sotona 2010-01-05 13:15:17 UTC 
I've already fixed this issue in JavaFX SDK / JavaFX Packager (which is responsible for deployment descriptors) three months ago.
See http://javafx-jira.kenai.com/browse/RT-4843
Unfortunately the latest released JavaFX SDK is older.
Comment 2 jgonca 2010-01-06 04:31:13 UTC 
(In reply to comment #1)
> I've already fixed this issue in JavaFX SDK / JavaFX Packager (which is
> responsible for deployment descriptors) three months ago.
> See http://javafx-jira.kenai.com/browse/RT-4843
> Unfortunately the latest released JavaFX SDK is older.

Oh, ok. 
I'll have to edit the file manually until the new JavaFX SDK comes out.

Thanks for your attention. :)
Comment 3 Adam Sotona 2010-01-06 04:36:57 UTC 
No, you don't have to, Java WebStart is simply ignoring the fact that is is an invalid XML so that is why we did not find it sooner.
I've experienced no impact on Java WebStart when the end slash is missing.
Comment 4 jgonca 2010-01-06 05:04:01 UTC 
(In reply to comment #3)
> No, you don't have to, Java WebStart is simply ignoring the fact that is is an
> invalid XML so that is why we did not find it sooner.
> I've experienced no impact on Java WebStart when the end slash is missing.

Me too, i've experienced no impact on Java Webstart. 

I only have the problem because I'm making an app in which I need to upload the contents of the dist folder to a webserver, in order to make the javafx app available on the web. After the upload, I need to change the codebase attribute to launch the javafx app correctly. And because the codebase depends on some parameters submitted in the upload form, I must change it and not the user.
Comment 5 Alexandr Scherbatiy 2010-02-04 03:09:24 UTC 
verified in NetBeans-JavaFX-Soma:  #142 with javafx-1.3dev