Contributions
SoapUI-5.0.0.exe does not find JavaFX
I installed soapui 5.0.0 with the installer (SoapUI-x32-5.0.0.exe) and then removed the jre directory because I want soapUI to use the installed Java version. When I start soapui using soapui.bat my installed jfxrt.jar in c:\Program Files (x86)\Java\jre7\lib\ is found and the browser component works. But when I use SoapUI-5.0.0.exe then the browser component does not work. Is there a property in SoapUI-5.0.0.vmoptions that lets me tell soapui where javafx is installed? I tried -Djavafx.runtime.lib.jar=C:\Program Files (x86)\Java\jre7\lib\jfxrt.jar but this did not work. Tom2.2KViews0likes1CommentRe: [Res] Error loading WSDL with german Umlaute (soapUI 4.6.4)
Hello Mark Many thanks for your post - it did solve the problem! Even though the option is called file.encoding it also seems to work when you download the WSDL from the service directly. Thanks again Tom10 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.6KViews0likes0CommentsRe: soapUI 4.6.4 not sending client certificate
Many thanks to dmaddox! Your post help me to work around my soapui problem. I can confirm that also with soapUI 4.6.4 this client certification problem only occurs when the proxy is active. When I do not have the proxy defined the certificate is sent and the requests work ok. Our proxy does not use any authentication, so the problem is not only with NTML authenticated proxies. @SmartBear: I hope these two posts help you fix the problem soon Tom10 years agoPlace ReadyAPI QuestionsReadyAPI Questions16KViews0likes0Comments[Res] Error loading WSDL with german Umlaute (soapUI 4.6.4)
When I try to create a new project from WSDL with soapUI 4.6.4 I get following error message: Error loading WSDL There was something wrong with the WSDL you are trying to import Error loading [https://test-xml.labelbase.ch/?wsdl]: org.apache.xmlbeans.XmlException: java.io.CharConversionException: Malformed UTF-8 character: 0xfc 0x63 0x6b 0x2e The WSDL contains german Umlaute in the wsdl:documentation tags, but they are correctly encoded as 0xbc 0x63, not 0xfc 0x63 as claimed by soapui When I get the WSDL with a browser, save it to a file (in UTF-8) and then use that file to create the project, I get the same error message, although there is *no* character sequence 0xfc 0x63 in this file! When I remove all german Umlaute the WSDL file, the project is created correctly With soapUI 3.6.1 it was working... Tom10 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.4KViews0likes3CommentsRe: soapUI 4.6.4 not sending client certificate
The problem is still unsolved. No comment on this problem from the SmartBear guys? Is there anyone who has successfully used soapUI 4.6.4 with client certificate authentication? Will updating to soapUI 5.x solve the problem? Thanks Tom10 years agoPlace ReadyAPI QuestionsReadyAPI Questions16KViews0likes0CommentssoapUI 4.6.4 not sending client certificate
I use a 3rd party https webservice that requires client authentication with a certificate. With soapUI 3.6.1 this works fine, with soapUI 4.6.4 it does not work because soapUI 4.6.4 does not send the client certificate during the handshake. The certificate is defined the same way for both versions (in Preferences -> SSL Settings) How does soapui know which client certificate from the keystore it should choose?? Is this somehow based on the presented server certificate (in 4.6.4) ? If yes, then I have problem because the client certificate I need to use is not derived from the certificate chain of the server certificate. Instead, I made a self-signed certificate and the admins put my public certificate into their webservice for verification. So, I would need to have a way to define which certificate of the keystore should be used when communicating with the webservice. Or, is there a way to force soapUI 4.6.4 to send the client certificate (there is only 1 in the keystore) ? Thanks in advance Tom11 years agoPlace ReadyAPI QuestionsReadyAPI Questions19KViews0likes9CommentsRe: R Getting error SSLPeerUnverifiedException in soapUI 4.5.1.1
I have downloaded soapUI 4.6.2 and still got the SSLPeerUnverifiedExceptions. But I have found the solution now: For every webservice accessed through https, you need to add the certificate of the server (or the parent certificate of the server's certificate) to your cacerts file. If you don't have write access to the cacerts file, you can copy the cacerts file to a writeable location (e.g. X:\_soapui\), add the certificates and change the soapui.bat as follows: set JAVA_OPTS=-Djavax.net.ssl.trustStore=X:\_soapui\cacerts -Xms128m -Xmx1024m -Dsoapui.properties=soapui.properties "-Dsoapui.home=%SOAPUI_HOME%\" -splash:soapui-splash.png Tom11 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.5KViews0likes0CommentsRe: R Getting error SSLPeerUnverifiedException in soapUI 4.5.1.1
This is a know issue (SOAPUI-4487) and we'll inform you as soon as we got more information about this. Is there any progress on this issue? soapUI-Pro-x32-4.5.1.1-SNAPSHOT.exe does not work for me. Thanks Tom12 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.5KViews0likes0CommentsRe: Incorrect WSDL parsing in soapUI Pro 3.5.1
Hello Ole Yes, the WSDL is using SOAP Encoding. What is just a bit confusing is, that in soapUI 2.0.2 the WSDL was parsed correctly and the editor did not have any problems with the WSDL. So, in this context, soapUI 3.5.1 is not backward compatible and we shirk the upgrade if an important feature is not working anymore... I have send the WSDL by mail. Thanks for digging. Tom14 years agoPlace ReadyAPI QuestionsReadyAPI Questions651Views0likes0Comments