Validation « Development « Java Articles

1.	Build Deploy
2.	Class
3.	Core Library
4.	Data Types
5.	Database JDBC
6.	Design
7.	Development
8.	File Input Output
9.	Graphics Desktop
10.	J2EE Enterprise
11.	J2ME Wireless
12.	JVM
13.	Language
14.	Library Product
15.	Network
16.	Security
17.	SOA Web Services
18.	Test
19.	Web Development
20.	XML

Java Articles » Development » Validation

1. Validation with pure Java javaworld.com

The logic behind constrained properties in Java is quite simple. Before accepting a new data value, the object (owner of the constrained property) makes sure it is accepted by all interested parties that may veto it. Such a "request for approval" is delivered to every registered java.beans.VetoableChangeListener in the form of a java.beans.PropertyChangeEvent object. If one or more vetoes have been issued, the proposed data value is rejected. A veto is presented by a java.beans.PropertyVetoException. Generally speaking, the complexity of the rules enforced by those listeners has no limit and depends only on the project's requirements and the developer's creativity. The objective of this exercise is to learn how to deal with the most generic data-validation criteria that you can apply to most objects.

2. Implementing Validation Rules using Aspects today.java.net

Before we get into the details of a validation framework and its implementation using rules engine and aspects, let's compare the traditional way of implementing data validation in a Java EE application to an aspect-oriented data validation. The following table lists the steps involved in implementing data validation in a typical application.

3. Java validation with dynamic proxies ibm.com

In this article, I'll show you a more decoupled and centralized approach to validation, using the dynamic proxy facility introduced to the Java platform with version 1.3. Working with a single example throughout the article, I'll demonstrate the weaknesses of both tightly coupled and loosely coupled validation schemes, and then show you how dynamic proxies can help you improve on both.

4. The Java XML Validation API ibm.com

Until recently, the exact Application Programming Interface (API) by which programs requested validation varied with the schema language and parser. DTDs and XSD were normally accessed as configuration options in Simple API for XML (SAX), Document Object Model (DOM), and Java? API for XML Processing (JAXP). RELAX NG required a custom library and API. Schematron might use the Transformations API for XML(TrAX); and still other schema languages required programmers to learn still more APIs, even though they were performing essentially the same operation.

5. IBM Cognos SDK Validation tool ibm.com

The IBM Cognos Validation tool was developed using the IBM Cognos 8 and IBM Cognos ReportNet Java SDK to validate reports in the Content Store. Two separate versions are available, one for IBM Cognos 8 and one for IBM Cognos ReportNet. Using this tool, you can automate the process of manually validating reports through the Report Studio user interface.

6. Advanced XML validation ibm.com

Grammar-based validation languages, such as XML Schema and DTD, are well equipped to ensure that XML documents conform to a well-defined message structure. This ensures that incoming XML messages can be processed correctly by the receiving applications, but it does not ensure that the data contained in the messages is valid. The limitations of grammar-based validation languages mean that, for example, you have to validate co-occurrence constraints and constraints against variable and external data sets using different methods.