Created attachment 1008704 [details] output in window when I follow the url under steps to reproduce Description of problem: unable to run jnlp Version-Release number of selected component (if applicable): IcedTea-Web Plugin (using IcedTea-Web 1.5.2 (fedora-0.fc21-x86_64)) How reproducible: First problem was that firefox didn't know what to do with type application/x-java-jnlp-file. I eventually figured out (hope I was right) to navigate to /etc/alternatives/javaws. Now I get the failure in the attachment. Steps to Reproduce: point your browser at https://www.sonario.com/~alpha/sonario/com.sonario/Releases/release150329/direct\ or_sonario_com-mysql.jnlp Actual results: see attachment Expected results: This does work on windows using oracle java 8
For some reason ITW thinks this is by-jnlp signed app. But no jnlp is presented inside signed jars.
I don't understand what by-jnlp means, but I see the jnlp in director_sonario_com-mysql2.jar (which is signed) under jnlp-inf/application.jnlp Isn't that the way it's supposed to be?
(please scratch comment #1) ok. So . Yes, the application is isgned, and yes have vlaid siganture via internal JNLP All jnlp files are really same, but the jnlp file contains ... <application-desc name="Strategic Organization & Talent Development Technology" main-class="Sonario" ... Which really is not valid xml. The vendor should be urged to use & instead of &. however, the initila JNLP shpould not be parsed at all, which it is. Tahts because ITW is using tagsoup to clean input (try to remove tagsoup, and app willnot even downlaod) So actually this uncvoered bug in itw itself - the file used as tempalte, si not cleaned via tagsoup. I will enable this for 1.6, but becasue of underlying issue, this bug should be correctly closed as not-a-bug. or "corrupted input". Still I will use it to track the issue for 1.6 (which should go out in aprox month)
Hi Donald, nice midair collision ;)
Ok. I have poatchready, and it works - the template now can be sanitized. However, I'mnot able to test the app, as it is complaing about not existing javafx. Is it expected? Do you have some workaround for it?
If you wont to play with self build ITW, here is ooriginal patch for head - http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2015-April/031397.html
So is the only problem the ampersand ? It would be nice if there were some way to tell what's wrong with the xml. In fact it would be nice if the program that can't parse it would tell you. At very least it could report that there is some problem with the xml.
One other thing - fx is supposed to be part of java 8. If you're using something earlier then another jar is needed.
ok. I had pushed the fix to head, and build icedtea-web-1.6.1.pre04 (release candidate1) for f22. Hope that it helps. If you will need additional file jar of java fx - feel free to modify your javaws "binary" (for itw it is only shell script) and aad the fx.jar behind tagsoup.jar.... Still - fix on calsspath with javafx should be somehow fixed for ITW. But its another story for now.
Ok. It did not let me sleep. http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2015-April/031461.html I posted alsopatch to support javafx by ITTW by default. Hopefully it will make it to 1.6 J.
Is this fix supposed to be available via yum update any time soon? I see an update for java-1.8.0-openjdk x86_64 1:1.8.0.40-25.b25.fc21 I don't see anything for IcedTea. Just getting the update above doesn't seem to allow me to run the app.