WO2012100681A1

WO2012100681A1 - Data verification method and device

Info

Publication number: WO2012100681A1
Application number: PCT/CN2012/070268
Authority: WO
Inventors: 姚博
Original assignee: 北京京东世纪贸易有限公司
Priority date: 2011-01-26
Filing date: 2012-01-12
Publication date: 2012-08-02
Also published as: CN102103639A

Abstract

Provided are a data verification method and device. The data verification method can include: receiving information to be verified; constructing a verification object using the received information to be verified; acquiring a verification rule configuration file corresponding to the verification object; and verifying the verification object using the acquired verification rule configuration file. The data verification method and device according to the present invention improve the reusability and maintainability of verification.

Description

Data verification method and device

The present invention relates to a data verification method and apparatus. Background technique

In the field of network related technologies, it is often necessary to verify information input by a user. In the common information verification method, each field that needs to be verified is performed one by one. For example, when it is judged that there are three fields A, B, and C that need to be verified, the verification method A is used to verify the field A, then the verification method B is used to verify the field B, and finally the verification method C is used to verify the field C. Therefore, when several fields need to be verified, a large number of verification methods need to be maintained in the day after tomorrow, resulting in an increase in maintenance costs. In the above verification method, a multi-branch verification process is adopted. The more fields, the more branches, the more verification methods the system needs to maintain. The system becomes bloated and difficult to maintain, and it is difficult to scale and is not efficient. In order to overcome the problems of the above verification method, the application number is CN

A data verification method is disclosed in the patent application of 200810227933.9 to improve maintainability and scalability. In the method disclosed in the patent application No. CN 200810227933.9, a unified verification label and a unified verification interface are used to implement a unified data verification mechanism. The method first uses the unified verification tag isNameExist to identify all the fields that need to be verified for data repetitiveness, and then obtains a unified verification interface of the field that needs to be repetitively verified, and invokes the verification rule corresponding to the unified verification interface to perform data repeatability. Verify the fields for verification. However, in the above verification method, the following main problems still exist. First, since a unified authentication interface is used for multiple fields, the most suitable verification rule cannot be used for each of the multiple fields. For example, there may be many field information named name in each verification, but each A verification logic is not identical, so it is difficult for the unified authentication interface to use the most appropriate validation rules for these field information. Second, the method still calls the unified verification interface for each field that needs to be verified by referring to the unified verification label, thereby reducing the verification efficiency. Summary of the invention

The present invention has been made in order to solve the above disadvantages and problems in the prior art.

According to an aspect of the present invention, a data verification method is provided, and the method may include:

Receiving information to be verified;

Constructing a verification object by using the received information to be verified;

Obtaining a validation rule configuration file corresponding to the verification object;

The verification object is verified using the obtained verification rule configuration file. According to this aspect of the invention, the verification rule configuration file may include a plurality of verification rules, one or more of the plurality of verification rules being associated with an attribute of the verification object. The plurality of verification rules may include a default verification rule and a custom verification rule. Further, when the verification of the verification object fails, an error message can be output. The error message may be derived from the verification rule profile. According to another aspect of the present invention, a data verification apparatus is provided, and the apparatus may include:

a verification data input unit, configured to receive information to be verified;

a verification object construction unit, configured to receive the to-be-verified information submitted from the verification data input unit and construct a verification object by using the to-be-verified information;

a verification rule setting unit for maintaining at least one verification rule profile; a verification unit, configured to acquire, from the verification rule setting unit, a verification rule configuration file corresponding to the verification object constructed by the verification object construction unit, and perform the verification object on the verification object by using the acquired verification rule configuration file verification. According to this aspect of the invention, the verification rule configuration file may include a plurality of verification rules, one or more of the plurality of verification rules being associated with an attribute of the verification object. The plurality of verification rules may include a default verification rule and a custom verification rule. Furthermore, the data verification apparatus may further include a verification result processing unit, and output error information when the verification unit fails verification of the verification object. Moreover, the error information is derived from the verification rule profile. DRAWINGS

The above and other aspects, features, and advantages of some exemplary embodiments of the present invention will become apparent to those skilled in the <

1 is a block diagram illustrating a data verification apparatus in accordance with the present invention;

2 is a schematic diagram illustrating a verification profile for a data verification device in accordance with the present invention;

3 is a flow chart illustrating a data verification method in accordance with the present invention. detailed description

The following description of the drawings is provided to provide a comprehensive understanding of the exemplary embodiments of the invention. It includes various details to assist in understanding, and should be considered as merely exemplary. Therefore, it will be apparent to those skilled in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness. The invention will be described in detail below with reference to the accompanying drawings. 1 is a block diagram illustrating a data verification apparatus in accordance with the present invention. As shown in FIG. 1, the data verification apparatus includes a verification data input unit 110, a verification object construction unit 120, a verification unit 130, and a verification rule setting unit 140. The verification data input unit 110 can generate a graphical user interface for inputting verification information. The generated graphical user interface may include a plurality of fields for the user to input various information. Taking the user registration as an example, the verification data input unit 110 may generate a user registration page, and the user registration interface may include a user name, a password, a mailbox, and a verification. Fields such as codes. After the user inputs various information to the graphical user interface, the verification data input unit 110 may submit the input various information to the verification object construction unit 120. In the above-described user registration example, after the user inputs various information to the user registration interface, the input various information may be submitted to the verification object construction unit 120 by clicking the "register" button on the user registration interface. Upon receiving the information submitted by the self-verification data input unit 110, the verification object construction unit 120 constructs the verification object based on the received information, for example, by setting the information input in each field as the attribute value of the corresponding attribute of the verification object. Build a verification object. The verification unit 130 is configured to verify the verification object constructed by the verification object construction unit 120. The verification unit 130 may acquire a verification rule profile corresponding to the constructed verification object from the verification rule configuration unit 140. The verification rule configuration unit 140 may maintain at least one verification rule configuration file, where the at least one verification rule configuration file corresponds to the verification object by using the file name. Further, each verification rule configuration file may include a plurality of verification rules, one or more of the plurality of verification rules being associated with an attribute of the verification object, and then a plurality of verification rules will be described in detail with reference to FIG. How one or more of the ones are associated with an attribute of the verification object. The verification unit 130 may acquire the verification rule configuration file corresponding to the constructed verification object from the verification rule configuration unit 140 in various manners, for example, the verification rule configuration file corresponding to the constructed verification object may be acquired according to the following code example. : <bean id= "formService " class= "com.jd. website, commons, validator. DefaultFormService ">

<list>

<!- configuration file —>

<value>form/registerForm.xml</value>

</list>

</property>

</bean>

Wherein, the verification object name is indicated by id=7 r SerWce ", and the verification rule configuration file corresponding to the verification object is indicated by form/registerForm.xml. Of course, the verification unit 130 acquires and constructs from the verification rule configuration unit 140. The verification rule configuration file corresponding to the verification object is not limited to the above manner. After the verification rule configuration file is acquired, the verification unit 130 performs the verification rule set for each attribute of the verification object in the verification rule configuration file (refer to FIG. 2 below) Description) Verifies the verification object and outputs the verification result. For example, when the verification object is successfully verified, the verification result can be "true", and when the verification object fails to be verified, the verification result can be verification error information, the verification The error information may be from a verification rule configuration file. The data verification device may further include a verification result processing unit 150 that processes according to the verification result from the verification unit 130. For example, when the verification is successful, other processes may be continued, such as registration at the user In the example, Go to the interface that only allows registered users to view; When the verification fails, you can output verification error information, for example, the verification error message as the verification result is twice rendered and then rolled back to the front end and displayed error message. Describe the verification profile. Figure 2 illustrates a schematic diagram of a verification rule profile for a data verification device in accordance with the present invention. The piece includes a configuration block 1 - configuration block 4 for configuring a corresponding verification rule for each attribute of the verification object. Configuration block 1 sets the authentication rule I" associated with the attribute "name" of the verification object, where ^(^(^ required="trwe'^ put the attribute cannot be empty, pass

<validator minLength= "4 " maxLength= "20 ">Set the attribute to be longer than 4 digits and less than 20 digits. Configuration block 2 sets the authentication rule I" associated with the attribute "password" of the verification object, where ^(^(^ required="trwe'^ put this attribute cannot be empty, passed

<validator minLength=" " maxLength='76">Set the length of this attribute must be greater than 6 digits and less than 16. The configuration block 3 sets the validation rules associated with the authentication object's attribute "email", where <validator required = "trwe ">Set this property to be empty, pass

<validator maxLength="W>Set the length of this attribute must be less than 50 characters, via < validator

Set the regular expression validation for this property. Configuration block 4 sets the authentication rule associated with the attribute "checkCode" of the verification object, where ^(^(^ required="trwe'^ put the attribute cannot be empty, passing <validator

Type= "com.jd. website, apply, web. validator. CheckCode Validator ">Set up custom validation of this property (described in more detail later). In addition, configuration block 1 - configuration block 4 defines an error message to be output when the verification fails by the "message" node, where "${displayName}" corresponds to the name of the attribute. As can be seen from the above description, the verification rule for each attribute of the verification object is passed.

The "type" attribute in the "validator" node is set. In the present invention, four default validators (equivalent to the meaning of the validation rules) are used as follows:

When it is not appropriate to use any of the above four default validators, a custom validator can be used, such as the custom validator used in configuration block 4 above. The custom validator can be arbitrarily defined as needed. The following example is a custom validator that defines the validation rules used in configuration block 4:

Package com.jd.website.apply.web.validator;

Import org. apache. commons. lang.StringUtils;

Import com.jd.website. commons. validator. check. DefaultValidator; import com.jd.website. commons. validator. form. Field;

Public class CheckCodeValidator extends DefaultValidator { private final static String CHECK_ CODE = "8888";

@Override

Protected boolean validator(Field field) {

String value = fleld.getStringValue();

If (StringUtils.isNotBlank(value) && StringUtils. equals (CHECK_ CODE, value)) {

Return true; Return false;

}

} The example above defines a custom validator CheckCodeValidator that only accepts the verification code " 8888 ". Other custom validators can be defined in a similar manner. In addition, in order to increase the applicability, flexibility, and the like of the verification configuration rule, the configuration of the verification rule for the similar verification object can be implemented by the inheritance method. For example, in the above user registration example, if you need to add the verification item "age" and the verification logic of other verification items remains unchanged, you can do so by:

<?xml version= "1.0" encoding= "GBK"7>

<forms>

<!-- Registration — >

<message>$ {displayname} won't be ^; empty! </message> </validator>

</field>

</form>

</forms> As can be seen from the above description, the data verification apparatus according to the present invention defines the verification rules associated with each attribute of the corresponding verification object in detail by the verification rule configuration file. First, since one or more validation rules are associated with each attribute, the most appropriate validation of each attribute of the verification object can be performed. In addition, when changes need to be verified For logic, you only need to change the validation rules in the configuration file. Third, when there are multiple registration entries, you only need to reuse the configuration file. Therefore, the reusability and maintainability of the verification are improved. A data verification method according to the present invention will be described below with reference to FIG. 3 is a flow chart illustrating a data verification method in accordance with the present invention. At step S310, information to be verified is received. The information to be verified may be information entered by the user in each field of the graphical user interface. The specific process can refer to the description about the verification data input unit 110. At step S320, the verification object is constructed using the received information to be verified. For example, the verification object can be constructed by setting the information input through each field of the graphical user interface to the attribute value of the corresponding attribute of the verification object. At step S330, a verification rule profile corresponding to the constructed verification object is obtained. For example, the verification rule configuration file corresponding to the verification object can be obtained by verifying the file name of the rule configuration file. As previously described, each validation rule profile can include a plurality of validation rules, one or more of which are associated with an attribute of the verification object. The specific process can refer to the description about the verification rule configuration unit 140 and FIG. At step S340, the verification object is verified using the acquired verification rule profile. The specific process can refer to the description about the verification unit 130 and FIG. 2. At step S350, processing is performed based on the verification result. For example, when the verification is successful, other processes can be continued, for example, in the user registration example, it can be transferred to an interface that only allows registered users to view; when the verification fails, verification error information can be output, for example, verification as a verification result. The error message is rolled back to the front end after the second rendering and an error message is displayed. It should be noted that the apparatus and method embodiments of the present invention have been described above separately, but the details described for one embodiment are also applicable to another embodiment. The basic principles of the present invention have been described above in connection with the specific embodiments, but it should be noted that those skilled in the art can understand that all or any of the steps or components of the method and apparatus of the present invention may be in software, hardware, or The firmware or a combination thereof is implemented, which can be accomplished by one of ordinary skill in the art using their basic programming skills while reading the description of the present invention. Accordingly, the objects of the invention may also be realized by running a software module or a set of software modules on any computing device. The computing device can be a well-known general purpose device. Accordingly, the object of the present invention can also be achieved by merely providing a program product comprising program code for implementing the method or apparatus. That is to say, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. Obviously, the storage medium may be any known storage medium or any storage medium developed in the future. The description contains many specific details of the invention, and should not be construed as a limitation of the scope of the invention. Certain features that are described in this specification in the context of separate embodiments can also be implemented in a single embodiment. Conversely, various features that are described in the context of a single embodiment can be implemented separately in various embodiments or in any suitable subcombination. Moreover, although features may be described above as being functional in certain combinations, even initially claimed, in some cases one or more features from the claimed combination may be deleted from the combination and may be The claimed combination points to a sub-combination or a variant of a sub-combination. Similarly, although the operations are depicted in a particular order in the figures, this should not be understood as requiring that such operations be performed in the particular order shown or in a sequential order, or that all illustrated operations may be performed to achieve the desired. result. In some cases, multiple And parallel processing can be advantageous. Moreover, the separation of the various system components in the above-described embodiments should not be understood as requiring such separation in all embodiments, but it should be understood that the described program components and systems can generally be integrated together. A single software product or packaged into multiple software products. A computer program (also referred to as a program, software, software application, script, or code) can be written in any form of programming language, including a compiled or interpreted language, or an illustrative or procedural language, and which can be deployed in any form , included as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. The computer program does not necessarily correspond to the files in the file system. A program can be stored in a file that holds other programs or data (for example, one or more scripts stored in a markup language document), a single file dedicated to the program under discussion, or multiple coordination files (for example, storing one Or multiple modules, subroutines, or partial code files). The above specific embodiments do not constitute a limitation of the scope of the present invention. Those skilled in the art will appreciate that a wide variety of modifications, combinations, sub-combinations and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

A data verification method, the method comprising:

Receiving information to be verified;

The verification object is verified using the obtained verification rule configuration file.

2. The method of claim 1, wherein the verification rule configuration file includes a plurality of verification rules, one or more of the plurality of verification rules being associated with an attribute of the verification object.

3. The method of claim 2, which

Validation rules and custom validation rules.

4. The method of claim 1 wherein

In the event of a loss, an error message is output.

5. The method of claim 4, wherein the error information is derived from the verification rule configuration file.

6. A data verification device, the device comprising:

a verification rule setting unit, configured to maintain at least one verification rule configuration file; and a verification unit, configured to acquire, from the verification rule setting unit, a verification rule configuration file corresponding to the verification object constructed by the verification object construction unit And verifying the verification object with the obtained verification rule configuration file.

7. The apparatus of claim 6, wherein the verification rule configuration file comprises a plurality of verification rules, one or more of the plurality of verification rules being associated with an attribute of the verification object.

8. The apparatus according to claim 7, wherein the plurality of verification rules include a default verification rule and a custom verification rule.

9. The apparatus according to claim 6, wherein the data verification apparatus further includes a verification result processing unit, and when the verification unit fails the verification of the verification object, the error information is output.

10. The apparatus of claim 9, wherein the error information is derived from the verification rule configuration file.