Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I noticed that the launching of Java applets using deployJava.js seems to have stopped working on some Mac browsers. Safari and FF still work, but Opera and Chrome send the user to Java installation page, as if the plugin was not found.
Take for example this. If you click the launch button in Opera, it sends you to a Java installation page. Any ideas on how to fix this?
I ended up checking User-Agent HTTP header for “Opera” and in this case using standard tag. For any other browser I use deploy deployJava.js as currently served by Sun.
I know that there are modified versions of deployJava.js (e.g. this one used by Atlassian JIRA) which correctly start the applet in Opera instead of sending the user to Java installation page. But in my case, this approach caused ClassLoader issues (truncated classes) with Opera as I was using applets packaged into several jar files (main + 3rd party jars). had no such problems, even with Opera (which has buggy Java support as Sun claims).
Strangely, I had no issues with standard deployJava.js with Chrome (checked on Linux and Mac Snow Leopard).