Projects tagged ‘java’ and ‘validator’

A common issue when receiving data either electronically or from user input is verifying the integrity of the data. This work is repetitive and becomes even more complicated when different sets of ... [More] validation rules need to be applied to the same set of data based on locale. Error messages may also vary by locale. This package addresses some of these issues to speed development and maintenance of validation rules. [Less]

OVal is a pragmatic and extensible validation framework for any kind of Java objects (not only JavaBeans). Constraints can be declared with annotations (@NotNull, @MaxLength), POJOs or XML. ... [More] Custom constraints can be expressed as custom Java classes or by using scripting languages such as JavaScript, Groovy, BeanShell, OGNL or MVEL. Besides field/property validation OVal implements Programming by Contract features by utilizing AspectJ based aspects. This for example allows runtime validation of method arguments. [Less]

DataCleaner is an Open Source application for profiling, validating and comparing data. These activities help you administer and monitor your data quality in order to ensure that your data is useful ... [More] and applicable to your business situation. DataCleaner is the free alternative to software for master data management (MDM) methodologies, data warehousing (DW) projects, statistical research, preparation for extract-transform-load (ETL) activities and more. [Less]

lindbergframework - simple solutions to problems of day-to-day --- English lindbergframework is a framework for provides simple solutions to several problems types. The lindbergframework´s ... [More] objective is centralize several solutions in one place. The beginning of the project is recent and so far was available only a solution for automated validations. lindbergvalidation - Solution for Automated Validations Is a solution developed to remove the redundant validations code and isolate the logical these validations allowing a smaller code, more clean and more readable. This solution is very flexible and allows that the way is made each validation and the validation messages is highly personalized. lindbergvalidation contains several validations default like required field, field not null, date validations, list validations, CPF, CNPJ, among other. The developer can also implement their own validations using or not lindberg validations default. -- Português lindbergframework é um framework que provê simples soluções para vários tipos de problemas. O objetivo do lindbergframework é centralizar diversas soluções em um único lugar. O ínicio do projeto é recente é até o momento apenas foi disponibilizada a solução para automação das validações. lindbergvalidation - Solução para Automação de Validações É uma solução desenvolvida para remover os códigos de validações redundantes e isolara lógica dessas validações permitindo um código menor, mais limpo e mais legível. Essa solução é muito flexível e permite que a forma como são feitas as validações e as mensagens das validações sejam altamente personalizadas. lindbergvalidation contém várias validações por padrão como campo requerido, campo não nulo, validações de data, validações de lista, CPF, CNPJ, entre outras. O desenvolvedor porde também implementar suas próprias validações usando ou não as validações pre-definidas do lindberg. [Less]

This is one of the first implementations of JSR 303 (Bean Validation), a specification of the Java API for JavaBean validation in Java EE and Java SE. The technical objective is to provide a class ... [More] level constraint declaration and validation facility for the Java application developer, as well as a constraint metadata repository and query API. This implementation is based on the validation framework of agimatec GmbH, that is in production since 2007 and offers additional features, like XML-based extensible metadata, code generation (JSON for AJAX applications), JSR303 annotation support. For more information refer to the Wiki at Overview or contact us. Dependencies, API documentationJSR303 specification agimatec-validation - Maven-site with dependencies agimatec-validation - JavaDoc agimatec-jsr303 - Maven-site with dependencies agimatec-jsr303 - JavaDoc [Less]

Full Hibernate Plugin 2.0 Beta Released (21 oct 2009)(Release Notes page) Hibernate Validator integrationDRY - Don't Repeat Yourself! This feature allow the use of the fantastic Hibernate ... [More] Validator Framework with very simple use of annotations in your Actions. More about Hibernate Validator at http://www.hibernate.org/412.html Hibernate Core Sessions injection capabilityThe Open Session in View pattern made easy This feature provides an Interceptor that open and sets in the value stack a Hibernate Core Session and closes (or not) this after the results are rendered for the client. No code lines need to be added to manage Hibernate sessions in Struts 2 projects. Only some XML (or .properties) lines needed. This feature follows the concepts in http://www.hibernate.org/43.html Important! hibernatesession-plugin-for-struts2 users: You are strongly encouraged to migrate for this plugin! Hibernate Transactions injection capabilityTransactions by request This feature provides an Interceptor that opens and sets in the value stack a Transaction and commit this after the results are rendered for the client if a rollback method was not invoked. You can configure multiple databases (2.0+). No code lines need to be added to manage Hibernate sessions in Struts 2 projects. Only 01 (one) XML (or .properties) line needed. Hibernate Core configuration management Web ToolManage and reload your Hibernate Core configurations without reload your web content This feature provides an WEB front-end tool for view and reload your Hibernate Core configurations. You can provide this tool in your context in a public way or protect this by 2 ways: IPs/Hosts list or HTTP Autentication. [Less]

Simple, configurable utility for filtering unwanted html markup entered by a user that could be used to perform a cross-site scripting attack.

Struts validator using struts validator plugin

What is GWT? The recent buzzword around Java world is GWT, the Google Web Toolkit. The backbone of GWT is Ajax, which is not something new. The thing makes GWT unique is its tools that makes web ... [More] application development with Ajax a snap. Java developers no longer need to deal with html code(jsp code) and javascript code. Instead,they stay in their comfortable zone, writhing Java code only, for both client side and server side. GWT compiles the client side Java code to javascript, that makes your web application an Ajax application. Whenever user clicks on web page, the javascript code in the browser issues a light-weight RPC call to server and page refreshes only the part needs to. What is missing? Sounds great? Kind of. It is great from user’s point of view. It is not so great if you think of the security the current GWT implementation provides. GWT provides client side API for basic user input validation but nothing for server side. The client side API can do only basic check including mandatory check,length check and syntax check. That is enough for some but not for all applications. Some applications need more complicated validation like dependency check among input fields, a business-logic based check needs to hit database. These types of validation can’t be done in client side. Experienced developers also know that you can’t depend on client side validation and assume everything from client is valid. Because an attacker could easily bypass javascript check and submit a RPC call with invalid data. Sure enough, the individual (server side)service method can do validation itself, but it is not desirable because it puts validation burden and flow control on service. What we need here is a server side validation framework. A robust GWT application should be able to do both client side validation and server side validation. The client side validation is good because it reduces the number of the round-trip to server and improves user experience. The server side validation is great because it makes sure everything from client is valid and removes the burden from individual services. With server side validation is in place, the client side validation becomes optional. It is good to have but not have to. Design philosophy: Do not re-invent wheels. By reusing popular and proven framework, it does not need time to mature thus can be quickly adopted with confidence. Do not add complexity to the system. Learning GWT is already hard enough. Do not scare user away by adding your own complexity. Easy to use. With those in mind, jakarta commons-validator pops up immediately. If you comes from Struts world, you already knew about it. If you do not know, it is time to learn. It is the backbone of GWT server side validation framework I come up. [Less]