Talk:LiveConnect

Location of LiveConnect classes =

All of the documentation linked from here is out of date in at least one respect: where do you find the LiveConnect class definitions for compiling applets that refer to javascript? Sun's documentation describes it as being included in "JAWS.JAR", but this was last distributed with JDK1.3 AFAICT. The mozilla documentation suggests it should be in [path to mozilla installation]/Java/Classes/java40.jar, but this was last true for Netscape 4, I think.

Take a look at http://forum.java.sun.com/thread.jspa?threadID=5143832&messageID=9755591 IlariS (talk) 16:00, 8 July 2008 (UTC)

Anyone know how you actually use this API today? JulesH 20:25, 1 August 2006 (UTC)

Some examples can be found at http://java.sun.com/j2se/1.5.0/docs/guide/plugin/developer_guide/java_js.html and http://java.sun.com/j2se/1.5.0/docs/guide/plugin/developer_guide/js_java.html IlariS (talk) 16:00, 8 July 2008 (UTC)

Rhinohide has up-to-date instructions on this. Michael Allan 10:13, 30 May 2007 (UTC)

Someone might want to mention that Opera and Gecko-based browsers use this. Also, it isn't mentioned that this is also a communication method used by flash. Also, it isn't mentioned that Opera uses Java, and, if I recall correctly, IE uses ActiveX. --203.63.65.189 01:16, 9 August 2007 (UTC)

Requires own page

This page was merged into the NPAPI page, but that merge has not been relevant for many years now, as LiveConnect will mostly be used by users looking for a Java<->Javascript standard, not the outmoded browser API. It is more suitable for LiveConnect to link to the NPAPI documentation as a historical reference. Most of the information on the NPAPI page discusses the browser implementation, there is only a single line explaining that the JRE's redesigned support is also called LiveConnect, so it would be incorrect to call the NPAPI article more complete in that respect. So, on the basis that users are likely looking for current documentation on LiveConnect (which the NPAPI article does not provide as the primary LiveConnect link leads onwards to a broken link), and that it isn't the NPAPI article's purpose to document the JRE's support for javascript interoperability, I will revert the undo if there is no response in the next day or so.

On a side note, if someone has clearly added information, but the structure is disagreed with, just comment on the talk page like this, rather than making an undo without incorporating any new information (such as the JRE documentation link). — Preceding unsigned comment added by 194.74.171.34 (talk) 18:41, 10 June 2016 (UTC)

Hi.

Let's get over your point one by one:

1. "that merge has not been relevant for many years now". That merger didn't occur until a year ago! What "many years" are you talking about?
2. "LiveConnect will mostly be used by users looking for a Java<->Javascript standard". It does not matter. The criteria for having an article in Wikipedia is notability, not any of the things you said. We don't even have contents here, let alone notability. If you have access to content and source, please consider proving the potential for the expansion first by contributing to the existing location. We can unmerge at any time.
3. "I will revert the undo if there is no response in the next day or so". That would be a very rude thing to do, called edit warring. We have administrators who would lock pages to prevent any edit in them, if edit warring is observed. You must understand that even one reversion of your contribution would mean that there is opposition to it. Your contribution was a very poor one and this discussion is unlikely to be seen by many people anyway. (You should consider either publicizing it, or better yet, prove that there is ground for a reversion of the merger by adding well-referenced contents to the existing location.)

Best regards,

Codename Lisa (talk) 09:39, 12 June 2016 (UTC)