Java dependency injection standard (JSR-330) Introduction
Reprinted by the author:
By: 88250, Vanessa
Time: January 1, November 19, 2009
Java dependency injection standard (JSR-330, dependency injection for Java) 1.0 specification was released in October this year. This specification is intended for dependency injection users, but does not have detailed requirements on the Implementation and configuration
JSR 299 canonical leader Gavin King yesterday submitted a draft of JSR-299 's final proposal to JCP. The JSR 299 Expert Group will release the final specification in August this year (the Java EE 6 specification will be released in September). If you are very concerned about this specification, please update the specification document now, download here.
One:JSR 303 is a sub-specification in Java EE 6, called the Bean Validation, and the official reference implementation is Hibernate Validator, which has nothing to do with hibernate ORM. JSR 303 is used to validate the value of a field in a Java bean.This tutorial is translated from the Hibernate Validator 4.0 GA guide, and reference to the JSR 303 specification, with the exception of the
Used to know, JSR310 the time API is really artifact, greatly facilitates the process of time operation in Java.
The JSR 310 specification Leader Stephen Colebourne is the Joda-time author, whose main idea is to learn from Joda-time, instead of directly porting Joda-time to the Java platform, the API is similar but has been improved, For specific improvements please refer to one of its 2009 articles and Infoq's interview with him:
Http://
REST: Representational state delivery (English: Representational, Transfer, or rest) is a distributed Application architecture style and a design methodology for large-volume distributed applications.
JSR is the abbreviation for Java specification requests, meaning Java specification proposal. is a formal request to JCP (Java Community Process) to propose a new standardized technical specification. Anyone can submit a
At any time, when it comes to dealing with the business logic of an application, data validation is something you have to consider and face.The application must have some means to ensure that the input parameters are correct in context.Layered applications In many cases, the same data validation logic will appear on different tiers, which can lead to code redundancy and some management issues.To avoid this or that situation, it is best to bind the validation logic to the corresponding data model
Introduction: This paper introduces the Java Rule Engine and its API (JSR-94) and related implementation in detail, describes its architecture and API application, and points out the relationship between Java Rules Engine, rule language, JSR-94, and the deficiencies and prospects of JSR-94.
The development of complex enterprise-level projects, as well as the bus
Document directory
1.3 default binding
2.1 built-in Scope
Java context and dependency injection (JSR 299) [1]
Reprinted by the author:By: 88250Blog: http:/blog.csdn.net/dl88250MSN Gmail QQ: DL88250@gmail.com
Summary
This article starts with the JSR 299 specification, sorts out and translates very important concepts in this specification, and describes the use of
Java Context and Dependency injection (JSR 299) [1]Reprint please retain the author information:
Author: 88250
blog:http:/blog.csdn.net/dl88250
MSN Gmail qq:dl88250@gmail.com
SummaryStarting with the JSR 299 specification, this paper collates and translates the very important concepts in the specification and describes the use of JSR 299 in terms of short e
JSR 303 is the standard framework that Java provides for the validation of the bean data, which is already included in EE 6. 0. JSR303Specify a validation rule by annotating annotations on bean properties that are similar to @notnull, @Max, and so on, and validate the bean with a standard authentication interface:---------------------------------------------------------------------------Annotation Description-------------------------------------------
In the project, most of the front-end checks are used, such as the JS check in the page and the form form using the bootstrap checksum. However, for higher security requirements, it is recommended to verify on the service side.Service-side check:
Control Layer Controller: Verifies the legality of the parameters requested by the page. In the server-side control layer controller checksum, the client type is not distinguished.
Business Layer Service (use more): Mainly check the key bus
Download JSR 303-bean validation specification http://jcp.org/en/jsr/detail? Id = 303
Hibernate validator is a reference implementation of bean validation. hibernate validator provides all built-in constraint implementations in the JSR 303 specification, in addition to some additional constraint. For more information about hibernate validator, see the http://www.
JSR 207 Java Process Definition for Java aims to explore and standardize the relationships between Process Languages (such as BPEL), Java languages, and J2EE platforms. Java Process Definition (JSR 207) defines a more advanced programming model that allows developers to write business processes. Its Standardization is very encouraging, it can improve the abstract level of enterprise-level application develo
Js
Content Repository API (JSR-170) posts Final Draft
The JSR-170 Expert Group submitted the final draft of the JSR specification for Java Content Repository (JCR), which JCR the specification of "content services", such as based on the author's version, Full-text search, excellent authorization access control, content classification, and content event monitori
In a Web application, it is necessary for the user to submit form data in order to ensure the validity of the data, and the validation of the foreground client, such as JavaScript, is not always secure and reliable, so we need a robust background validation framework to handle this problem. Fortunately, Java has released the JSR-303 interface standard, and there are many vendors that implement this standard, and the Hibernate Validator Verification fr
the specified format, interger Specifies the integer precision, fraction specifies the decimal precision.The @Range (min=, max=) checks whether the number is between Min and Max.@Range (min=10000,max=50000,message= "Range.bean.wage")Private BigDecimal wage;The @Valid recursively verifies the associated object, and if the associated object is a collection or an array, the element is recursively checked, and if it is a map, the value part of it is verified. (whether recursive validation is perfor
The following provides a SPRINGMVC calibration scheme, generally no calibration or manual write validator words have to write a lot of code a lot of if judgment, using JSR-303 specification check only need to add the corresponding annotations on the Pojo field to achieve the verification1. Dependent jar package, I paste the pom directly2.SPRINGMVC Configuration3. Write the Java codeBuild a user class firstpublic class User {@NotNullprivate string user
About Bean Validation The JSR 303-bean Validation is a sub-specification in Jree6, and theJSR 303-bean Validation focuses on the following practical issues: At any time, when you are dealing with the business logic of an application, data validation is something you have to consider and face. The application must have some means to ensure that the input data is semantically correct. In the usual case, the application is layered and different layers
Today, Red Hat submitted the final draft of JSR-299To JCP. JSR-299 specification (CDI) (contexts and dependency injection, context and dependency injection), at the same time, the reference implementation of this specification (weld 1.0)
) And TCK (compatibility test suite) have also been completed. To view the javadoc of this specification, click here
.
This specification defines a series of complemen
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.