I just successfully used jnpl with my client-bank software. Chromium
4.0.266.0 under
linux.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
Still not working Google chrome version 4.0.249.89 unknown (38071).
Google! Java isn't going away, fix this.
Chrome version 5.0.307.11 beta using Ubuntu Linux - same issue. Had to
publish a
message asking users of my site to not use Chrome if they want to use my
site
properly.
I can't imagine this being a complex bug to fix because a) it's easily
reproducible
and b) associating JWS with a specific mime-type/extension is, from an
outside
perspective, not too cumbersome.
Please fix this on OS X! It is REALLY annoying!
I would really appreciate if this could be fixed.
I guess I finally found out how to "fix" this, at least on Fedora 13
(credit goes to an answer on Fedora ML). It seems to be a GNOME bug after
all.
If you try to associate JNLP files to javaws by
right-click on the file > Open With > Another Application ... > javaws
and checking "Remember this application ...", it doesn't work (next time
you double-click the file it will open with gedit).
BUT if you set file association by
right-click > Permissions > Open With tab > javaws
it *DOES* work, file association sticks. If you open a JNLP file through
Chrome, it will work =)
My users are having a problem too! goto http://www.binfer.com/download and
click on the Web Launcher button, Chrome downloads the jnlp file and does
nothing. Many users assume the app doesn't work and abandon it. I am going
to advice my users NOT to use Chrome to run the app.
@aimran50 : I just tried your URL and, at least here on Fedora 13, the
modifications detailed on comment #40 made it work as expected (the JNLP
file was automatically executed by javaws).
@andre.ocosta does that really sound like a User friendly support for jnlp ?
This bug is annoying as hell, Chorme is basically not a java friendly
browser if they don't support auto opening of JNLP cross platform.
IT call:
User: I'm pressing the link and your app doesn't start.
Tech: What browser?
User: Chrom.
Tech: We don't support Chrom, Use another browser please.
End of story.
Please add application/x-java-jnlp-file to mimetypes supported by chrome.
I can't use cisco web start as it tests for mimetype :
<script type="text/javascript">
<!--
var appName = "";
var isWindowsOS = (navigator.userAgent.indexOf("Windows") >= 0);
var javawsInstalled = 0;
isIE = "false";
if (isWindowsOS) {
if (navigator.mimeTypes && navigator.mimeTypes.length) {
mimeEntry = navigator.mimeTypes['application/x-java-jnlp-file'];
if (mimeEntry) {
javawsInstalled = 1;
}
} else {
isIE = "true";
}
} else {
javawsInstalled = 1;
}
//-->
</script>
Using chrome 5.0.375.126 on Windows XP. JNLP files should launch, and
because they don't, this is a deal breaker. I have been using this browser
for a while now, and was ready to suggest a switch at work, but without
Java, I will not.
It can't be that hard. What happened to that "don't be evil" mission
statement?
It is more than a year this bug is reported, no action from Google! Is
Google moving away from developers?
Google has the same problem with both Java WebStart and Microsoft's
ClickOnce. Google Developers, if you read this: Java WebStart and
Microsoft ClickOnce are accepted standards. You must support these if
Chrome is to be a standards based browser. Otherwise, you're just being
anticompetitive. I say this as a neutral 3rd party ISV - I just want my
apps (both WebStart & ClickOnce) to be supported properly on all browsers.
The really sad thing about this bug is that there are people who really want
to fix it and get absolutely nowhere with some of the chromium developers. I
bought Visual Studio primarily so I could start compiling chromium on
Windows to work on this bug (as well as getting into Windows programming). I
started an initial debate with the people I was told to. I drew up a design
document, it was discussed - by all except the one person who seems to be
responsible for making the decision. Nearly a month has passed since he was
asked to give the go-ahead on or comment on the proposal, and nothing. It
seems there are only 1 or two people who can have the final say on anything
that impacts the UI, and they are either completely overloaded or completely
disinterested in helping the community at large and only work on the stuff
thats in front of them, instead of giving developers such as myself a bit of
leeway or encouragement to help them help make chromium a better product. I
find it quite sad really.
So for the myriad number of people that this affects, don't hold your
breath. Alternately, I may just go ahead and fix this on my own branch of
the code and I will post builds from that branch which people can either
use, or not, as they see fit.
Like someone else noted, I'm trying to use Google's own App Inventor in
Chrome and can't because of this issue. I switched to Chrome full time a
couple months back, but if you REALLY want me to use another browser, I'll
go back to Firefox. PLEASE FIX.
It doesn't work as expected on Linux, but it seems to be due to some weird
GNOME bug (see comment #40), at least on Fedora 13 and Ubuntu 10.04 (which
both use GNOME 2.30.x).
Also discovered the bug when trying to test App Inventor.
Yeap same as many above, Google App Inventor / Chrome will NOT be used
together by many people when other more popular browsers (firefox) work as
expected.
If you cant be bothered to fix it at least post a simple work around...
Should the app be opened standalone or just inside browser? You can easily
run it with "javaws file.jnlp" btw.
@phlogi1, we are application developers and Java Web Start is a platform
developed by Sun to distribute Java applications. All Java developers knows
how to run a Java WS app, but not the end users.
@tgarancsi, works like a charm, thanks! Just download the file and once it
has downloaded, click the arrow next to it (on the download bar at the
bottom) and choose "Always open files of this type". Ran into this when
trying to get App Inventor setup.
@tgarancsi, works like a charm, thanks! Just download the file and once it
has downloaded, click the arrow next to it (on the download bar at the
bottom) and choose "Always open files of this type". Pretty easy once you
know how, but it can be a pain in the butt if you don't know how. Should be
a little easier to figure out though. Ran into this when trying to get App
Inventor setup.
I am also unable to get Chrome on linux to launch Curl applets ( Curl as in
www.curl.com and not cURL)
Curl applets had been an alternative to Gears and JavaFX - but used mostly
in a few corp's in Japan and discretely elsewhere in some large corp's (
clients of Thomson Reuters Tax div GRC customers via acquisition of
paisley.com of MN, USA)
Curl in Japan (curlap.com) has work underway on a Java ORB so this issue in
Chrome on linux is annoying ... - the issue is Linux only TTBOMK
Curl in banking is about as well-kept a secret as VW Smalltalk in banking
prior to some chatter from NY. Smalltalk was big at a telco with some
mobile over-charging issues - it will be amusing if those came from an app
that had replaced Smalltalk ...
Hope these bugs get fixed before Chrome leaves beta ...
This is an issue with Google Chrome 6.0.472.53. Some of our equipment
produces URLs that look like this:
http://.../viewer.jnlp(10.0.3.223@0@idrac-HV00LM1,+PowerEdge+R610,+User-root@1287580593721)
Selecting "Always open files of this type" does nothing because that
appears to be a tool for mapping file extensions. These documents (and
really everything else) need to be identified by MIME type, not file
extension.
I have a feeling that with Oracle suing Google, this probably won't get
fixed any time soon or at all now.
http://news.cnet.com/8301-30684_3-20013546-265.html
The way I see it, this behavior isn't a Chrome bug, it's rooted in the fact
the Chrome consciously does not manage its own set of file extension ->
launcher application associations. Instead, it relies on the operating
system / desktop environment to provide those associations for it. This
means that you have to configure your system (e.g. Windows or Gnome) such
that it opens .jnlp files with javaws (the webstart launcher). From then
on, Chrome will use that setting and open .jnlp files with javaws (after
clicking "Open" in the download bar, or automatically after you
check "Always open files of this type" there). This is the way to "fix"
this issue. Google cannot really "fix" this themselves because Chrome
deliberately doesn't contain any code that makes (configurable) decisions
on what application to use to run what downloaded files -- they
deliberately use the OS settings for that.
@olaf.klischat, have you tried downloading a jnlp file (where a file
association is already there) before making this comment?
mis webos
@sunilmnambiar, yes I have. I use Xubuntu (xfce under Ubuntu 9.10), and I
had to configure the association once in the system (I did it from the file
manager I think, but I don't remember for sure, it's been too long). Chrome
has been opening .jnlp in Webstart automatically ever since.
For Windows users see http://www.petenetlive.com/KB/Article/0000354.htm
Pete
Having the same issue on Windows 7/Chrome beta release - the option in the
drop down is greyed out for me although starting the app by double-clicking
the jnlp file works - would be a lot more convenient to start directly from
Chrome
It does not work on Linux :( If you don't fix this bug, I will advise my
users to go back to Firefox!!!! I'm fed up! I have just paid to upload my
game and now I'm stuck.
I think that I have found a bug fix. I have looked at the source code of
Chromium, especially the MIME handling and there is only one line to add to
fix it :) I will try to commit it. Java rocks, long life to Java and to
free open source softwares!!
Please find enclosed the file /trunk/src/net/base/mime_util.cc that I have
modified to try fixing this bug. application/x-java-jnlp-file was never
returned for a jnlp file, it was not returned by the platform-specific mime
type handler and it was not returned by the platform-agnostic mime type
handler. As it is not a platform-specific mime type, it has to be put in
the platform-agnostic mime type handler. I'm not sure it fixes completely
this bug BUT it improves the situation on Linux as the correct mime type is
returned to the application used to open a JNLP file, for example
Konqueror. Please use it as soon as possible.
Attachments:
mime_util.cc 22.4 KB
Issue 66860 has been merged into this issue.
Issue 66993 has been merged into this issue.
The workaround (i.e. Always open file) NOW works UNTIL you get to 100
starts of the same application. This didn't work when I first raised the
bug report. Testing the Draw app from
http://java.sun.com/javase/technologies/desktop/javawebstart/demos-nojavascript.html
today (OSX 10.6.5, Chrome 8.0.552.231) I end up with "draw (1..100).jnlp"
files in my Download directory. The next attempt I get the dialog to ask me
where I want to save the file.
craigday, this workaround does not work on Linux without my fix.
Thanks. Some file browsers used by default on Mac OS X and Windows may
detect the file type without using the mime type or they do not take into
account the wrong mime type sent by Chrome/Chromium, that is why your
workaround works on some platforms but not on some Linux distros. My fix
only sends the right mime type for Java Web Start applications.
What happens if the file is not a .jnlp extension?
It does not work if I run a .asp file with a jnlp mime-type.
This has stopped working on the 8.0.552.215 update of chrome.
iparraa, I have the same problem with a .php file that forces the JNLP mime
type but I didn't know it had worked in the past. Thank you very much for
this piece of information. However, I don't advise you to use php or asp to
do this in the future as my fix only concerns files with a .jnlp extension.
I do my best. Rather write a bigger JNLP file containing more conditions
concerning the OS, the architecture, etc...
Yes, in earlier versions, Chrome download the file as a .jnlp file and let
the user execute the file.
In the last version, Chrome download the .asp file and open it as a text
file.
Making a bigger jnlp file is not a solution (at least for me), because I
generate a jnlp code with different parameters created on the web before
launching the jnlp.
My 'temporal solution' is renaming the .asp file to .jnlp but this is not a
solution for the final users, which are using now IE and FF.
Firefox renames the file automatically when detects the jnlp mime type and
let you launch it with Java Web Start.
On the other hand, IE launches Java Web Start directly without prompt
anything to the user.
What is the status of this ? Why you guys making it so complicated ? Jnlp
is a method of easy package deployment to reduce the hell of package mess.
- Why dont you guys just fix this ?
- How long Java will be suffering hate and hate and hate ???
- Why not put bug for Flash player and Silverlight ?
Comment #106 on issue 10877 by scarybea...@gmail.com: Chrome does not
launch Java automatically for JNLP resources
http://code.google.com/p/chromium/issues/detail?id=10877
Ok -- on trunk, it's now possible to set JNLP to "auto-open" and it will
bypass the warning iff a user gesture (such as a button click) caused the
JNLP to be served.
Put another way, you can set JNLP to "auto-open", and the John Travoltage
demo app works with just the button click:
http://phet.colorado.edu/simulations/sims.php?sim=John_Travoltage
This will filter into Chrome dev channel in a couple of weeks and then
onwards to stable!
This is good news, and will be handy, however I feel the real fix is to
have the ability built into Chrome preferences , that allows you to
associate applications to specific file types, like you can do in Firefox.
Not sure if this has been suggested or is being worked on, but fixing these
one at a time seems to be a waste of developer time, in my opinion.
Thank you for the fix. A lot of final users will be happy with your time.
Thanks!
@swcodfather: this is not a one-off fix. It applies to any "dangerous" file
type for which a MIME type handler is registered at the system level.
Thanks for the update chaps, I will follow the bug report 55566 and help
with testing when it is available.
I have the exact same problem under Windows 7 64bit, Chrome 9.0.597.98.
What I would like to point out is that the steps listed above by a few
people to click the down arrow and tell Chrome to 'always open files of
this type' does not work. It does absolutely nothing. I tried re-starting
Chrome and same thing. It automatically downloads but then does absolutely
nothing. I am using this to try and access my DRAC (Dell Remote Access
Console) on a server remotely. Under IE 7,8,9 works without issue. Under
Chrome, it just downloads the file and sits there. It would be nice to just
have this work out of the box or to at least provide end users with a
simple warning if you do not want this on by default. But at least don't
make it hard to have this work seamlessly.
BTW, I had the same problem on my Mac and there I had to follow some other
instructions and actually register the file association with an executable
in a directory. After that it worked like a charm. But on Windows, it does
not work for me.
EJK
The fix that is currently used does not change anything in the MIME type,
mine would be complementary, wouldn't it?
Exactly the same problem here: Chrome 10.0.648.127, Mint Linux 9 (Isadora)
x86.
Same problem. Chrome 10.0.648.133/Vista x86.
There is a workaround -- after enabling auto-open, when the JNLP file is
being downloaded, you will see it at the left bottom with "SAVE"
or "DISCARD", click "SAVE" then it will auto launch. Hope this helps.
but how do I set it to auto-save AND Open automatically? I remember it
works OK before the recent upgrade..Pls advice.
I am still having this problem.
This is a very important issue because when I use trade, I need to launch
jnlp.
I just verified that it didn't auto launch my jnlp after clicking it in dev
chrome 11. This should ideally work just like an applet where the menu
above pops up and asks if you want to run java application. My concern is
that it still is dumping the jnlp to Downloads and is numbering it
file(1).jnlp, file(2).jnlp, etc. which will continue to take up space and
never get cleaned up as it is not going to the temp directory and not
getting cleaned up once the browser is closed. I understand that customers
can set auto-open of jnlp, but that is not what I'd like to happen.
Attachments:
java plugin image.jpg 161 KB
Attachments:
java plugin image.jpg 155 KB
google, i thought you didn't suck.
I haven't checked that with Google Chrome 11.
Maybe James Gosling can fix it for us now.
Kenneth Bradley Russell and James Gosling are able to fix this bug but the
problem does not rely in any Java source code as Chrome is written in C++.
However, the fix already used in Chrome 10 works even though some people do
not like its behavior and I provided another fix. If the code has not been
deeply restructured, a new fix is not really necessary, otherwise I will
give it a quick look.
This bug should not be marked as fixed.
BTW it is possible to achieve desired behavior by writing NPAPI plugin
(there are download managers that integrate with Chrome this way).
Unfortunately sun/oracle never really cared. Even their Firefox integration
is rather bad, yet Microsoft managed to integrate .NET ClickOnce properly.
Below ASP code works fine within IE & Firefox
Chrome just save the target ASP file !!
Please fix it, no workarounds
Pedro
<%@ language="VBSCRIPT" codepage="1252" %>
<%
Response.ContentType="application/x-java-jnlp-file"
Response.Write("<?xml version=""1.0"" encoding=""ISO-8859-1""?>")
Response.Write("<jnlp spec=""1.5+"" codebase=""http://www.SERVER.com/""
href=""file.jnlp"">")
...
Response.Write("</jnlp>")
%>
Hi guys,
you need to set JNLP files to auto-open. To do this:
1.) Download a JNLP file
2.) In the download bar, right-click the item
3.) Choose "Always open this type of file"
After that, this should work.
No, it doesn't work. If you do that then file is still downloaded to you
Downloads directory.
@thakis I don't think it is expectable behavior for jnlp where the user has
to select open or auto-open. Most users do not even know what a jnlp file
is or what to do with it. For example, nobody expects to open a file when
you launch an adobe air program. Here is an example. http://chessjam.com/
clicking install does not prompt you to save a file to open. It just
launches the air installer. I believe the same thing should happen for the
jnlp. All the other browsers perform in such a way. If google is worried
about launching something harmful then it should probably display something
like what I suggested in comment 123.
@mwisnicki I don't agree with you, Firefox integration of the plugin 2 of
J2SE 1.6 is excellent, there had been numerous problems with the plugin 1
but these problems did not affect Java Web Start as far as I know. .NET
ClickOnce works only on a single family of operating system, you cannot
compare this thing with Java Web Start. Can you tell me which version of
Chrome you use please?
@thakis It works for me. However, I agree with the previous comment. The
treatment of Java in Chrome is unfair, I see the (bonus) dangerous file
warning whereas there is already the scary warning of Java Web Start for
signed applications requiring some authorizations. If you want to
discourage the final users from launching Java applications, keep the same
behavior :(
@supag The default scary warnings of Java are enough, don't they? On which
operating system did you try Chrome 11?
Please, do you know why chrome is not handling "ContentType" (last tested
version 10.0.648.204) ?
See comments #130, #102
@goues...
It's certainly less than excellent (unlike ClickOnce). Firefox basically
treats JNLP exactly the same way as Chrome except it downloads this file to
$TMP and I already mentioned that in comment 73. Such treatment causes JNLP
files to not work if codebase is not hardcoded into them, yet codebase is
optional according to jnlp documentation.
That ClickOnce works only on windows does not really matter as its Firefox
plugin is pure javascript and very simple, it just catches download of
clickonce file and passes the url to clickonce launcher. With 3 simple
changes it could be used for JNLP.
Anyway this is mostly Oracle's problem. They can easily provide working
WebStart solution for Chrome and Firefox if they want. Instead they (and
Sun before them) choose to ignore bugs and other deficiencies of WebStart.
In fact they don't even accept such bugs into their bug system (which is
moderated).
I'm using Chrome 11 if you really need to know.
Oh and one more thing. There is a javascript jnlp deployment script which
you are supposed to use at
http://download.oracle.com/javase/tutorial/deployment/webstart/deploying.html,
or more precisely http://www.java.com/js/deployJava.js.
Unfortunately it uses 'application/java-deployment-toolkit' mime type
handled by special deployment plugin 'npdeployJava1.dll' that:
1. is not registered with Chrome
2. even though it's present in Firefox it does not seem to work there
And webstart deployment toolkit does not work by design ;)
From http://java.com/js/deployJava.txt:
launchWebStartApplication: function(jnlp) {
// This methos is disabled for the time being
return false;
},
Been that way since forever. Typical shit like you would expect from Sun.
Under XUbuntu Linux (with both Thunar and Nautilus properly opening
the .jnlp files), this still does not work under Google Chrome version
13.0.761.0 dev.
I'm noticing that it's silently downloading the file to my Downloads
folder, as mentioned in comment 132.
@thakis ~ your three step solution does not work because there is
no "always open" option on a right-click. I get several "open link in"
options as well as "save as", "copy", "inspect" and "search in" wikipedia
and dictionary. Your solution seems to be specific to your operating
system, because the option you recommend does not exist in Mac OS.
Another vote for Chrome not dealing with JNLP well. Out of the box, I
shouldn't have to download it and then manage settings in any way. If
anything, Chrome could have a pop-up confirming we want to run it, save it,
or cancel.
Good job Google for not fixing it!
Still a problem on 12.0.742.100
@efreak2004: forgive me for not running a random piece of Java on the
internet, but I had a quick look at the HTTP headers at least.
Does it not work if you select "always open files of this type" from the
Chrome download shelf?
I did what the community has suggested, so when I click on the test links
from java website- I get a nice splash screen from java showing me Java 6..
and then poof !!! there is no notepad file opened anywhere.
About Chrome gives Chrome version as 12.0.742.112 , I am running this on
Vista.
@ conspiracy theorists - I dont think Google can stoop so low as to
consciously disable/ prevent Java features from working just to get level
with Oracle.. so
Any Gurus/ Geeks who can help ?
It's extremely frustrating! The only thing, I can't use Chrome right now,
is accessing IP Console for our servers. This URL can not be open with
chrome:
https://managementhost/viewer.jnlp(managementhost@0@1310216803551)
It would be nice if you would support this, Every time I think I can move
to chrome the inability to kick off JNLP programs makes me move back to
firefox.
This issue is still occurring for me as well using Chromium 15.0.866.0
(Developer Build 98596 Windows)
not fixed yet. I opted for the run this file type always method which
seems to work for now
Having the same issues as "ptu...@gmail.com" with iDRAC. Windows see's
every .jnlp file as a unique extension due to the embedded info on the
file. Using IE for now to save time; would really love to see this resolved.
Still broken
14.0.835.202 m
jnlp file from Dell Drac works in Firefox, works in IE, just downloads in
Chrome.
@aha..., @ptu...: Could you switch over to issue 92846? That sounds like
it may be something real. @aha...: Can you say more about the windows
behavior? I'm not familiar with that, and that type of thing could easily
get in the way of auto-opening jnlp files, since we delegate the opening to
the OS.
15.0.874.102 m it's working fine, thank you!
Seems to be OS specific.
Doesn't work for me with 15.0.874.106 on Windows XP, however works on
Windows 7.
JNLP's do not auto launch on Mac OSX Lion Chrome 15.0.874.106. Confirmed
today.
I first noticed this behavior in the beta channel several weeks ago and
switched to stable because of it. Now it's in the stable channel.
Oh!! It has been solved on version 16 !!!
*
*
Oh! Finally in version 16.0.912.21 beta it has been solved!!
The mime-type is recognized and the browser open the jnlp file!
I'm using Chrome 16.0.912.41 beta on Linux and it doesn't open the jnlp
file....
K12 school system relies on .jnpl mime type. Pretty much if you don't fix
this, kids being home schooled can't run under chrome.
Still not fixed! How is this possible? This bug has been around since 2009!
I develop applications for biologists, and I use JWS for its simplicity.
Chrome takes that away.
Please fix!!
not fixed..
google are you actually listening to us ?