Oracle SOA Suite 11g offers multiple validation options. By carefully using these options at appropriate places, we can perform validations without compromising on performance.
XSD Validation: This is the most basic form of validation. When enabled, XML elements are verified against their corresponding XSD schema definitions. XSD validation can be performed at Mediator or BPEL component level. Element type and size are two checks that are normally performed using this type of validation.
Since XSD validation is built into the schema, service clients will have an opportunity to understand the validation constraints imposed by the service.
Schematron: is a XML based content validation language that can be used to build business rules. We can selectively validate only required elements of a XML document, as opposed to the entire document in case of XSD validation. Further, we can use XPATH functions to avoid verbose logic.
Mediator offers out-of-the-box support for Schematron rules. In case of BPEL, we can either route the request through a mediator or create an external service that can be invoked by BPEL.
Schematron rule repository can be used across all SOA artefacts by making it part of MDS. Also, it helps us to separate out validations from business logic. Since is a very light weight validation engine, performance is not compromised.
Business Rules is an acquired product from Haley. This provides a GUI to build and execute rules. Rules Engine is java based and hence can easily be invoked as an external webservice, if required. BPEL has out-of-the-box support for embedding business rules.
In simple terms, Schematron can perform all validations that Oracle Business Rules can perform. Though Business Rules approach may be slightly less efficient compared to Schematron, graphical interface provides an easy way to build rules.
There may be cases when we will have to build validation logic into the application. For example, if validation is performed by an external service, we’ll have to invoke this service from composite to validate our content.
XSD Validation: This is the most basic form of validation. When enabled, XML elements are verified against their corresponding XSD schema definitions. XSD validation can be performed at Mediator or BPEL component level. Element type and size are two checks that are normally performed using this type of validation.
Since XSD validation is built into the schema, service clients will have an opportunity to understand the validation constraints imposed by the service.
Schematron: is a XML based content validation language that can be used to build business rules. We can selectively validate only required elements of a XML document, as opposed to the entire document in case of XSD validation. Further, we can use XPATH functions to avoid verbose logic.
Mediator offers out-of-the-box support for Schematron rules. In case of BPEL, we can either route the request through a mediator or create an external service that can be invoked by BPEL.
Schematron rule repository can be used across all SOA artefacts by making it part of MDS. Also, it helps us to separate out validations from business logic. Since is a very light weight validation engine, performance is not compromised.
Business Rules is an acquired product from Haley. This provides a GUI to build and execute rules. Rules Engine is java based and hence can easily be invoked as an external webservice, if required. BPEL has out-of-the-box support for embedding business rules.
In simple terms, Schematron can perform all validations that Oracle Business Rules can perform. Though Business Rules approach may be slightly less efficient compared to Schematron, graphical interface provides an easy way to build rules.
There may be cases when we will have to build validation logic into the application. For example, if validation is performed by an external service, we’ll have to invoke this service from composite to validate our content.
No comments:
Post a Comment