Forum Discussion
paulmckenna
14 years agoNew Contributor
Hi Aidan,
DataHandler is a platform-specific type, only used by Apache Soap
This means that those APIs have to be called from Java using the Apache Soap jar, and not (eg) C++, .NET or SoapUI
No platform other than Apache Soap is going to understand it. Apache Soap was a non-standards project that was abandoned in about 2002, and was superseded by Apache Axis; links from Apache Axis to Apache Soap in 2004 are dead, and Apache Soap has no web presence.
Even though SoapUI is Java, it does not implement Apache Soap.
I've compiled SoapUI from source, and it would not be easy to update to include an abandoned standard, even unofficially.
SoapUI has hard-coded validation of the wsdl against the wc3 standards, and so DataHandler won't pass.
I believe that you could continue to use DataHandler server-side, exposing it using MTOM and Base64Binary which IS a standard, but that there is no alternative to changing the wsdl extensively.
Regards
Paul
DataHandler is a platform-specific type, only used by Apache Soap
This means that those APIs have to be called from Java using the Apache Soap jar, and not (eg) C++, .NET or SoapUI
No platform other than Apache Soap is going to understand it. Apache Soap was a non-standards project that was abandoned in about 2002, and was superseded by Apache Axis; links from Apache Axis to Apache Soap in 2004 are dead, and Apache Soap has no web presence.
Even though SoapUI is Java, it does not implement Apache Soap.
I've compiled SoapUI from source, and it would not be easy to update to include an abandoned standard, even unofficially.
SoapUI has hard-coded validation of the wsdl against the wc3 standards, and so DataHandler won't pass.
I believe that you could continue to use DataHandler server-side, exposing it using MTOM and Base64Binary which IS a standard, but that there is no alternative to changing the wsdl extensively.
Regards
Paul