lena92
New Contributor
Joined 2 years ago
User Profile
User Widgets
Contributions
Error Message Installing ReadyAPI 3.51.0
Hey guys, I get an error message, by installing ReadyAPI 3.51.0 Java.lang.RuntimeException: No toolkit found at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:278) at com.sun.javafx.application.PlatformImpl.isFxApplicationThread(PlatformImpl.java:428) at com.sun.javafx.application.PlatformImpl.runAndWait(PlatformImpl.java:473) at com.sun.javafx.application.PlatformImpl.tkExit(PlatformImpl.java:622) at com.smartbear.ready.ui.ReadyApiMain.main(ReadyApiMain.java:258) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84) at com.exe4j.runtime.WinLauncher.main(WinLauncher.java:94) at com.install4j.runtime.launcher.WinLauncher.main(WinLauncher.java:25) Have you got any idea about this?SOAP Tests aren't running after updating ReadyAPI
Hey guys, After updating from ReadyAPI 3.43 to 3.49 my SOAP tests no longer work. I was able to narrow down the problem to the outgoing WSS. It looks as if the Basic(Bultin) authentication method requires an outgoing WSS, otherwise ws-security policies do not work. After adding outgoing WSS the tests are working. Attached is the error message: HTTP/1.1 500 500 Date: Thu, 30 Nov 2023 14:05:02 GMT Server: Apache Strict-Transport-Security: max-age=31536000 Content-Type: text/xml;charset=UTF-8 X-Content-Type-Options: nosniff X-Frame-Options: sameorigin Connection: close Transfer-Encoding: chunked <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>These policy alternatives can not be satisfied: {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}SupportingTokens {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}UsernameToken {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}HashPassword</faultstring></soap:Fault></soap:Body></soap:Envelope> Why is it required to add an WSS in this version, when it wasn't necessary in version 3.43? Is there a way to circumvent this WSS requirement?
