Xsd validation in java

hai
I need help on validating a schema(xsd) file in parsing an xml document
how can i do it ?
I would be thankful if you could give any sample code or link .
Thank you

hi Jose,
PI 7.1 has a built in feature available called XML vaidations ..
your source xml can be validated against a XSD placed at a specific location on the PI server..
validation can be performed at adapter/integration engine
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06dff94-9913-2b10-6f82-9717d9f83df1?quicklink=index&overridelayout=true

Similar Messages

Problem with XSD validation in Java 5

Hi everyone,
my application creates in memory schema using JDOM. In Java 6 validation runs fine, but in Java 5 (which is the target platform currently) it fails.
I tried a second test with just parsing an existing XSD document (not created using JDOM) and that works.
The textual representation of both (file and JDOM generated) are identical. If I replace the XSD file with the JDOM output, the "file test" runs fine, too.
Here's the test code:
    protected void assertXsdValid(Source xsdSource, InputSource xmlInputSource) throws SAXException, ParserConfigurationException, IOException {
        isValid = true;
        SchemaFactory sf = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);
        sf.setErrorHandler(myErrorHandler);
        Schema schema = sf.newSchema(xsdSource); // <<--------- THIS LINE FAILS IN JAVA 5
        DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
        dbf.setNamespaceAware(true);
        dbf.setSchema(schema);
        DocumentBuilder db = dbf.newDocumentBuilder();
        db.setErrorHandler(myErrorHandler);
        db.parse(xmlInputSource);
        assertTrue(isValid);
    }This is the XSD:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://some.org/metamodel" elementFormDefault="qualified">
<xs:element name="system">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="name" type="xs:string" />
        <xs:element name="vendor" type="xs:string" />
        <xs:element name="version" type="xs:decimal" />
      </xs:sequence>
    </xs:complexType>
</xs:element>
</xs:schema>This is the error message I get:
ERROR: org.xml.sax.SAXParseException: s4s-att-invalid-value: Invalid attribute value for 'type' in element 'element'. Recorded reason: UndeclaredPrefix: Cannot resolve 'xs:string' as a QName: the prefix 'xs' is not declared.
This is how I call the test code in the JDOM test:
        assertXsdValid(new JDOMSource(xsdDoc), new JDOMSource(xmlDoc).getInputSource());If I change the code to parsing not the JDOMSource, but a StreamSource reading the textual representation of the XSD, it works fine!
        assertXsdValid(new StreamSource(new ByteArrayInputStream(new XMLOutputter().outputString(xsdDoc).getBytes())), new JDOMSource(xmlDoc).getInputSource());But this is not what I want (I expect suboptimal performance with large XSD documents). So, if it works with Java 6, then why doesn't it work with Java 5?
How can I use the Java 6 JAXP in Java 5?
Thank you.

A new user name?
I can think of ways round your problem but can you first provide a reference that indicates that byte 0x80 is the MS936 encoding for the Euro?
P.S. This is a forum and the vast majority of participants, including me, have no direct relationship with Oracle so getting definitive answers from Oracle via this forum is unlikely. If you think you have found a bug in 1.5 and/or 1.6, and I am not convinced you have, you need to report it via the bug database. If it is a bug then the response time for a fix is likely to be months rather than days.
P.P.S No I can't explain why it works in 1.7!

XML Validation using java for SQL Injection and script validation

I have an input coming from xml file.
I have to read that input and validate the input against sql injections and scripts.
I require help now how to read this xml data and validate against the above two options.
I am a java developer.
in this context what is marshelling?

http://www.ibm.com/developerworks/library/x-javaxmlvalidapi.html?ca=dgr-lnxw07Java-XML-Val
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/validation/package-summary.html
The following code validates the xml against a xml schema
// define the type of schema - we use W3C:
String schemaLang = "http://www.w3.org/2001/XMLSchema";
SchemaFactory factory = SchemaFactory.newInstance(schemaLang);
Schema schema = factory.newSchema(new StreamSource("sample.xsd"));
Validator validator = schema.newValidator();
// at last perform validation:
validator.validate(new StreamSource("sample.xml"));Message was edited by:
haishai

Can SOA 11g fault policy handle XSD Validation errors from the Mediator?

I would like all errors in my SOA process to go through the fault-policies.xml. But I don't seem to be able to catch any mediator error caused by an XSD validation failure. A sample of the sort of error I am trying to 'catch' is:
Nonrecoverable System Fault          oracle.tip.mediator.infra.exception.MediatorException: ORAMED-01303:[Payload default schema validation error]XSD schema validation fails with error Invalid text 'A' in element: 'TermCode'Possible Fix:Fix payload and resubmit.
My fault-policies.xml file is as follows:
<?xml version="1.0" encoding="UTF-8" ?>
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<faultPolicy version="2.0.1"
     id="NewStudentRegistrationFaults"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:1303">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:rjm="http://schemas.oracle.com/sca/rejectedmessages" name="rjm:GetNewStudentRegistrationFile">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:TYPE_ALL">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:mediatorException">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:bindingFault">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:remoteFault">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="java-fault-handler">
<javaAction className="edu.villanova.soa.handlers.FaultNotificationHandler"
defaultAction="ora-human-intervention" propertySet="faultNotificationProps">
<returnValue value="OK" ref="ora-human-intervention"/>
</javaAction>
</Action>

<Action id="ora-human-intervention">
<humanIntervention/>
</Action>

<Action id="ora-terminate">
<abort/>
</Action>
</Actions>

<Properties>

<propertySet name="faultNotificationProps">
<property name="from">[email protected]</property>
<property name="to">[email protected]</property>
<property name="subject">Reporting a SOA fault</property>
</propertySet>
</Properties>
</faultPolicy>
<faultPolicy version="2.0.1"
     id="MediatorFaults"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:1303">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="java-fault-handler">
<javaAction className="edu.villanova.soa.handlers.FaultNotificationHandler"
defaultAction="ora-human-intervention" propertySet="faultNotificationProps">
<returnValue value="OK" ref="ora-human-intervention"/>
</javaAction>
</Action>

<Action id="ora-human-intervention">
<humanIntervention/>
</Action>

<Action id="ora-terminate">
<abort/>
</Action>
</Actions>

<Properties>

<propertySet name="faultNotificationProps">
<property name="from">[email protected]</property>
<property name="to">[email protected]</property>
<property name="subject">Reporting a SOA rejected msg. fault</property>
</propertySet>
</Properties>
</faultPolicy>
</faultPolicies>
My fault-bindings.xml file is as follows:
<?xml version="1.0" encoding="UTF-8" ?>
<faultPolicyBindings version="2.0.1"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<composite faultPolicy="NewStudentRegistrationFaults"/>
<component faultPolicy="MediatorFaults">
<name>NewStudentRegistrationMediator</name>
</component>
<service faultPolicy="NewStudentRegistrationFaults">
<name>GetNewStudentRegistrationFile</name>
</service>
</faultPolicyBindings>
You'll notice that I've tried a number of ways (and various other combinations) to try to steer the error above into my Java fault handler but nothing has meet with success. The mplan is as follows:
<?xml version = '1.0' encoding = 'UTF-8'?>

<Mediator name="NewStudentRegistationMediator" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.oracle.com/sca/1.0/mediator"
wsdlTargetNamespace="http://xmlns.oracle.com/pcbpel/adapter/ftp/Experiments/NewStudentRegistration/GetNewStudentRegistrationFile%2F">
<operation name="Get" deliveryPolicy="AllOrNothing" priority="4"
validateSchema="true">
<switch>
<case executionType="queued" name="RegToBanner.insert_2">
<action>
<transform>
<part name="$out.NewstudentregistrationCollection"
function="xslt(xsl/NewStudentRegistration_To_NewstudentregistrationCollection.xsl, $in.body)"/>
</transform>
<invoke reference="RegToBanner" operation="insert"/>
</action>
</case>
</switch>
</operation>
</Mediator>
I'm a newbie to Oracle SOA. So perhaps I am missing the obvious. But I haven't read much in the documentation specifically about using the XSD validation option on the mediator and have seen nothing specifically about catching this sort of exception in the fault policy (apart from the faults I already have in my policy). Can anyone suggest what I am doing incorrectly here or perhaps whether what I am attempting to do is not possible? Thanks.
- Cris

Has anyone got it working yet?
In my case, I have the following sequence:
FileAdapter -> Mediator1 -> Mediator2->DB Adapter
I am deliberately introducing validation error in File. Isn't it correct to assume Fault framework would get triggered at Mediator1 level since we are invoking FileAdapter service?
I am getting a strange behaviour. If I enable XSD validation at Mediator1 level, process is Faulted with no re-try option. However, if I enable XSD validation ONLY at Mediator2 level, I get Recoverable fault. There seems to be some disconnect between documentation and reality. I am using JDeveloper 11.1.1.3.0 version and SOA Suite 11g.
Thanks,
Amjad.

DOM validation using Java is extremely slow

I have a large XML file ~8MB. When I do validation on it using java api, takes ~5 hours to process it.
I have narrowed down the problem to xs:unique rules in the schema file. When I remove these rules, validation takes ~1 min.
I have tried using MSXML parser with unique rules and it take about 30 min.
My question is how could I speed up the validation in Java with these unique rules in the schema.
Any help will be greatly appreciated.
Thanks.

Basically, you are saying removing the unique elements
from schema and do the checking myself. This means
everytime the schema is updated with new unique rules,
I will have to modify the code to check for unique
elements.
Is there any other way to tackle this problem?You can choose what processing is done with the XML parser, and what is done within java, if you control the schema. Uniqueness is one that I have preferred to perform in java, since I often perform other validations in java anyway, and it works well. Just my opinion.
If you post some XML/XSD code and list the parser you are using, someone that uses xs:unique may find something they can help you with.
-Scott

XSD VALIDATION

Hi,
I have generated the DOM TREE and this dom tree need to pass through XSD Validate and then the generated (XML) is to go through the XSLT processor.
I need your suggestion how to go with after generating the DOM TREE.
Thanks.

Nice find, Ben. Thanks.
I've been using jUnit with the XML and XSD support in Java 5. Here's a link, if anyone is looking for a way to do XSD validation from within a Java program:
http://itunesu-api-java.googlecode.com/svn/branches/xsd-validation/src/test/edu/ asu/itunesu/XsdTest.java
Dave

XSD validation in ABAP

Hi folks.
Is it possible to validate a message using a XSD (in XI) using ABAP Classes / functions instead of JAVA (and BPM)? Like mandatory fields, field types, etc etc
Thanks in advance.
Best regards.
Valter Oliveira.

hey valter,
you can do that in any language you want.
The point is that you already have delivered java APIs for xsd validation (actually, xsd validation is performed as standard by compliant SAX/DOM parsers).
For ABAP, you'd probably need to develop this API from scratch.
The advantage of Java is not its speed or resource-consuming: it is just that everything is already developed on Java. lol
Regards,
Henrique.

XSD VALIDATION IN ABAP PROGRAM

Hi,
I have a requirement where in a report i am picking xml file from the presentation server (desktop) and then i am parsing the xml file using FM "SMUM_XML_PARSE" (first i use FM SCMS_BINARY_TO_XSTRING and then SMUM_XML_PARSE). after using the function SMUM_XML_PARSE i get the xml data in my internal table and then my report uses that data for some processing. This all is working fine .
My issue is that how do i do a XSD VALIDATION for the xml file that i am reading . I would have liked to do a xsd validation after i import the xml file and throw error if the xml file is not as per its xsd.As i am not using any middleware technology like XI/ WTX which have XSD validation functionality i am not sure how to achieve this in abap program.

Hi,
I think you're right, iXML can only validate DTD via its if_ixml_parser->set_validating method (you can find this information in SAP SDN article "ABAP XML Mapping", as of release 6.10, I couldn't find any other reference saying that xsi:noNamespaceSchemaLocation is supported since then).
By looking at SDN, I saw an external link about XSD to DTD conversion via XSLT (http://crism.maden.org/consulting/pub/xsl/xsd2dtd.xsl), but I don't have any idea if it works. On another thread, people used OS command to do XML/XSD validation, but didn't describe what they ran exactly (anyway, that means using any external tool).
Sandra

FTP Adapter XSD Validation

Hi All,
Oracle InterConnect 10.1.2
Oracle Adapters (AQ,FTP) using XSD
FTP Adapter on local filesystem
In the FTP Adapter, Is there anyway to validate the XML content against the XSD?
The validation is happening at the common view when i use the "Validate XML" check box while creating the event in iStudio. However this option does not appear while configuring the FTP adapter in iStudio. I would like FTP adapter to reject the XML file if the XSD validation fails and move the file to the exception folder.
Objective: XSD should perform datatype, datasize and format validations.
Thanks,
Sherry

Can anyone let me know how to enforce the XSD validation in the adapter. As of now only the structure of the message is being checked.

How to write validation in java sript item should not allow more than 20 ch

HI,
I need to write validation in java script for a item it should not allow more than 20 characters.
Thanks
Nr

If this answers your question, please mark your question as answered (so everyone knows it is answered) and assign points where you see fit..
Thank you,
Tony Miller
Webster, TX

Attributes missing after XSD validation!

I'm feeding a very simple XML file into an equally simple XSD validator. When it returns, all of my tags are fine, but the attributes are dropped. If I parse the file directly, without validation, the attributes are fine.
I've posted my files online at http://www.pastie.org/507569
Am I doing something wrong here? Is this a bug in my JRE (1.6.0r14)?
Thanks for any help,
Norman

XML
<config blah="5">hello!</config>
XSD
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd" />
<xs:element name="config">
   <xs:complexType>
    <xs:simpleContent>
     <xs:extension base="xs:string">
      <xs:attribute name="blah" type="xs:string"/>
     </xs:extension>
    </xs:simpleContent>
   </xs:complexType>
</xs:element>
</xs:schema>
My code...
SchemaFactory schema_factory = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);
Schema schema = schema_factory.newSchema(new File("test.xsd"));
StreamSource xml_source = new StreamSource(new File("test.xml"));
StringWriter xml_bridge = new StringWriter();
StreamResult xml_result = new StreamResult(xml_bridge);
Validator validator = schema.newValidator();
validator.validate(xml_source, xml_result);
System.out.println("Validated to: " + xml_bridge.toString());
Result...
Validated to: <?xml version="1.0" encoding="UTF-8"?><config>hello!</config>

XSD validation for incoming data into BPEL process

Please suggest how to validate XSD incoming data into BPEL process.
I just wanted to verify the data before entering into BPEL

Hi,
I guess i am replying very late.
In BPEL 2.0 we have an activity called "Validate" which can do the XSD validations.
"Lets Learn Oracle SOA: Validate XML schema In BPEL"
Regards,
Chinmaya

Schema Validation with Java and Document object

Hi, I am working on a project that will validate an xml Document object from a child class. I seem to have completed XSD validation with new DOMSource(doc) and using schema factory, which doesn't support DTD validation. And now I am attempting to validate the DTD. It seems like all the examples I've seen are trying to parse files, and I am struggling with finding a way to validate it directly against the document object.
The child class creates the xml document which is passed back to the parent class, and I need to do the validation in the parent class, so I need away to validate against the document object. This will be an assertion in Fitnesse if anyone is familar with it.
private void doSchemaValidationCommand(int rowCount, Document doc, String xpathExpression)
         String validationPath = getText(rowCount,1);
         String extensionSeparator = ".";
         Boolean error = false;
         String ext = null;
         try
         int dot = validationPath.lastIndexOf(extensionSeparator);
        ext = validationPath.substring(dot + 1);
         catch(Exception e)
              this.wrong(rowCount, 1, e.getMessage());
         if (ext.equalsIgnoreCase("xsd"))
         try {
         SchemaFactory factory =
            SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);
        File schemaLocation = new File(validationPath);
        Schema schema = factory.newSchema(schemaLocation);
        Validator validator = schema.newValidator();
        try {
            validator.validate(new DOMSource(doc));
        catch (SAXException ex) {
            this.wrong(rowCount, 1, ex.getMessage());
            error = true;
        catch (IOException ex) {
             this.wrong(rowCount, 1, ex.getMessage());
             error = true;
       catch (SAXException ex) {
           this.wrong(rowCount, 1, ex.getMessage());
           error = true;
       catch (Exception ex){
            this.wrong(rowCount, 1, ex.getMessage());
            error = true;
         else if (ext.equalsIgnoreCase("dtd"))
              try {
         }

I tried this but it doesn't give me any validation of whether or not it was completed successfully, it just adds a tag for the dtd to the xml and doesn't seem to do anything further with it, am I missing any steps?
else if (ext.equalsIgnoreCase("dtd"))
              try {
                   DOMSource source = new DOMSource(doc);
                   StreamResult result = new StreamResult(System.out);
                   TransformerFactory tf = TransformerFactory.newInstance();
                   Transformer transformer = tf.newTransformer();
                   transformer.setOutputProperty(OutputKeys.DOCTYPE_SYSTEM, validationPath);
                   transformer.transform(source, result);
              catch(Exception e)
                   this.wrong(rowCount, 1, e.getMessage());
                   error = true;
         }Edited by: sarcasteak on Apr 13, 2009 1:33 PM

XSD validation with multiple namespaces

Hi All,
I'm trying to validate some XML using an XSD that contains multiple namespace schema descriptions, as such, the main XSD file must import an XSD for each namespace.
The difficulty is that I cannot seem to find a way (in Oracle) to run a XSD validation using this (multi-XSD file) method.
Has anyone out there tackled a similar problem?
Cheers,
Ben

check out the class
CL_XML_SCHEMA
Regards
Raja

XSd-validation isn't performed when invoking file Adapter

I've configured an ESB where data needs to be transformed using a file adapter and a db adapter.
The deleimted files first need to be validated using xsd (native transformation) and if validation was performed correctly they can be transformed and loaded into db tables.
The xsd-validation isn't performed in my use case where some fields are required, have a decimal-format etc., if the files don't comply they're still picked up and being transformed to the db adapter, where the insertion will fail then because the file had errored records in it.
I'm using esb 10.1.3.3 in this case.
kind regards,
Nathalie

Hi Nathalie,
I'm not able to define properties on my esb routing
service in release 10.1.3.3, the definition tab isn't
showing any detailed information for my routing
service.Strange, we're also using 10.1.3.3. Make sure in the ESB Control when you select the routing service, that the operation for which you want to validate the payload is selected. If it is selected, the operation details section should show the validation option. Also see page 3-14 of the ESB Developers Guide. You can also change the esbsv-file:
<operations>
<operationInfo guid="xyz" qname="Test.Insert.insert" wsdlOperation="insert" mepDisplayName="One Way" mep="OneWay">
<request validate="true" xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/d
b/top/Insert" element="tns:TestCollection"/>
</operationInfo>
</operations>
</service>
using the validate="true" option.
No logging is being generated for this matter, so I'm
not sure which problem I'm facing wright now. I will
bounce the service and try again.We had such an issue when we didn't validate payload at runtime and inserted data using DB adapter. Our TopLink mappings didn't correspond to the XML data to be inserted. That caused only 2 tables out of 4 to be updated, without any error logged. Enabling validation, resulted in an error being thrown; the behaviour we wanted.
The only thing that's of importance here, is that I
need to define this functionality within BPEL and not
ESB, the customer has only acquired bpel for this
matter because human task integration was necessary.One of the advantages of 11g fortuntely is that separation of concerns will be better. It will be much clearer where to use adapters. Not that this helps in your current case right now :-s
I should be able to accomplish the xsd validation
inside a bpel configuration.That should work, good luck!
Regards, Ronald

Xsd validation in java

Similar Messages

Maybe you are looking for