SWT Browser Problem on Vista - java

We're running Java Swing and are using an SWT bridge to get ahold of the SWT browser. Everything normally works just fine, but we have a problem on a Vista test machine. It worked fine until just a week ago or so. The call stack:
org.eclipse.swt.SWTError: No more handles
at org.eclipse.swt.SWT.error(SWT.java:3589)
at org.eclipse.swt.SWT.error(SWT.java:3481)
at org.eclipse.swt.SWT.error(SWT.java:3452)
at org.eclipse.swt.browser.IE.create(IE.java:184)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:109)
...
I have tried IE7 and IE8 through the SWT browser, but none is working (XULRunner is not applicable on our application since we need two browser instances).
XP, Windows7 and Vista is working on other machines, and I can't exclude something being correpted on this specific machine. We got some Windows updates close to when this error started happening, they seem related. It is a our only Vista test machine with a virtual screen, has there been any Windows updates for IE relating to virtual screens that could cause this? To me it looks like a likely target for security holes, so maybe that could be it?
I know this is looking for a needle in a haystack, but has anybody seen anything similar lately?

Edit: looking at the source, I see that the IE.create method swallows an exception to throw this error - I'd step into the WebSite constructor to try and figure out what's happening.

My solution is not to embed the SWTBrowser into our Swing application at all. (I've always hated web tech on desktop apps anyway. :)

Related

Java Intranet Applet not working in Internet Explorer 11

for days now I'm having a lot of issues of IE 11 with Java.
History
On my father's computer there's an Intranet Java app that works only with IE, not any other browser.
Until couple of days ago it worked almost perfect. I tried updating Java and since then it doesn't work with IE 11.
No Solution
I tried a lot Googling and looked for other peoples similar problems, none of the solutions people offered has worked for me.
I tried un-installing and re-installing many times. At first the Java was completely blocked, now I have installed an older version (Java 7) which works when I go to java.com and do the Verify Java Version.
However when I open the app (which opens through IE 11) I get this 404 message.
Other Browsers
In FireFox it actually opens the screen IE should open using Java, however the rest of the program is not compatible with FireFox so I am forced to use Java. But it shows that the problem is definitely in the hook of Java with IE but I can't figure out what it is.

Touch on JavaFX (Java 1.0.8-b123, VM 25.0-b70) on ARM

I programmed an application in Oracle’s NetBeans for deployment on a Raspberry Pi. The program itself works fine with the Runtime as specified in the title. To be exact, I have the jdk-8-oracle-arm-vfp-hflt.
However, when I touch the screen, the following message is given in console:
Jul 29, 2015 10:11:56 PM com.sun.glass.ui.lens.LensApplication nativeEventLoop
SEVERE: 4998 udevInput.c:1596 lens_input_pointerEvents_handleSync: malformed multi touch event - ignoring
I’ve already read, that there was a problem with the Lens framework and one would rather use Monocle, but I can’t figure out, how to include Monocle and drop Lens in NetBeans. (I am quite new to Java.)
Do you have an idea to solve this problem? I do want to use multi-touch later, if possible.
I have the exact same problem on my RPI2 with a Hanns-G Touchscreen, which is working fine in X, but not in the JavaFX application.
As you said, I tried to use monocle instead of lens. This itself is quite challanging. There are no ready-made and complete Monocle-Jars out in the internet. The only one I find was a "headless" version, which kind of works on my PI:
http://mvnrepository.com/artifact/org.jfxtras/openjfx-monocle/1.8.0_20
While running my JavaFX app with this monocle like this:
java -Dglass.platform=Monocle -Dmonocle.platform=Headless -Dprism.order=sw -jar myJar.jar
I starts and doesnt create those malformed multitouch events anymore. Drawback is: The GUI doesnt show up, because it is "headless". Not so funny...
Monocle also works with a none-headless mode (with a GUI starting up). But it seems, as if you have to build it on your own, as described here:
https://wiki.openjdk.java.net/display/OpenJFX/Monocle
Here my luck stopped. My linux skill is too low, to build it on my own. I started a bounty, so hopefully a skilled person will help us... Good luck! I also have a friend, that has the exact same setup as I do, and he claims, that he has working touch enabled JavaFX apps running. He will show me soon. I'll keep you updated.
I finally got it working!!! Unfortunately I cannot collect my own Bounty :-)
The solution for this problem in my environment was:
Simply start the application with sudo:
sudo java -jar myApp.jar
The device driver of my touchscreen seems to need access to certain etc files, that are only accessible by root or with the sudo command. Give it a try!

Oracle Forms running on java 6 Update 45

I have one program, I maintain, that was originally written in Oracle Forms 6i. A while ago I migrated it to 11g. Our users access this Oracle Forms program through their Internet Explorer browser on their Windows 7 machines.
The problem has been that the program only seems to run well for our users, when they have Java 6 Update 45, installed on their machines. Going to a newer version causes problems.
Today, I wanted to get this resolved, so I updated my PC to Java 8.31, and attempted to access my Oracle forms program using IE. (Thanks to Viewing oracle app and getting: java.lang.ClassNotFoundException: oracle.forms.engine.Main I was able to get the form running again in my web browser.)
When my form ran, I found the tab key wouldn't advance to the next field on the login dialogue box. But after I logged in the tab key worked. (The tab key initially not working is a small thing, but it has really annoyed some of our users.)
I then used several different forms. Some worked just fine, no problems. But then when I clicked a button, on one form, it would endlessly try to complete a request; to the point that I couldn't even close the web browser to stop it. (Finally I just used task manager to end my web browser’s process.) This seemed to go in line with what some of our users have reported: (when attempting to use the latest Java) that the Oracle forms application just stops working completely after a while.
Because of these issues our users want to keep Java 6 Update 45 on their machines. I know this is a major security hole, but I haven’t quite nailed down what the solution to it is.
Has anyone else had a similar issue? We're running Oracle Fusion Middleware 11; specifically Forms Services version 11.1.2.0.0
Thanks.
Well this may not be a question that needs answering after all.
I've done some more testing since asking this. Besides the login dialogue box (not responding, as it should, to the tab key) everything else works just as it should.
I still have one form that hangs; but that’s all (and it may be caused by something else). All my other forms seem to work just fine.
I talked with one of my co-workers, and I realized we really need to investigate and determine what version of Java our users really are using. They may not have used the most recent version of Java; which I used with success, today. Or some may be already on it; and that's why they aren't complaining.
At any rate more research, is needed on my part. Thanks to all who read this. If any of you have had similar experience in something like this, still feel welcome to answer/comment.

Java UI on macOS X Lion

I'm having a strange bug wich i suspect to be specific to either MacOS X Lion and/or Java VM implementation on this OS.
When a java app summons a secondary window like a dialog box, i'm often unable to interact with its content ie. click, use menus, etc.
At first i though my app was buggy but since i had developped it on windows (where it worked fine) and switched to mac. I though some weird swing setting was to blame and i had noticed on the console that a compatibility mode with cocoa was enabled when i launched my app.
But i encountered the same bug with eclipse itself (a well known java based ide) tough it does not always happen in it while it's all the time with my app.
I have browsed for this issue but found nothing. Meanwhile i found that there is an issue between oracle and apple about java. I downladed a java update specific to Lion but the bug is still here
My question is : have you encountered the same bug ? is it macos lion specific ? have you found a workaround ??
Thanks
Made some research. Eclipse seems to be the cause of the bug. More precisely SWT support in eclipse under MacOS environnement.
The bug is not present with netbeans.

Java swing components not displayed properly outside netbeans

I have developed a Java Swing application. When running the application in Netbeans IDE, everything works properly (see http://www.fkserv.ugent.be/vrg/tom_dierickx/Screenshot2.png for a screenshot).
After building the project to .jar and running it in command line, the application window appears but the components are not displayed properly (See http://www.fkserv.ugent.be/vrg/tom_dierickx/Screenshot1.png for a screenshot).
Does anyone have experienced this before and may have a solution to this problem?
As the thread points out, this seems to be a Ubuntu-related problem. I experienced no trouble when running the application on a windows system.
Some threads on the web contribute the defect to Compiz or Beryl. However, I never installed these graphic-tools. However, I ran a line of code I found on the net for uninstalling Compiz. It seemed that Compiz was installed by default. Unfortunately, the problem remains. Beryl doesn't seem to be installed.
The threads also note to add export AWT_TOOLKIT="MToolkit", but this doesn't seem to work either.
No runtime errors where generated on the command line.
Any suggestions?
After some testing, I came to following conclusions:
The application runs on Windows, but not on Ubuntu.
Some Swing applications run on Ubuntu, while others don't.
Hence it seems like the problem is due to one or a few Swing components which do not work in Ubuntu. I think it's best for now to avoid these components by testing what works and what does not.

Categories

Resources