-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to launch a jnlp file #45
Comments
Hello jsa34, There are several exceptions pasted but most probably the cause is that you search for frame with title Oracle Forms:
Note that ATS is using FEST-Swing library (org.fest.swing package, https://github.com/alexruiz/fest-swing-1.x) which is not recently updated. Also we have not tested with with applets so it might not be compatible. Hope that helps! |
Yes - I could see this, however I have not set the expected window title - it seems to be self-derived when instantiating the SwingDriver |
The windows title searched comes from the title defined in the JNLP file. |
Ah - Apologies, I really should have looked at the source... I was just going by the possible constructors, and it looks like it's just missing a constructor for setting the window title when setting the app type as JNLP. I have done this by creating a custom class for instantiating the SwingDriver:
But, when I try and use the inspector, it returns: CustomSwingDriver cannot be cast to com.axway.ats.uiengine.internal.driver.SwingDriverInternal |
Hello, |
That's all I have:
Custom constructor used:
Usage:
|
I've raised a PR for the SwingDriver constructors that should resolve this (the ability to set the window title to something other than the default derived from the JNLP file) |
Issue: When trying to start a JNLP file (launching), I come across the following issue:
The JNLP is of type Oracle Forms: https://oracle-base.com/articles/11g/oracle-forms-11g-and-java-web-start
The JNLP file retrieved as a local file using:
SwingDriver.getSwingDriver("file:///C:/Users/test/Downloads/frmservlet.jnlp", true);
This then leads to...
The text was updated successfully, but these errors were encountered: