vbrabant
Occasional Contributor
Joined 16 years ago
User Profile
User Widgets
Contributions
Soapui accept a wsdl considered as invalid by other tools ?
We have a vendor tool that refuse to import the following wsdl https://api.mozypro.com/api/0.1.48/partner/service.wsdl saying that such WSDL is not valid because there is no import of "http://schemas.xmlsoap.org/soap/encoding/" in the xsd:schema part. Seems that Eclipse is also complaining about that. And wsimport of Jaxws is also complaining about that. But SOAPUI accept without any problem such WSDL. Is it normal that such WSDL is accepted by SOAPUI when other tools refuses it ? If yes, can you explain the reason why SOAPUI is accepting such WSDL when other tools are refusing it ? Thanks a lot. Vincent Hereafter the result of the wsimport command [WARNING] src-resolve.4.2: Error resolving component 'soapenc:Array'. It was detected that 'soapenc:Array' is in namespace 'http://schemas.xmlsoap.org/soap/encoding/', but components from this namespace are not reference able from schema document 'file:/C://Mozy/mozy.wsdl#types?schema1'. If this is the incorrect namespace, perhaps the prefix of 'soapenc:Array' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/Mozy/mozy.wsdl#types?schema1'. line 48 of file:/C:/Mozy/mozy.wsdl#types?schema1 [ERROR] undefined simple or complex type 'soapenc:Array' line 48 of file:/C:/Mozy/mozy.wsdl [ERROR] undefined attribute 'soapenc:arrayType' line 49 of file:/C:/Mozy/mozy.wsdl [ERROR] undefined simple or complex type 'soapenc:Array' line 61 of file:/C:/Mozy/mozy.wsdl [ERROR] undefined attribute 'soapenc:arrayType' line 62 of file:/C:/Mozy/mozy.wsdl [ERROR] undefined simple or complex type 'soapenc:Array' line 68 of file:/C:/Mozy/mozy.wsdl [ERROR] undefined attribute 'soapenc:arrayType' line 69 of file:/C:/Mozy/mozy.wsdl [ERROR] undefined simple or complex type 'soapenc:Array' line 75 of file:/C:/Mozy/mozy.wsdl [ERROR] undefined attribute 'soapenc:arrayType' line 76 of file:/C:/Mozy/mozy.wsdl [ERROR] undefined simple or complex type 'soapenc:Array' line 104 of file:/C:/Mozy/mozy.wsdl [ERROR] undefined attribute 'soapenc:arrayType' line 105 of file:/C:/Mozy/mozy.wsdl Exception in thread "main" java.lang.NullPointerException at com.sun.tools.internal.xjc.reader.internalizer.SCDBasedBindingSet.apply(SCDBasedBindingSet.java:201 ) at com.sun.tools.internal.xjc.ModelLoader.createXSOM(ModelLoader.java:502) at com.sun.tools.internal.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:216) at com.sun.tools.internal.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:69) at com.sun.tools.internal.ws.processor.modeler.wsdl.JAXBModelBuilder.bind(JAXBModelBuilder.java:120) at com.sun.tools.internal.ws.processor.modeler.wsdl.WSDLModeler.buildJAXBModel(WSDLModeler.java:2173) at com.sun.tools.internal.ws.processor.modeler.wsdl.WSDLModeler.internalBuildModel(WSDLModeler.java:17 3) at com.sun.tools.internal.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:119) at com.sun.tools.internal.ws.wscompile.WsimportTool.run(WsimportTool.java:170) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.tools.internal.ws.Invoker.invoke(Invoker.java:100) at com.sun.tools.internal.ws.WsImport.main(WsImport.java:38)2.3KViews0likes0CommentsAdding NTLM v2 support in SOAPUI Proxy Settings (and others)
Would be nice if SOAPUI could have support for NTLM v2 for the Proxy Settings. Default Proxy of my company is configured to accept only requests identified with NTLM v2. So, impossible for SOAPUI to reach a service available outside our intranet because NTLM v2 is not supported by SoapUI in the Proxy Settings. Thanks a lot.3.5KViews0likes1CommentRe: Project level headers
In fact, you have that possibility, but not at project level, but at interface level. Right click at your interface level, and select "Show Interface Viewer" Select the Service Endpoints You can then associate to each endpoints url a username, password, and even Outgoing WSS and Ingoing WSS if you are using WS-Security Then, by just selecting the right endpoint url when you execute a request, the associated username & password will be used. It's really great.1.7KViews0likes0CommentsRe: How to force the Expect 100-continue ?
Thanks a lot for your reply. I know that such info is only supported by http 1.1 protocol, but it should be possible, without a lot of work and complexity I hope, to permits to enable/disable such feature in the preference panel when the Http version is 1.1. And to gray such option when Http version is not 1.1. No ?2.7KViews0likes0CommentsHow to force the Expect 100-continue ?
I have to reproduce some behaviour a client has when he call my webservice. I want to use SOAPUI (2.5) to reproduce the exact behaviour of that client. But I was unable to find how to enable the Expect 100-continue. Any idea are welcome !!!4.1KViews0likes4Comments