Answer by Reguel Wermelinger

Reguel Wermelinger — Wed, 30 May 2018 09:38:27 -0400

CXF can easily ignore that exception

You can disable the schema validation as described here: http://mail-archives.apache.org/mod_mbox/cxf-users/201001.mbox/%3C201001291547.56047.dkulp@apache.org%3E

Within Axon.ivy 7.1 you just have to pack this property into a custom feature:

package com.axonivy;

import ch.ivyteam.ivy.webservice.exec.feature.WebServiceClientFeature;
import ch.ivyteam.ivy.webservice.exec.feature.WebServiceClientFeatureContext;

public class CompliantSchemaValidation implements WebServiceClientFeature {

    @Override
    public void initialize(WebServiceClientFeatureContext context) {
        context.getBindingProvider().getRequestContext()
            .put("set-jaxb-validation-event-handler",  "false");
    }

}

And then use in in your client configuration.... Then these unexpected subElement exceptions are gone.

Another solution could be to set a specific event handler and only ignore these unexepted SubElement exceptions. But I didn't test it: http://whileonefork.blogspot.com/2010/11/cxf-backwards-compatibility-adding.html

AXIS2 needs dirty handwork

If you can not migrate to Axon.ivy 7.1 or newer you can also patch Axis2 client to ignore new properties.

add AXiS2 dependencies to your project classpath
introduce a new source folder (e.g. src_axis)
add the contents of your webservice client jar (lib_ws/client/xyz.JAR) to your new source folder
remove the original client jar from the classpath
patch the factory classes of your beans. E.g. uncomment all occurences of AdbException with Unexpected subelement as message.

Answers to: Can I avoid 'Unexpected subelement' errors when the service-provider introduces new properties?

Answer by Reguel Wermelinger