Contributions
Re: [SOLVED]soapUI 3.0.1 and MTOM: cast exception
I solved my issue. I have just forgot to change the "Request Properties" in order to set to True the property "Enable MTOM". You can also force MTOM. The "Request Properties " are available at the lower left part of the soapUI screen. S.15 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews0likes0Comments[SOLVED]soapUI 3.0.1 and MTOM: cast exception
Hello, I am using soapUI Pro edition (version 3.0.1) and try to invoke a Web Service with an attachment. This Web Service (deployed on Oracle WebLogic Server 10gR3) works properly with a Java Client proxy. Through soapUI, when I submit my SOAP request with an attachment, I got the following error on the server: Caused by: java.lang.ClassCastException: javax.activation.DataHandler cannot be cast to com.sun.xml.ws.developer.StreamingDataHandler Is this a known problem or limitation of soapUI? Is there any workaround or did I miss something? Thanks for your help15 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.7KViews0likes1CommentRe: SOAP UI 3.0 Endpoint editing on a Mac vs Windows
Hi. I can confirm this issue with soapUI pro 3.0.1. Here is how it works: in the request window, you have the endpoint selection drop-down at the top. If you click it once and then click on an endpoint, it is not selected and the window closes. If you hold the mouse button down and release it on the endpoint to select, it works. I verified this on two different machines, one with Leopard and one with Snow Leopard.648Views0likes0CommentsRe: Memory leak Soap UI?
Hi, We do have the same kind of problem using Soap UI pro 2.02 on win XP, but without even running a test case. Here are the operations we perform and the associated memory usage: Launching SoapUI and opening the project we use: 79716K Creating a new empty test case: 190104K (While loading the cached wsdl) Creating another test case: 214312K Adding a request: 218716K Any idea where this could come from?17 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes0Comments2.0.2 Pro: choice issue with Form mode
Hi, We have a problem with SoapUI 2.0.2 Pro when creating a request in form mode and the request contains a between two elements. I created a small WSDL to illustrate the issue (full WSDL attached). It looks like this: or in xml: <xsd:element name="NewOperation"> <xsd:complexType> <xsd:sequence> <xsd:element name="a" type="xsd:string" /> <xsd:choice> <xsd:element name="b" type="xsd:string"></xsd:element> <xsd:element name="c" type="xsd:string"></xsd:element> </xsd:choice> <xsd:element name="d" type="xsd:string"></xsd:element> </xsd:sequence> </xsd:complexType> </xsd:element> To see the problem, create a request with it in form mode, switch to XML mode and you'll get: <soapenv:Body> <soap:NewOperation> <a>sdfsqdf</a> <!--You have a CHOICE of the next 2 items at this level--> <b>?<b>bbbbbbb</b></b> <c>?</c> <d>jkhkjh</d> </soap:NewOperation> </soapenv:Body> This is clearly wrong. There should only be one tag and no . It doesn't even validate: line 7: Element not allowed: b in element b line 8: Expected element 'd' instead of 'c' here in element NewOperation@http://www.vivansa.com/soapuitest/ Note that if you fix it in XML, switch to form mode and back, it's gone wrong again. Therefore, the only solution right now is to set the default edit mode to be XML but I have to switch to form mode for every other request in the project.17 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.4KViews0likes1Comment