Schema Validation on Webservice Endpoints

[T. Papke]

Hello IPF User's,

currently IPF XDS (and other soap based API's) do not enable xsd Schema Validation by default and also do not provide an easy configuration option.

CXF itself support a option:

https://cxf.apache.org/faq.html#FAQ-HowcanIturnonschemavalidationforjaxwsendpoint

E.g. on ITI-42 component this can be configured by passing 

xds-iti42:registry/iti42?properties=#xdsProperties

And defining a corresponding bean

@Bean

Map<String, Object> xdsProperties() {

return Maps.of("schema-validation-enabled", "true");

}

--> Now two questions here:
Are there any reason's why a schema validation shall not be supported?

Similar to CXF Camel component, shall we add a more lightweight endpoint configuration like  "schemaValidationEnabled=true" to IPF's WS components to simplify the configuration here?

Best regards,

Thomas

[Dmytro Rud]

Hi Thomas

1. During the last 15 years, the IPF's Java-based XDS validators have proven that they are good enough.  There are nevertheless errors which they are unable to catch -- for example, a wrong order of XML elements, but not "wrong enough" to become a problem for the JAXB unmarshaller).  But, of course, we shall not prohibit XSD-based validation.

2. I think, the option "properties" is enough.  Because the option "schemaValidationEnabled" would be unique for XDS, as the Camel validators for all other XML-based formats used in SOAP transactions (HL7v3, DSMLv2, SAML, XACML, etc.) involve XSD-based validation as well (if I remember correctly).

Thank you and best regards

Dmytro

--
You received this message because you are subscribed to the Google Groups "ipf-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ipf-user+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ipf-user/CADbaft97pf4uM%3DupJtsRS70J268aWcuPeh2cLLAMVVxqBJLbMQ%40mail.gmail.com.