Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Hilderich,
in 5.3 there is no way by means of an outside configuration to make it working on a Data Service (from Studio exported), mean my hope that we can apply a policy does not exists anymore. As a summery of options we see:
1) Wait for 5.4.0 / 5.4.1 (but we know not everyone can switch to the newest version immeditaly but it might be still an option to consider as here it is supported by policy an by a simple 'Check Box' to enable it for the Data Service provider very easily.
2) Use a Proxy in front (e.g. a Route with cCXF and schema validation enabled)
3) Do the schema validation in the Data Service Operation (using tXSDValidator right after tESBProvider Request component)
4) well not really something easy but if you really like to go down the path to even patch the exported kar file it should work to patch the bean.xml directly (by this you have to extract the kar file and the contral-bundle jar also and change the '{your dataservice name}-control-bundle\0.1\META-INF\spring\bean.xml and add the following jaxws property to the existing jaxws properties (add it to the existing once)
<jaxws
roperties>
..... others already existing once ........
<entry key="schema-validation-enabled" value="true"/>
</jaxwsroperties>
After that you have to make sure that you really create a valid jar and kar again with the changed bean.xml and when you then deploy it to the Container it should enforce the schema validation (but for sure whenever you export the dataservice from the studio this change will be lost (you might need to setup e.g. a jenkins job or so to do this in a more automated fashion )
Some hint to the jaxws property can be also found here: http://www.jroller.com/gmazza/entry/soap_xml_schema_validation
I hope one of the options is still helpful for you.
Dietmar
in 5.3 there is no way by means of an outside configuration to make it working on a Data Service (from Studio exported), mean my hope that we can apply a policy does not exists anymore. As a summery of options we see:
1) Wait for 5.4.0 / 5.4.1 (but we know not everyone can switch to the newest version immeditaly but it might be still an option to consider as here it is supported by policy an by a simple 'Check Box' to enable it for the Data Service provider very easily.
2) Use a Proxy in front (e.g. a Route with cCXF and schema validation enabled)
3) Do the schema validation in the Data Service Operation (using tXSDValidator right after tESBProvider Request component)
4) well not really something easy but if you really like to go down the path to even patch the exported kar file it should work to patch the bean.xml directly (by this you have to extract the kar file and the contral-bundle jar also and change the '{your dataservice name}-control-bundle\0.1\META-INF\spring\bean.xml and add the following jaxws property to the existing jaxws properties (add it to the existing once)
<jaxws
roperties>
..... others already existing once ........
<entry key="schema-validation-enabled" value="true"/>
</jaxws
roperties>
After that you have to make sure that you really create a valid jar and kar again with the changed bean.xml and when you then deploy it to the Container it should enforce the schema validation (but for sure whenever you export the dataservice from the studio this change will be lost (you might need to setup e.g. a jenkins job or so to do this in a more automated fashion )
Some hint to the jaxws property can be also found here: http://www.jroller.com/gmazza/entry/soap_xml_schema_validation
I hope one of the options is still helpful for you.
Dietmar