Aidan365
15 years agoNew Contributor
SoapUI : How to deal with DataHandler in WSDL ?
Hi,
I suspect this is a common problem, but after much searching on this and other forums I would really appreciate some help from the community here.
Basically I want to use SoapUI to test a WSLD which attempts to define a complex type that contains
<element name="in3" type="apachesoap:DataHandler"/>
Granted, I suspect this may be bad practice (to use DataHandler in the WSDL) but is there any way I can create a new SoapUI project from this wsdl without major refactoring of the WSDL or server-side webservice operations?
As you probably know, SoapUI currently will return : Error: type 'DataHandler@http://xml.apache.org/xml-soap' not found.
The webservice uses axis 1.3. We can run org/apache/axis/wsdl/WSDL2Java on the same WSDL, but really want to run SoapUI on the WSDL, hence this question.
I have looked into a few options with no success:
- Can I modify the schema definition part of my wsdl?
- Configure SoapUI to deal with (or ignore Datahandler)
- Provide the schema to SoapUI
- etc ?
At the moment I can generate test requests for the other operations if I save wsdl as a file and comment out the offennding DataHandler reference (or replace with type="xsd:string" etc.) but this is far from ideal.
Any help would be greatly appreciated. I have attached an example WSLD to illustrate the problem. It's not exactly same as my WSDL under test as that can't be shared here, but it highlights the problem. What options do I have, or can you point me to a good reference to solve this problem
Many Thanks,
Aidan
Note: I don't expect to be able to call the operations that have DataHandler (unless you think that is possible!?) but I'd really like to be able to generate a SoapUI project like I could before this complex type (with DataHandler) was added to the WSDL.
I suspect this is a common problem, but after much searching on this and other forums I would really appreciate some help from the community here.
Basically I want to use SoapUI to test a WSLD which attempts to define a complex type that contains
<element name="in3" type="apachesoap:DataHandler"/>
Granted, I suspect this may be bad practice (to use DataHandler in the WSDL) but is there any way I can create a new SoapUI project from this wsdl without major refactoring of the WSDL or server-side webservice operations?
As you probably know, SoapUI currently will return : Error: type 'DataHandler@http://xml.apache.org/xml-soap' not found.
The webservice uses axis 1.3. We can run org/apache/axis/wsdl/WSDL2Java on the same WSDL, but really want to run SoapUI on the WSDL, hence this question.
I have looked into a few options with no success:
- Can I modify the schema definition part of my wsdl?
- Configure SoapUI to deal with (or ignore Datahandler)
- Provide the schema to SoapUI
- etc ?
At the moment I can generate test requests for the other operations if I save wsdl as a file and comment out the offennding DataHandler reference (or replace with type="xsd:string" etc.) but this is far from ideal.
Any help would be greatly appreciated. I have attached an example WSLD to illustrate the problem. It's not exactly same as my WSDL under test as that can't be shared here, but it highlights the problem. What options do I have, or can you point me to a good reference to solve this problem
Many Thanks,
Aidan
Note: I don't expect to be able to call the operations that have DataHandler (unless you think that is possible!?) but I'd really like to be able to generate a SoapUI project like I could before this complex type (with DataHandler) was added to the WSDL.