You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I managed to launch the .jnlp application using Robot Framework with Remote Swing Library in which RemoteSwingLibrary 2.2.4 (which uses SwingLibrary 1.9.9 (supports Java version older than 8 as the .jnlp app uses Java SE 6). There's no problem with the application launch, everything works fine. But this internal error means SwingLibrary doesn't work with the .jnlp app.
Here's my environment:
OS:
Windows 10, 64-Bit
Java:
java version "1.8.0_271"
Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)
Robot Framework:
Robot Framework 3.2.2 (Python 3.7.9 on win32)
JNLP Application:
Java 6 SE
RemoteSwingLibrary:
RemoteSwingLibrary 1.9.9
The text was updated successfully, but these errors were encountered:
Hi @ndsulit ,
I also need to automate jnlp application with Robot framework and RemoteSwingLibrary. But i not able to launch the application using start application keyword. Kindly help me to solve this problem.
I am using windows 11 machine.
Python version - 3.12.1
RemoteSwingLibrary-2.3.2
jnlp application java version - 1.8.351
I managed to launch the .jnlp application using Robot Framework with Remote Swing Library in which RemoteSwingLibrary 2.2.4 (which uses SwingLibrary 1.9.9 (supports Java version older than 8 as the .jnlp app uses Java SE 6). There's no problem with the application launch, everything works fine. But this internal error means SwingLibrary doesn't work with the .jnlp app.
Here's my environment:
OS:
Windows 10, 64-Bit
Java:
java version "1.8.0_271"
Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)
Robot Framework:
Robot Framework 3.2.2 (Python 3.7.9 on win32)
JNLP Application:
Java 6 SE
RemoteSwingLibrary:
RemoteSwingLibrary 1.9.9
The text was updated successfully, but these errors were encountered: