Closed Bug 161266 Opened 23 years ago Closed 19 years ago

java.lang.UnsatisfiedLinkError: getBrowserType in External Authering Interface (EAI)

Categories

(Core Graveyard :: Java: OJI, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: hendri, Assigned: joe.chou)

References

()

Details

Attachments

(3 files)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1a) Gecko/20020611 BuildID: 2002061104 Using Cosmoplayer 2.1.1 as plugin for VRML in Mozilla 1.x and Netscape 6.x My Java Plugin is: Java(TM) Plug-in: Version 1.4.0_01 Using JRE version 1.4.0_01-ea Java HotSpot(TM) Client VM I always get the following error. java.lang.UnsatisfiedLinkError: getBrowserType at vrml.cosmo.Browser.getBrowserType(Native Method) at vrml.external.Browser.getBrowser(Browser.java) at vrml.external.Browser.getBrowser(Browser.java) In java file Browser.getBrowser() is called to contact the VRML-plugin with JVM using LiveConnect. In Netscape 3.x and 4.x and Internet Explorer this is done by EAI (External Authoring Interface) to connect Java VM with the VRML world, so events can be thrown and catched from this VRML world and the VR world can be changed on runtime. It is not a bug in Cosmoplayer because other Plugins (Cortona for example, http://www.parallelgraphics.com) do have the same problem. Reproducible: Always Steps to Reproduce: 1. install CosmoPlayer as VRML-Plugin 2. install Java Plugin 3. Load URL mentioned above and see the linkage error. Actual Results: I get an linkage error in the Java Console: java.lang.UnsatisfiedLinkError: getBrowserType at vrml.cosmo.Browser.getBrowserType(Native Method) at vrml.external.Browser.getBrowser(Browser.java) at vrml.external.Browser.getBrowser(Browser.java) Because the Java program can't make a connection to the VR world a 'dead' VR world appears. No communication between Java and VR-plugin is possible. Expected Results: Return a 'pointer' to the Browser Component which is able to use the getBrowserType. The other way to make a Browser connection using LiveConnect is using JSObject: class myApplet extends Applet { ... JSObject win = JSObject.getWindow(this); JSObject emb = (JSObject) win.getMember("embeds"); Browser browser = (Browser) emb.getSlot(0); } This is alos not working. The getSlot call returns an Exception. Also this code is Browser depended (because JSObject is Netscape code) and not preferable.
the Plugin API has changed and LiveConnect doesn't exist any more. I'm not shure, if the Cosmo Plugin is aware or this...
Reassigning to OJI, particulary for the reporter's last remark: > The other way to make a Browser connection using LiveConnect > is using JSObject: > class myApplet extends Applet { > ... > JSObject win = JSObject.getWindow(this); > JSObject emb = (JSObject) win.getMember("embeds"); > Browser browser = (Browser) emb.getSlot(0); > } > This is also not working. The getSlot call returns an Exception. > Also this code is Browser depended (because JSObject is Netscape code) > and not preferable. That applet code should work, shouldn't it?
Assignee: rogerl → joe.chou
Component: Live Connect → OJI
QA Contact: pschwartau → pmac
No. There is a ClassCastException: sun.plugin.navig5.JSObject As Attchements a give you three files: - test.wrl - test.html - Test.java The wrl is a very little VRML file. The html file starts the VRML plugin and the Java Class file. Inside the Java file is uncommented code which gives the Browser.getBrowser() error.
Attached file Simple vrml file
Attached file Simple Java file
Please compile with javaws.jar
Reporter, could you try this on a more recent build of mozilla (1.1, 1.2 etc.) and JRE (1.4.1rc, available for downloading from java.sun.com/j2se), and see what happens?
I've tried your suggestion. Same errors. Mozilla 1.2a Java 1.4.1.
QA Contact: pmac → petersen
Mozilla also does not respond correctly to the ASP command: client=Server.CreateObject("MSWC.BrowserType"), must be the same problem, I guess. client.browser returns: Default client.cookies returns: false (and that just can't be true!) using IIS 5.1 on WinXP using Mozilla 1.3 on WinXP and on Win98
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: