Schema validation question

Does data service automatically validate any xquery input parameters against respective XML Schema by default? If so, can it be turned off?

It depends on the way the function arguments and return types are defined.
If they are defined as element (foo) - then the schema validation is not done.
If they are defined as schema-element (foo) causes it to perform validation.
Hope this helps.
Thanks,
Patrick

Similar Messages

XML SCHEMA validation question

i'm using jdk 1.4.2 and am trying to validate an xml document against an xml schema. i don't have any packages like xerces or apache and am trying to avoid having to use them. i've had a look at the jdk 1.5 api documentation, and it seems to have some new classes dedicated to xml validation using schemas that 1.4.2 does not have (e.g. the Schema class). my question is, is it possible to do xml validation against a schema only using jdk 1.4.2 and without the likes of the xerces and apache parser packages?
any help much appreciated, thanks

The tutorial on Schema Validation parses/validates with the SAXParserFactory. J2sdk 1.4.2 JAXP has an error in the implementation of the SAXParserFactory. Parse/validate with the DocumentBuilderFactory instead of the SAXParserFactory.
http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JAXPSAX9.html

Schema Validation Questions

I'm not really sure if this is the proper forum, so please advise if I got that wrong.
I'm quite the newbie on schema validations, but have had some success using them. In the past, I've used tools such as XRay and Editix to do this. Now I'm experimenting with doing this in my c# project using the XmlSchemaSet.
One thing I have noticed, regardless of which tool being used, is that if namespaces don't match, the validation seems to give a "false positive", as it reports successful validation even if there are missing nodes as per the schema.
It seems like if the namespaces don't match, the validation should either fail and advise of that, or ignore the namespaces and use the schema to simply validate against the xml being supplied. It is misleading to report a successful validation just
because the namespaces don't match.
Am I totally misunderstanding this topic? Are there any articles you can recommend to learn this stuff?
Thanks for any help...
Ron Mittelman

Hello Ron,
I am not familiar with XRay and EditiX, while for the xmlschemaset class, it is by designed that when validating a document the target namespace of the document must match the target namespace of the schema in the schema set, for details, you could check
this article:
XML Schema (XSD) Validation with XmlSchemaSet
Or it will perform the behavior which seems to be false positive.
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Getting schema validation working in Eclipse with Coherence 3.7.1.0

Just wondered if anyone had got schema validation to work in Eclipse (3.5 - Galileo) for Coherence 3.7.1.0?
The Coherence developer docs show that you should add sections like this:
<pof-config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://xmlns.oracle.com/coherence/coherence-pof-config"
xsi:schemaLocation="http://xmlns.oracle.com/coherence/coherence-pof-config
coherence-pof-config.xsd">
However, if I use that "shortened" form (for cache, pof, etc. configs) Eclipse gives a warning "No grammar constraints (DTD or XML schema) detected for the document." and the schema validation fails to work (i.e. no "auto pop-ups" when entering content, and rubbish content is gladly accepted.)
In Coherence 3.7.0, I'd used the following "extended" form (note the longer "schemaLocation") to get things working correctly:
<pof-config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://xmlns.oracle.com/coherence/coherence-pof-config"
xsi:schemaLocation="http://xmlns.oracle.com/coherence/coherence-pof-config
http://xmlns.oracle.com/coherence/coherence-pof-config/1.0/coherence-pof-config.xsd">
Also note that entering the "http://xmlns.oracle.com/coherence/coherence-pof-config/1.0/coherence-pof-config.xsd" in a web browser opens the xsd, as you'd expect.
Now...
I'm looking at the PofAnnotationSerializer in 3.7.1.0 and the "auto indexing" option. The declaration in my pof file for it fails as the "class" (or fully-qualified java.lang.Class version) in the "init-params" section isn't valid. If I look at the xsd on the url above, this is indeed the case, that option does not appear.
However, if I look at the POF xsd in the coherence.jar file for 3.7.1.0, the "class" option has been added, and has a newer 'version="1.1"' added to it's schema declaration. So I therefore tried to point my "extended" declaration to point to " http://xmlns.oracle.com/coherence/coherence-pof-config/1.1/coherence-pof-config.xsd", in order to get schema validation to work in Eclipse with this new schema. Unfortunately that url doesn't exist - you get a "Content Server Request Failed" error.
So, I guess my question is, is there a way to get myself pointed at the 1.1 versions of the xsd's so I can have schema validation working in Ecliipse? Or is there another workaround (did a bit of Googling, but that mainly seemed to be people switching validation off to simply get rid of the error...)
Cheers,
Steve

Cheers, Dave.
I had in fact had a try at extracting the xsd and pointing to it directly, and that did indeed work (had to do this following the same steps shown below using an "entry" in the XML Catalog.)
I had a look around at some of the other "entries" in Eclipse by default and noticed that they actually refer to xsd's directly within the jars, hence saving the extraction step and keeping screw-ups down to a minimum; a bit of playing around to get the syntax right and I finally managed to get it working.
For those who are interested (NB. my Coherence 3.7.1.0 install is in a directory "c:\coherence3.7"), the steps are:
In Eclipse, Go to Window->Preferences->XML->XML Catalog. Then create a "User Specified Entry".
In the "Location", add (without the quotes): "jar:file:/C:/coherence3.7/coherence/lib/coherence.jar!/coherence-pof-config.xsd"
In the "Key Type", add (without the quotes): "Namespace Name"
In the "Key", add (without the quotes): "http://xmlns.oracle.com/coherence/coherence-pof-config"
The schema validation now works fine. Eclipse shows no warnings/errors, and the auto-complete and validation are fully functional.
Still, it would be nice to get the "1.1" urls updated to point to the schemas on the Oracle site, to avoid all our developers from having to make these changes (and of course avoid them pointing at an older, out-of-date local install of coherence.)
Cheers,
Steve

Java Stored Procedure SAXParser XML Schema Validation

Using Oracle XML Developers Kit 10.2.0.2.0 - Production.
Attempting to validate using XML Schema in a Java stored procedure with the code:
               if ( schemaDoc == null )
                    // Obtain default connection
                    Connection conn = new OracleDriver().defaultConnection();
                    OraclePreparedStatement stmt = (OraclePreparedStatement) conn.prepareStatement("SELECT XmlDocObj FROM XmlDoc WHERE XmlDocNbr = 2");
                    OracleResultSet rset = (OracleResultSet)stmt.executeQuery();
                    if ( rset.next() )
                         // get the XMLType
                         XMLType schemaXml = (XMLType)rset.getObject(1);
                         XSDBuilder builder = new XSDBuilder();
                         XMLSchema schemaDoc = (XMLSchema)builder.build(new InputSource(schemaXml.getInputStream()));
               if ( inst == null )
                    inst = new ValidateCoreRequest();
               ErrorHandlerImpl handler = inst.getNewErrorHandler();
SAXParser saxParser = new SAXParser();
saxParser.setXMLSchema(schemaDoc);
saxParser.setValidationMode(XMLParser.SCHEMA_VALIDATION);
saxParser.setErrorHandler(handler);
saxParser.parse(new InputSource(new StringReader(docStr)));
if( handler.validationError )
                    errorMsg[0] = handler.saxParseException.getMessage().substring(0, Math.min(199, handler.saxParseException.getMessage().length()));
Never reports validation errors in the XML. Although the XDK Programmers Guide states "...you can use
the oracle.xml.parser.schema.XSDBuilder class to build an XML schema and
then configure the parser to use it by invoking the XMLParser.setXMLSchema()
method. In this case, the XML parser automatically sets the validation mode to
SCHEMA_STRICT_VALIDATION and ignores the schemaLocation and
noNamespaceSchemaLocation attributes." No validation seems to occur. I have tried to set an xsi:noNamespaceSchemaLocation attribute on the root XML node, but this results in URL errors if the URL is not valid or schema build errors if the URL is valid, but does not point to a real location.
It appears that without a schema location attribute, no schema validation occurs. Using setXMLSchema() with a database source does not seem to cause the schema location attributes to be ignored. At least for Java stored procedures.
Does XML Schema validation work in the database for externally referenced schemas?
Thank You,
Art

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Jan Vissers ([email protected]):
I have two schemas A and B. A contains a java stored procedure which calls a java stored procedure stored in B. Upon resolving the "A" Java Stored Procedures I get the following error:
ORA-29545: badly formed class: at offset 3093 of Adapter.TFADPBeschikbaarheid.sendAanvraag expecting a class-oracle.xml.parser.v2.XMLDocument but encountered a class-oracle.xml.parser.v2.XMLDocument.
... Question:
it is expecting something which it has in fact encountered... SO!!!! What is the error.
Thx,
Jan<HR></BLOCKQUOTE>
Try this:
Edit your XSU installation script located on lib directory of Oracle XSU's distribution:
Find the line:
loadjava -r -v -u $USER_PASSWORD xmlparserv2.jar
Replace by:
loadjava -r -v -g public -u $USER_PASSWORD xmlparserv2.jar
And installs your Oracle XSU again.
Best regards, Marcelo.

Schema validation

We are migrating from 10g to 11g but seem to be getting schema validation errors. This did not happen on 10g - can I turn this validation off in 11g.

We are migrating from 10g to 11g but seem to be getting schema validation errors. This did not happen on 10g - can I turn this validation off in 11g. I guess you are asking a question related to SOA but for which component - BPEL, Mediator, OSB...? Where exactly it is failing validation? Provide complete error detail along with the stack trace.
Regards,
Anuj

Schema validation for XMLType Clob vs Binary

Hi
Whilst looking at 11g R2 for use in validating XML against schemas, I have noticed that validation of XML using xmlDoc.schemavalidate() on a XMLType of CLOB would appear to be using a different schema validation process to validating by inserting into a column of XMLType of Binary.
A couple of things that drew my attention to this is 1) the slight difference in error message format , and 2) the fact that the validation for the Binary XMLType was detecting an error with a date format whilst validation of the CLOB wasn't.
Can anyone recommend which is the more thorough / robust of two ways to validate against a schema.
Many Thanks
Lawrence

You'll find the {forum:id=34} forum the more appropriate location for this question. Include all 4 digits of your version and if possible a short script that shows the issue you found.
Look in the [url https://wikis.oracle.com/display/Forums/Forums+FAQ]FAQ for how to use the tag to wrap your sample code and retain formatting when posting. This would include how the schema is registered (I'm assuming you did at least).

Schema Validation Key/Keyref and substitutionGroup Problem

First, thank you for fixing the schemaLocation problem.
My next question is about key/keyref and substitution. If I define a key/keyref relationship inside one element, then use another element to substitute that element, I found that the key/keyref relationship is not preserved in the new element using oracle schema validation. I am not clear whether this is the correct behavior.
For example:
<element name="extended" type="xl:extendedType" abstract="true">
<key name="labelKey">
<selector xpath=".//[@xlink:type='locator']"/>
<field xpath="@xlink:label"/>
</key>
<keyref name="labelKeyRef1" refer="self:labelKey">
<selector xpath=".//*[@xlink:type='arc']"/>
<field xpath="@xlink:from"/>
</keyref>
</element>
<element name="calculationlink" type="xl:extendedType" substitutionGroup="xl:extended"/>
The key/keyref is not validated inside calculationlink in this case.
Yufei
null

Yufei,
After we tested the schema location problem using the test case we produced, we can't find it has any problem. Would you send us the test data you have if you think it not works for you?
I will check your keyref soon.

Schemas validation

I'm using schema validation to validate XML instances.
In case of error (constraint violation), I need to provide information back to the user about the problem such as :
- value provided by the user,
- constraint violated,
- list of the facets of the object (min, max, nb of fractional digits, ...) and in addition, if possible, some (non native) attributes of the element.
Example :
Here is a complex type (part of o schema) describing the properties an element must match :
<xsd:complexType name="hciRADIUS_ACC_THRES_T">
     <xsd:simpleContent>
          <xsd:restriction base="FloatDef_T">
               <xsd:maxInclusive value="99.9"/>
               <xsd:minInclusive value="1.0"/>
               <xsd:fractionDigits value="1"/>
               <xsd:attribute ref="label" fixed="Radius Acc Thres"/>
               <xsd:attribute ref="continous" fixed="true"/>
               <xsd:attribute name="precision" type="xsd:decimal" fixed="0.1"/>
          </xsd:restriction>
     </xsd:simpleContent>
</xsd:complexType>
Here is the corresponding element :
<xsd:element name="hciRADIUS_ACC_THRES" type="hciRADIUS_ACC_THRES_T">
When receiving the element "hciRADIUS_ACC_THRES" in an XML instance with value 120.33 for example :
<hciRADIUS_ACC_THRES>120.33</hciRADIUS_ACC_THRES>
I would like to retrieve information about the properties of the element type in order to send an error message back to the user, message which could be formatted as follow :
Radius Acc Thres error[info contained in attribute "label"] : value 120.33
Possible values : from 1.0[info contained in "minInclusive" facet] to 99.9[info contained in "maxInclusive" facet], number of fractional digits is 1[info contained in "fractionDigits" facet]...
My questions are :
- Is it possible to do that using a java SAX or DOM parser ? -> can anybody send me some code examples or tell me where to find them ?
- Should I use DOM Level 3 API ?
Thank you all

Yes, I can use an ErrorHandler, but the ErrorHandler has a very poor content (only a standard message). I need much more information on the error such as the facets of the error node to give a complete message back to the user (min value, max value, nb of frcational digits, ...)
Thank you.

Schema Validator does not honor "nullable" attribute

Oracle XML Schema validator v1.0 does not seem to honor "nullable" schema attribute as in:
<xsd:element name='myelem' type='xsd:string' nullable='true'/>
On input
<myelem/> or <myelem></myelem>
it reports:
Element not completed: 'myelem'
Thanks
null

My mistake. Input must be specified as:
<myelem xsi:null="true">
where
xmlns:xsi="http://www.w3.org/1999/XMLSchema/instance"
null

Error : Catalog object schema validation failed in OBIEE 11.1.1.5

Hi all ,
Facing the below error while accessing few reports present in a folder (Voice Tab) . But , able to access other reports present in the same folder .
Catalog object schema validation failed: /users/weblogic/sayak/TPLAN reports/Voice Tab/Net revenue per minute (ILD\/NLD)
Error Details
Error Codes: AGFIXBO2:EIRWWH9E
Location: saw.httpserver.processrequest, saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool, saw.threadpool, saw.threads
Also while try to edit the analysis (Net revenue per minute (ILD\/NLD) from catalog , i am getting the above error .The Reports were fine till yesterday , What could be the issue ?
Thanks

Hi Devarasu ,
Yeah .. I'm aware of this bug of 11.1.1.5 , but I'm puzzeled by the sudden impact of it . i.e , It didn't gave me the error while creating/editing the file yesterday and looked fine on dashboard as well .
However , If there's no alternative other than applying patch , then please let me know the patch ID .
And applying this patch means , just overwriting some configure files in the OBIEE home folder sructure ? or somthing else ?
Thanks

"Schema validation found non-data type errors" error when passing a string value to date field in infopath

Hi,
I have an infopath web brower enabled form. In the form i have a date field.
I am passing the data from the database to that field using the C# code.
But, as the field from database is coming as string, i am getting an error, and i am not able to assign the value.
I get the date value from database as "3/25/2011 12:00:00 AM"
I used the below code:
[CODE]
if (objInfopathFormcData.myRecievedDate != null)
myRoot.SelectSingleNode("/my:myFields/my:field97", NamespaceManager).SetValue(objInfopathFormcData.myRecievedDate);
[/CODE]
I am getting the error as "Schema validation found non-data type errors".
How to set the value for a date field in Infopath.
Thank you

HI,
I fixed it:
Below code is used to fix:
[CODE]
XPathNavigator xfield = null;
DateTime dtmyRecievedDate;
dtmyRecievedDate = Convert.ToDateTime(objInfopathFormcData.myRecievedDate);
if (objFormcData.FcCompletionDate != null)
xfield = myRoot.SelectSingleNode("/my:myFields/my:field97", NamespaceManager);
DeleteNil(xfield);
xfield.SetValue(dtmyRecievedDate.GetDateTimeFormats().GetValue(5).ToString());
// method to delete xsi:nil
private void DeleteNil(XPathNavigator nav1)
if (nav1.MoveToAttribute("nil", "http://www.w3.org/2001/XMLSchema-instance"))
nav1.DeleteSelf();
[/CODE]
Thank you

Processing Schema Validation error in BPM?

Hi all,
We have a file to IDOC scenario where if the schema validation fails on the file adapter sender agreement, we want to pull the filename and send it in an error email. So, we are talking about the adapter specific message attribute "Filename".
unfortunately, this does not seem to be available as a container element for alert catagories in ALRTCATDEF. So, we are starting to look into using BPM to send a email via the email adapter. However, since the validation happens prior to BPM being called I am at a bit of a loss. Any ideas on how to get the email with the filename out to the suport group would be appreciated.
Thanks,
Chris

package com.validate;
import com.sap.aii.mapping.api.*;
import com.sap.aii.mappingtool.tf7.rt.Container;
import java.io.*;
import javax.xml.transform.stream.StreamSource;
import javax.xml.validation.*;
public class ValidateXML extends AbstractTransformation {
    public void transform(TransformationInput transformationInput, TransformationOutput transformationOutput) throws StreamTransformationException {
        OutputStream outputstream = null;
        try {
            InputStream inputstream = transformationInput.getInputPayload().getInputStream();
            outputstream = transformationOutput.getOutputPayload().getOutputStream();
            byte[] b = new byte[inputstream.available()];
            inputstream.read(b);
            String XMLinputFileContent = new String(b);
            // define the type of schema - we use W3C:
            String schemaLang = "http://www.w3.org/2001/XMLSchema";
            // get validation driver:
            SchemaFactory factory = SchemaFactory.newInstance(schemaLang);
            //Place XSD file in PI server same as http://help.sap.com/saphelp_nwpi711/helpdata/en/44/0bf1b3ec732d2fe10000000a11466f/frameset.htm
            //OR I think you can place any where on server.
            File XSDfile = new File("C:/xi/runtime_server/validation/schema/SchemaFile.xsd");
            // create schema by reading it from an XSD file:
            Schema schema = factory.newSchema(new StreamSource(XSDfile));
            Validator validator = schema.newValidator();
            // at last perform validation:
            validator.validate(new StreamSource(XMLinputFileContent));
            //If XML it not valid, exception will be thrown, if it is valid sent this PassOutputXML to output
            String PassOutputXML = "<?xml version=\"1.0\" encoding=\"UTF-8\"?><ns:MT_OutputXML xmlns:ns=\"http://sap.com/xi\"> <Name>FileName.txt</Name><Validation>Pass</Validation> </ns:MT_OutputXML>";
            outputstream.write(PassOutputXML.getBytes());
        } catch (Exception exception) {
            //Get File name using http://help.sap.com/saphelp_nwpi711/helpdata/en/43/03612cdecc6e76e10000000a422035/frameset.htm
            Container container = null;
            DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
            DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File", "FileName");
            String inputFileName = conf.get(key);
            String FailOutputXML = "<?xml version=\"1.0\" encoding=\"UTF-8\"?><ns:MT_OutputXML xmlns:ns=\"http://sap.com/xi\"> <Name>" + inputFileName + "</Name><Validation>Fail</Validation> </ns:MT_OutputXML>";
            try {
                outputstream.write(FailOutputXML.getBytes());
            } catch (IOException ex) {
                exception.printStackTrace();
                ex.printStackTrace();

Schema Validation failure in SOA Suite 11.1.1.6.0 but not in 11.1.1.7.0

I have a composite that is deployed on both a SOA Suite 11.1.1.6.0 and 11.1.1.7.0 server.
The composite exposes a service that my application subscribes to and sends messages to so the BPMN process can handle the request.
This works fine in 11.1.1.7.0. However, in the older version, when the message gets sent out, I'm getting the error shown below.
I've made sure that Schema Validation is disabled on all of the endpoints, but that doesn't appear to have any affect. Any thoughts?
<Aug 29, 2013 12:00:59 PM EDT> <Error> <oracle.webservices.service> <OWS-04115><An error occurred for port: FabricProvider: javax.xml.rpc.soap.SOAPFaultException: Schema validation failed for message part parameters. Please ensure at the message sender level that the data sent is schema compliant. Attribute 'http://schemas.xmlsoap.org/soap/envelope/:encodingStyle' not expected..>
<Aug 29, 2013 12:01:00 PM EDT> <Error> <oracle.webservices.service> <OWS-04086>
<javax.xml.rpc.soap.SOAPFaultException: Schema validation failed for message part parameters. Please ensure at the message sender level that the data sent is schema compliant. Attribute 'http://schemas.xmlsoap.org/soap/envelope/:encodingStyle' not expected.
        at oracle.integration.platform.blocks.soap.WebServiceEntryBindingCompone
nt.generateSoapFaultException(WebServiceEntryBindingComponent.java:1193)
        at oracle.integration.platform.blocks.soap.WebServiceEntryBindingCompone
nt.processIncomingMessage(WebServiceEntryBindingComponent.java:971)
        at oracle.integration.platform.blocks.soap.FabricProvider.processMessage
(FabricProvider.java:113)
        at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing
(ProviderProcessor.java:1187)
        at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementatio
n(WebServiceProcessor.java:1112)
        at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(
ProviderProcessor.java:581)
        at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServicePr
ocessor.java:233)
        at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcess
or.java:193)
Thanks,
Mike

Any suggestions on this....

Error in schema validation in XI. Please help!

Hi Experts,
I have a FILE to proxy scenario. In the sender agreement I have selected schema validation by Adapter. (Other option is by Integration Engine). Now when the file I get an error in sender file communication channel monitoring:
Error: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Schema DataIn.xsd not found in D:\usr\XXXXXXXXX\validation\schema\31f7c36098e411deadcae4d30a13c639\httptraining-00EIM_POC\DataIn_Async_Out\httptraining-00EIM_POC\DataIn.xsd (validation\schema)
Do I need to keep the schema file in some server location? Do I need to setup this path anywhere? Where do I need to place the schema file?
What is the difference between validation by adapter and by integration engine?
Please help!
Thanks
Gopal

>What is the difference between validation by adapter and by integration engine?
Both are same. One in Java engine and the other in the abap engine. If you set at one place that is good enough. In 7.1+ this becomes one of the pipeline steps.
>Do I need to keep the schema file in some server location? Do I need to setup this path anywhere? Where do I need to place the schema file
Yes you have to place schema in the server location.
Refer the Rajasekar document for the placing this file in the server location.

Schema validation question

Similar Messages

Maybe you are looking for