Contributions
Re: "Error getting response" while processing WSS response
Hi etsauer There exists a thread on this topic in the SoapUI Bugs forum: http://forum.soapui.org/viewtopic.php?f=13&t=24631&sid=b467693eb971acb0089c4f3cfc306c6d However, no one from the SoapUI team has responded to the thread yet FYI, the bug does not occur in SoapUI 4.6.4. It seems difficult to further debug this issue, since the "error" is logged with severity level "INFO" and nothing is logged anywhere else. /Christian1.4KViews0likes1CommentRe: Incorrect format of wsu:Id
Hi, Can this bug be recognized by the people at SoapUI or maybe others on the forum? As it makes the SOAP request invalid when performing WSDL validation, the bug prevents me from using SoapUI as a testing tool for my projects. Best regards Christian10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes0CommentsRe: Changed proxy settings in 5.0.0
I have tried to use the "Proxy Settings" in SoapUI in both 4.6.4 and 5.0.0, but without success. When I try to load a WSDL with imports, I am prompted with an "NT Authentication" window, even though I have entered username/password in the proxy settings. After entering the correct password and username, I get a message saying: "Error loading [the xsl url]: org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: Unexpected element: TAG_END" I have tried with different .xsl files, but with no luck. I have also tried with different combinations of domain/username during authentication.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes0CommentsIncorrect format of wsu:Id
Hi, I have a setup with an Outgoing WS-Security configuration for signing and encryption. When I send a request, the security headers are automatically created and inserted into the message, as expected. However, the value of the wsu:Id attribute is created with an incorrect format, which causes the request to be rejected during wsdl/xsd validation. The namespace "wsu" refers to http://docs.oasis-open.org/wss/2004/01/ ... ty-1.0.xsd In this schema, the definition of the Id attribute states that it is of the type xsd:ID. This refers to yet another schema, http://www.w3.org/2001/XMLSchema.xsd, where the definition of the ID type is found. The ID type has a restriction based on the NCName type, which is described here: http://www.w3.org/TR/REC-xml-names/#NT-NCName The restriction requires the wsu:Id attribute to start with "_" or any character. SoapUI allows these values to start with numeric values or other symbols, which makes the format invalid. I hope that a change to fix this will not require too much effort Best regards Christian10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.5KViews0likes1CommentRe: SoapUI 4/5 difference - Getting Error getting response;NULL
Hi I am experiencing the same behavior in my setup. However, when I turn off the Incoming WS-Security configuration, the encrypted message is received just fine. As such, my guess is that the problem lies within the Incoming WS-Security process, maybe during the decryption. A solution would be very much appreciated Best regards Christian10 years agoPlace ReadyAPI QuestionsReadyAPI Questions8.2KViews0likes0CommentsChanged proxy settings in 5.0.0
Hi, I am using SoapUI to send SOAP requests to my service through a proxy with authorization. While using version 4.6.4, I had to change soapui.bat to allow the requests to pass through the proxy. The change was as follows: set JAVA_OPTS= ... -Dhttp.proxyHost=myproxy.com -Dhttp.proxyPort=80 -Dhttp.proxyUser="myuser" In SoapUI, I then set my proxy settings to "None", and sending requests worked perfectly. I also have to go through the proxy to access the internet (getting external .xsd's or viewing the SoapUI "StarterPage"), which also worked fine with these settings. However, when I changed to version 5.0.0, this change no longer enabled me to access the internet, but only to send requests. If I change the proxy settings inside SoapUI, I am able to access the internet, but not send request through the proxy (!!!). I put this under "Bugs", since the newer version does not act the same way (correct way?) as an earlier one. I would very much like either one way or the other to work for both cases through the proxy - At least like it did in version 4.6.4.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions2KViews0likes2Comments