validate
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 223
PEAR Validate 0.6.4
PEAR Validate is a set of useful methods to validate various kinds of data. more>>
PEAR Validate is a set of useful methods to validate various kinds of data.
Main features:
- numbers (min/max, decimal or not)
- email (syntax, domain check, rfc822)
- string (predifined type alpha upper and/or lowercase, numeric,...)
- date (min, max)
- uri (RFC2396)
- possibility valid multiple data with a single method call (::multiple)
<<lessMain features:
- numbers (min/max, decimal or not)
- email (syntax, domain check, rfc822)
- string (predifined type alpha upper and/or lowercase, numeric,...)
- date (min, max)
- uri (RFC2396)
- possibility valid multiple data with a single method call (::multiple)
Download (0.014MB)
Added: 2006-08-02 License: The PHP License Price:
1179 downloads
CGI::Validate 2.000
CGI::Validate is an advanced CGI form parser and type validation. more>>
CGI::Validate is an advanced CGI form parser and type validation.
SYNOPSIS
use CGI::Validate; # GetFormData() only
use CGI::Validate qw(:standard); # Normal use
use CGI::Validate qw(:subs); # Just functions
use CGI::Validate qw(:vars); # Just exception vars
## If you dont want it to check that every requested
## element arrived you can use this. But I dont recommend it
## for most users.
$CGI::Validate::Complete = 0;
## If you dont care that some fields in the form dont
## actually match what you asked for. -I dont recommend
## this unless you REALLY know what youre doing because this
## normally meens youve got typos in your HTML and we cant
## catch them if you set this.
## $CGI::Validate::IgnoreNonMatchingFields = 1;
my $FieldOne = Default String;
my $FieldTwo = 8;
my $FieldThree = some default string;
my @FieldFour = (); ## For multi-select field
my @FieldFive = (); ## Ditto
my $EmailAddress= ;
## Try...
my $Query = GetFormData (
FieldOne=s => $FieldOne, ## Required string
FieldTwo=i => $FieldTwo, ## Required int
FieldThree => $FieldThree, ## Auto converted to the ":s" type
FieldFour=s => @FieldFour, ## Multi-select field of strings
FieldFive=f => @FieldFive, ## Multi-select field of floats
Email=e => $EmailAddress, ## Must look like an email address
) or do {
## Catch... (wouldnt you just love a case statement here?)
if (%Missing) {
die "Missing form elements: " . join ( , keys %Missing);
} elsif (%Invalid) {
die "Invalid form elements: " . join ( , keys %Invalid);
} elsif (%Blank) {
die "Blank form elements: " . join ( , keys %Blank);
} elsif (%InvalidType) {
die "Invalid data types for fields: " . join ( , keys %InvalidType);
} else {
die "GetFormData() exception: $CGI::Validate::Error";
}
};
## If you only want to check the form data, but dont want to
## have CGI::Validate set anything use this. -You still have full
## access to the data via the normal B object that is returned.
use CGI::Validate qw(CheckFormData); # not exported by default
my $Query = CheckFormData (
FieldOne=s, FieldTwo=i, FieldThree, FieldFour,
FieldFive, Email,
) or do {
... Same exceptions available as GetFormData above ...
};
## Need some of your own validation code to be used? Here is how you do it.
addExtensions (
myType => sub { $_[0] =~ /test/ },
fooBar => &fooBar,
i_modify_the_actual_data => sub {
if ($_[0] =~ /test/) { ## data validation
$_[0] = whatever; ## modify the data by alias
return 1;
} else {
return 0;
}
},
);
my $Query = GetFormData (
foo=xmyType => $foo,
bar=xfooBar => $bar,
cat=xi_modify_the_actual_data => $cat,
);
## Builtin data type checks available are:
s string # Any non-zero length value
w word # Must have at least one w char
i integer # Integer value
f float # Float value
e email # Must match m/^s*]+@[^@.]+(?:.[^@.]+)+>?s*$/
x extension # User extension type. See EXTENSIONS below.
Basicly a blending of the CGI and Getopt::Long modules, and requires the CGI module to function.
The basic concept of this module is to combine the best features of the CGI and Getopt::Long modules. The CGI module is great for parsing, building, and rebuilding forms, however it lacks any real error checking abilitys such as misspelled form input names, the data types received from them, missing values, etc. This however, is something that the Getopt::Long module is vary good at doing. So, basicly this module is a layer that collects the data using the CGI module and passes it to routines to do type validation and name consistency checks all in one clean try/catch style block.
The syntax of GetFormData() is mostly the same as the GetOptions() of Getopt::Long, with a few exceptions (namely, the handling of exceptions) . See the VALUE TYPES section for detail of the available types, and the EXCEPTIONS section for exception handling options. If given without a type, fields are assumed to be type ":s" (optional string), which is normally correct.
If successful, GetFormData() returns the CGI object that it used to parse the data incase you want to use it for anything else, and undef otherwise.
If you only want to do value type and name validation, use CheckFormData() instead with a field=type list. -See the SYNOPSIS for an example.
<<lessSYNOPSIS
use CGI::Validate; # GetFormData() only
use CGI::Validate qw(:standard); # Normal use
use CGI::Validate qw(:subs); # Just functions
use CGI::Validate qw(:vars); # Just exception vars
## If you dont want it to check that every requested
## element arrived you can use this. But I dont recommend it
## for most users.
$CGI::Validate::Complete = 0;
## If you dont care that some fields in the form dont
## actually match what you asked for. -I dont recommend
## this unless you REALLY know what youre doing because this
## normally meens youve got typos in your HTML and we cant
## catch them if you set this.
## $CGI::Validate::IgnoreNonMatchingFields = 1;
my $FieldOne = Default String;
my $FieldTwo = 8;
my $FieldThree = some default string;
my @FieldFour = (); ## For multi-select field
my @FieldFive = (); ## Ditto
my $EmailAddress= ;
## Try...
my $Query = GetFormData (
FieldOne=s => $FieldOne, ## Required string
FieldTwo=i => $FieldTwo, ## Required int
FieldThree => $FieldThree, ## Auto converted to the ":s" type
FieldFour=s => @FieldFour, ## Multi-select field of strings
FieldFive=f => @FieldFive, ## Multi-select field of floats
Email=e => $EmailAddress, ## Must look like an email address
) or do {
## Catch... (wouldnt you just love a case statement here?)
if (%Missing) {
die "Missing form elements: " . join ( , keys %Missing);
} elsif (%Invalid) {
die "Invalid form elements: " . join ( , keys %Invalid);
} elsif (%Blank) {
die "Blank form elements: " . join ( , keys %Blank);
} elsif (%InvalidType) {
die "Invalid data types for fields: " . join ( , keys %InvalidType);
} else {
die "GetFormData() exception: $CGI::Validate::Error";
}
};
## If you only want to check the form data, but dont want to
## have CGI::Validate set anything use this. -You still have full
## access to the data via the normal B object that is returned.
use CGI::Validate qw(CheckFormData); # not exported by default
my $Query = CheckFormData (
FieldOne=s, FieldTwo=i, FieldThree, FieldFour,
FieldFive, Email,
) or do {
... Same exceptions available as GetFormData above ...
};
## Need some of your own validation code to be used? Here is how you do it.
addExtensions (
myType => sub { $_[0] =~ /test/ },
fooBar => &fooBar,
i_modify_the_actual_data => sub {
if ($_[0] =~ /test/) { ## data validation
$_[0] = whatever; ## modify the data by alias
return 1;
} else {
return 0;
}
},
);
my $Query = GetFormData (
foo=xmyType => $foo,
bar=xfooBar => $bar,
cat=xi_modify_the_actual_data => $cat,
);
## Builtin data type checks available are:
s string # Any non-zero length value
w word # Must have at least one w char
i integer # Integer value
f float # Float value
e email # Must match m/^s*]+@[^@.]+(?:.[^@.]+)+>?s*$/
x extension # User extension type. See EXTENSIONS below.
Basicly a blending of the CGI and Getopt::Long modules, and requires the CGI module to function.
The basic concept of this module is to combine the best features of the CGI and Getopt::Long modules. The CGI module is great for parsing, building, and rebuilding forms, however it lacks any real error checking abilitys such as misspelled form input names, the data types received from them, missing values, etc. This however, is something that the Getopt::Long module is vary good at doing. So, basicly this module is a layer that collects the data using the CGI module and passes it to routines to do type validation and name consistency checks all in one clean try/catch style block.
The syntax of GetFormData() is mostly the same as the GetOptions() of Getopt::Long, with a few exceptions (namely, the handling of exceptions) . See the VALUE TYPES section for detail of the available types, and the EXCEPTIONS section for exception handling options. If given without a type, fields are assumed to be type ":s" (optional string), which is normally correct.
If successful, GetFormData() returns the CGI object that it used to parse the data incase you want to use it for anything else, and undef otherwise.
If you only want to do value type and name validation, use CheckFormData() instead with a field=type list. -See the SYNOPSIS for an example.
Download (0.010MB)
Added: 2006-10-06 License: Perl Artistic License Price:
1113 downloads
Params::Validate 0.88
Params::Validate is a Perl module to validate method/function parameters. more>>
Params::Validate is a Perl module to validate method/function parameters.
SYNOPSIS
use Params::Validate qw(:all);
# takes named params (hash or hashref)
sub foo
{
validate( @_, { foo => 1, # mandatory
bar => 0, # optional
}
);
}
# takes positional params
sub bar
{
# first two are mandatory, third is optional
validate_pos( @_, 1, 1, 0 );
}
sub foo2
{
validate( @_,
{ foo =>
# specify a type
{ type => ARRAYREF },
bar =>
# specify an interface
{ can => [ print, flush, frobnicate ] },
baz =>
{ type => SCALAR, # a scalar ...
# ... that is a plain integer ...
regex => qr/^d+$/,
callbacks =>
{ # ... and smaller than 90
less than 90 => sub { shift() < 90 },
},
}
}
);
}
sub with_defaults
{
my %p = validate( @_, { foo => 1, # required
# $p{bar} will be 99 if bar is not
# given. bar is now optional.
bar => { default => 99 } } );
}
sub pos_with_defaults
{
my @p = validate_pos( @_, 1, { default => 99 } );
}
sub sets_options_on_call
{
my %p = validate_with
( params => @_,
spec => { foo => { type SCALAR, default => 2 } },
normalize_keys => sub { $_[0] =~ s/^-//; lc $_[0] },
);
}
The Params::Validate module allows you to validate method or function call parameters to an arbitrary level of specificity. At the simplest level, it is capable of validating the required parameters were given and that no unspecified additional parameters were passed in.
It is also capable of determining that a parameter is of a specific type, that it is an object of a certain class hierarchy, that it possesses certain methods, or applying validation callbacks to arguments.
<<lessSYNOPSIS
use Params::Validate qw(:all);
# takes named params (hash or hashref)
sub foo
{
validate( @_, { foo => 1, # mandatory
bar => 0, # optional
}
);
}
# takes positional params
sub bar
{
# first two are mandatory, third is optional
validate_pos( @_, 1, 1, 0 );
}
sub foo2
{
validate( @_,
{ foo =>
# specify a type
{ type => ARRAYREF },
bar =>
# specify an interface
{ can => [ print, flush, frobnicate ] },
baz =>
{ type => SCALAR, # a scalar ...
# ... that is a plain integer ...
regex => qr/^d+$/,
callbacks =>
{ # ... and smaller than 90
less than 90 => sub { shift() < 90 },
},
}
}
);
}
sub with_defaults
{
my %p = validate( @_, { foo => 1, # required
# $p{bar} will be 99 if bar is not
# given. bar is now optional.
bar => { default => 99 } } );
}
sub pos_with_defaults
{
my @p = validate_pos( @_, 1, { default => 99 } );
}
sub sets_options_on_call
{
my %p = validate_with
( params => @_,
spec => { foo => { type SCALAR, default => 2 } },
normalize_keys => sub { $_[0] =~ s/^-//; lc $_[0] },
);
}
The Params::Validate module allows you to validate method or function call parameters to an arbitrary level of specificity. At the simplest level, it is capable of validating the required parameters were given and that no unspecified additional parameters were passed in.
It is also capable of determining that a parameter is of a specific type, that it is an object of a certain class hierarchy, that it possesses certain methods, or applying validation callbacks to arguments.
Download (0.078MB)
Added: 2007-04-11 License: Perl Artistic License Price:
927 downloads
Easiest Validate On Submit 1.0
Easiest Validate On Submit project enables Web developers to validate any number of form fields. more>>
Easiest Validate On Submit project enables Web developers to validate any number of form fields, client side (in Javascript), with only one line of code per HTML page.
Main features:
- It requires only 1 line of javascript per html file, to validate any number of fields in any number of forms.
- The script detects whether you have a div to display errors. If you havent, it puts messages in alert boxes.
- Evos supports styling both the input widgets and the labels upon validation errors.
- Which fields to validate, and which validation (required field, email, numeric) to use, is completely controlled through CSS classes.
- Pluggable custom validation per field, with minimal amounts of code.
- Messages are located in language files, so its easy to display messages in your native language.
- Everything can be styled using CSS.
<<lessMain features:
- It requires only 1 line of javascript per html file, to validate any number of fields in any number of forms.
- The script detects whether you have a div to display errors. If you havent, it puts messages in alert boxes.
- Evos supports styling both the input widgets and the labels upon validation errors.
- Which fields to validate, and which validation (required field, email, numeric) to use, is completely controlled through CSS classes.
- Pluggable custom validation per field, with minimal amounts of code.
- Messages are located in language files, so its easy to display messages in your native language.
- Everything can be styled using CSS.
Download (0.014MB)
Added: 2006-07-27 License: BSD License Price:
1185 downloads
Validate_fields Class 1.34
Validate_fields Class is an easy-to-use form field validation PHP script. more>>
Validate_fields Class is an easy-to-use form field validation PHP script. This class can be used to validate database inputs or mail forms.
It can validate simple text, numbers, dates, urls, email addresses, and the presence of HTML tags. Invalid form fields will be reported inside a detailed error message.
Enhancements:
- A small improvement in the create_msg() method makes it possible to switch between the XHTML version and the simple HTML version.
- In the fields array one key was named "name", and it has been renamed to "value" to make it more clear.
- The variable declarations at the beginning of the validation method was removed.
- Because the value of a checkbox (radio) type field is only available if the element is checked, there are new functions to validate this elements.
<<lessIt can validate simple text, numbers, dates, urls, email addresses, and the presence of HTML tags. Invalid form fields will be reported inside a detailed error message.
Enhancements:
- A small improvement in the create_msg() method makes it possible to switch between the XHTML version and the simple HTML version.
- In the fields array one key was named "name", and it has been renamed to "value" to make it more clear.
- The variable declarations at the beginning of the validation method was removed.
- Because the value of a checkbox (radio) type field is only available if the element is checked, there are new functions to validate this elements.
Download (0.008MB)
Added: 2006-02-21 License: GPL (GNU General Public License) Price:
1340 downloads
Net::Amazon::Validate::ItemSearch 0.39
Net::Amazon::Validate::ItemSearch is a Perl module to validate ItemSearch requests. more>>
Net::Amazon::Validate::ItemSearch is a Perl module to validate ItemSearch requests.
SYNOPSIS
Net::Amazon::Validate::ItemSearch;
my $valid = Net::Amazon::Validate::ItemSearch::factory(search_index => Actor);
my $option = $itemsearch_valid->user_or_default($input);
my $default = $itemsearch_valid->default();
Net::Amazon::Validate::ItemSearch is a class used to verify ItemSearch operation based on the current version of the WSDL and locale. For example if an Artist search is executed the user can search against Classical, Merchants, or Music.
METHODS
factory(search_index => type)
Constructs a new Net::Amazon::Validate::ItemSearch object, used to validate user input for a SearchIndex. Valid types include Actor, Artist, AudienceRating, Author Brand, BrowseNode, City, Composer, Condition, Conductor, Count, Cuisine, DeliveryMethod, Director, ISPUPostalCode, ItemPage, Keywords, MPAARating, Manufacturer, MaximumPrice, MerchantId, MinimumPrice, MusicLabel, Neighborhood, Orchestra, Power, Publisher, Sort, TextStream and Title. Which departments these search indexes are valid for is dependent upon locale.
default()
Return the default value for a given SearchIndex. Default are determined in order of preference and existence from the following list: Books, Music, DVD, Software. If none of those items are valid for a given SearchIndex then the first valid department of said SearchIndex is used.
user_or_default( $input )
If user input is specified it validates the input, and return it, otherwise it returns the default value for the SearchIndex.
<<lessSYNOPSIS
Net::Amazon::Validate::ItemSearch;
my $valid = Net::Amazon::Validate::ItemSearch::factory(search_index => Actor);
my $option = $itemsearch_valid->user_or_default($input);
my $default = $itemsearch_valid->default();
Net::Amazon::Validate::ItemSearch is a class used to verify ItemSearch operation based on the current version of the WSDL and locale. For example if an Artist search is executed the user can search against Classical, Merchants, or Music.
METHODS
factory(search_index => type)
Constructs a new Net::Amazon::Validate::ItemSearch object, used to validate user input for a SearchIndex. Valid types include Actor, Artist, AudienceRating, Author Brand, BrowseNode, City, Composer, Condition, Conductor, Count, Cuisine, DeliveryMethod, Director, ISPUPostalCode, ItemPage, Keywords, MPAARating, Manufacturer, MaximumPrice, MerchantId, MinimumPrice, MusicLabel, Neighborhood, Orchestra, Power, Publisher, Sort, TextStream and Title. Which departments these search indexes are valid for is dependent upon locale.
default()
Return the default value for a given SearchIndex. Default are determined in order of preference and existence from the following list: Books, Music, DVD, Software. If none of those items are valid for a given SearchIndex then the first valid department of said SearchIndex is used.
user_or_default( $input )
If user input is specified it validates the input, and return it, otherwise it returns the default value for the SearchIndex.
Download (0.15MB)
Added: 2007-03-09 License: Perl Artistic License Price:
960 downloads
CGI::Application::Plugin::ValidateRM 2.1
CGI::Application::Plugin::ValidateRM is a Perl module to help validate CGI::Application run modes using Data::FormValidator. more>>
CGI::Application::Plugin::ValidateRM is a Perl module to help validate CGI::Application run modes using Data::FormValidator.
SYNOPSIS
use CGI::Application::Plugin::ValidateRM;
my $results = $self->check_rm(form_display,_form_profile) || return $self->check_rm_error_page;
# Optionally, you can pass additional options to HTML::FillInForm->fill()
my $results = $self->check_rm(form_display,_form_profile, { fill_password => 0 })
|| return $self->check_rm_error_page;
CGI::Application::Plugin::ValidateRM helps to validate web forms when using the CGI::Application framework and the Data::FormValidator module.
check_rm()
Validates a form displayed in a run mode with a Data::FormValidator profile, returning the results and possibly an a version of the form page with errors marked on the page.
In scalar context, it returns simply the Data::FormValidator::Results object which conveniently evaluates to false in a boolean context if there were any missing or invalide fields. This is the recommended calling convention.
<<lessSYNOPSIS
use CGI::Application::Plugin::ValidateRM;
my $results = $self->check_rm(form_display,_form_profile) || return $self->check_rm_error_page;
# Optionally, you can pass additional options to HTML::FillInForm->fill()
my $results = $self->check_rm(form_display,_form_profile, { fill_password => 0 })
|| return $self->check_rm_error_page;
CGI::Application::Plugin::ValidateRM helps to validate web forms when using the CGI::Application framework and the Data::FormValidator module.
check_rm()
Validates a form displayed in a run mode with a Data::FormValidator profile, returning the results and possibly an a version of the form page with errors marked on the page.
In scalar context, it returns simply the Data::FormValidator::Results object which conveniently evaluates to false in a boolean context if there were any missing or invalide fields. This is the recommended calling convention.
Download (0.010MB)
Added: 2006-11-02 License: Perl Artistic License Price:
1088 downloads
Translate 0.9
Translate are tools for Mozilla, OpenOffice, and Gettext PO translation. more>>
Translate is a toolkit to convert between various different translation formats (such as gettext-based .po formats, OpenOffice.org formats, and Mozilla formats).
This makes it possible to stay in one format across all your localisation. Tools to help process and validate localizations, etc.
Main features:
- conversion between gettext po format and mozilla, openoffice, csv formats
- lots of others that I havent had time to describe yet...
Enhancements:
- Almost all storage classes have been migrated to the projects base class.
- The base class should make it easier to add new formats in the future.
- Major work was done to move escaping into the storage classes and to roundtrip escaping.
- Many many unit tests were added to check compliance.
- Many bugs were fixed.
- The DTD format is no longer escaped, and it follows the DTD spec correctly.
- .properties files are no longer used escaped Unicode, following the Mozilla convention.
- Duplicates are merged by default using the PO method of merging locations.
<<lessThis makes it possible to stay in one format across all your localisation. Tools to help process and validate localizations, etc.
Main features:
- conversion between gettext po format and mozilla, openoffice, csv formats
- lots of others that I havent had time to describe yet...
Enhancements:
- Almost all storage classes have been migrated to the projects base class.
- The base class should make it easier to add new formats in the future.
- Major work was done to move escaping into the storage classes and to roundtrip escaping.
- Many many unit tests were added to check compliance.
- Many bugs were fixed.
- The DTD format is no longer escaped, and it follows the DTD spec correctly.
- .properties files are no longer used escaped Unicode, following the Mozilla convention.
- Duplicates are merged by default using the PO method of merging locations.
Download (0.50MB)
Added: 2006-06-19 License: GPL (GNU General Public License) Price:
1227 downloads
Data::Validator::Item 0.75
Data::Validator::Item is a Factory Class to validate data items. more>>
Data::Validator::Item is a Factory Class to validate data items.
This is an attempt to create an object which will permit semi-automatic verification of a data value.
SYNOPSIS
use Data::Validator::Item;
my $item = Data::Validator::Item->new(); #Create a new Data::Validator::Item, called $item.
#Set values
$item->name(fred);
$item->values([1,2,3]); or $item->values(@array);
$item->missing(*); or $item->missing(); #undef is unlikely to be sensible!
$item->min(0); $item->max(100);
$item->verify($reference_to_subroutine); #Used in the $item->validate() function
$item->transform($reference_to_subroutine); #Used in the $item->put() function
#Get values
my $name = $item->name();
my @values = $item->values();
my $missing = $item->missing();
etc...
#Use it.. $item->validate(); #Returns 1 for success, 0 for failure $item->error(); #Returns the correct error message $item->put();
USAGE
Many people work with data organised as records, each containing (potentially many) variables. It is often necessary to process files of such records, and to test every variable within every record to ensure that each one is valid. I do this before putting data from very large flat files into my databases. For each variable I had a need to define specific, sometimes complex rules for validity, then implement them, and check them. This is what Data::Validator::Item is for.
Note carefully that Data::Validator::Item handles only one scalar vlaue at a time. This value could come from a file, a database, an array, a hash or your grannys parrot. Data::Validator::Item doesnt care.
I use Data::Validator::Item as follows. I create one for every named variable in my data file. In many real applications most of this setup can be done by looping over a list of variable names, creating many Data::Validator::Items each named for the corresponding variable. Common features, like missing values, and names can be set in this loop.
Specifics, like values(), min(), max(), verify() and so on can be set individually. I then create a hash to hold all of the Data::Validator::Items for a particular data source, The keys of this hash are the names of the variables, and the values are the Data:Validators themselves. Y.M.M.V.
<<lessThis is an attempt to create an object which will permit semi-automatic verification of a data value.
SYNOPSIS
use Data::Validator::Item;
my $item = Data::Validator::Item->new(); #Create a new Data::Validator::Item, called $item.
#Set values
$item->name(fred);
$item->values([1,2,3]); or $item->values(@array);
$item->missing(*); or $item->missing(); #undef is unlikely to be sensible!
$item->min(0); $item->max(100);
$item->verify($reference_to_subroutine); #Used in the $item->validate() function
$item->transform($reference_to_subroutine); #Used in the $item->put() function
#Get values
my $name = $item->name();
my @values = $item->values();
my $missing = $item->missing();
etc...
#Use it.. $item->validate(); #Returns 1 for success, 0 for failure $item->error(); #Returns the correct error message $item->put();
USAGE
Many people work with data organised as records, each containing (potentially many) variables. It is often necessary to process files of such records, and to test every variable within every record to ensure that each one is valid. I do this before putting data from very large flat files into my databases. For each variable I had a need to define specific, sometimes complex rules for validity, then implement them, and check them. This is what Data::Validator::Item is for.
Note carefully that Data::Validator::Item handles only one scalar vlaue at a time. This value could come from a file, a database, an array, a hash or your grannys parrot. Data::Validator::Item doesnt care.
I use Data::Validator::Item as follows. I create one for every named variable in my data file. In many real applications most of this setup can be done by looping over a list of variable names, creating many Data::Validator::Items each named for the corresponding variable. Common features, like missing values, and names can be set in this loop.
Specifics, like values(), min(), max(), verify() and so on can be set individually. I then create a hash to hold all of the Data::Validator::Items for a particular data source, The keys of this hash are the names of the variables, and the values are the Data:Validators themselves. Y.M.M.V.
Download (0.011MB)
Added: 2007-02-28 License: Perl Artistic License Price:
969 downloads
XhtmlValidator.php 0.2
XhtmlValidator can be used to validate XHTML documents. more>>
XhtmlValidator.php can be used to validate XHTML documents. It uses only the expat extension functions always available under since PHP 3 and it does not need other external XML processing extensions.
This validator is part of the Akelos Framework and is enabled by default when the framework is on development mode.
The class parses the documents and check whether the tags and attributes used by the documents are allowed within the XHTML standard.
If validation errors are found, highlighted error messages and offending document line numbers will be returned.
This is an experimental class, so you should double check your code with the w3c validator, as in only 1000 lines of code the XhtmlValidator lacks support for Encoding and Doctype validation.
Enhancements:
- Support for literal entities was added.
<<lessThis validator is part of the Akelos Framework and is enabled by default when the framework is on development mode.
The class parses the documents and check whether the tags and attributes used by the documents are allowed within the XHTML standard.
If validation errors are found, highlighted error messages and offending document line numbers will be returned.
This is an experimental class, so you should double check your code with the w3c validator, as in only 1000 lines of code the XhtmlValidator lacks support for Encoding and Doctype validation.
Enhancements:
- Support for literal entities was added.
Download (0.007MB)
Added: 2006-08-28 License: LGPL (GNU Lesser General Public License) Price:
1153 downloads
XML::Validator::Schema 1.08
XML::Validator::Schema is a Perl module to validate XML against a subset of W3C XML Schema. more>>
XML::Validator::Schema is a Perl module to validate XML against a subset of W3C XML Schema.
SYNOPSIS
use XML::SAX::ParserFactory;
use XML::Validator::Schema;
#
# create a new validator object, using foo.xsd
#
$validator = XML::Validator::Schema->new(file => foo.xsd);
#
# create a SAX parser and assign the validator as a Handler
#
$parser = XML::SAX::ParserFactory->parser(Handler => $validator);
#
# validate foo.xml against foo.xsd
#
eval { $parser->parse_uri(foo.xml) };
die "File failed validation: $@" if $@;
This module allows you to validate XML documents against a W3C XML Schema. This module does not implement the full W3C XML Schema recommendation (http://www.w3.org/XML/Schema), but a useful subset. See the SCHEMA SUPPORT section below.
IMPORTANT NOTE: To get line and column numbers in the error messages generated by this module you must install XML::Filter::ExceptionLocator and use XML::SAX::ExpatXS as your SAX parser. This module is much more useful if you can tell where your errors are, so using these modules is highly recommeded!
<<lessSYNOPSIS
use XML::SAX::ParserFactory;
use XML::Validator::Schema;
#
# create a new validator object, using foo.xsd
#
$validator = XML::Validator::Schema->new(file => foo.xsd);
#
# create a SAX parser and assign the validator as a Handler
#
$parser = XML::SAX::ParserFactory->parser(Handler => $validator);
#
# validate foo.xml against foo.xsd
#
eval { $parser->parse_uri(foo.xml) };
die "File failed validation: $@" if $@;
This module allows you to validate XML documents against a W3C XML Schema. This module does not implement the full W3C XML Schema recommendation (http://www.w3.org/XML/Schema), but a useful subset. See the SCHEMA SUPPORT section below.
IMPORTANT NOTE: To get line and column numbers in the error messages generated by this module you must install XML::Filter::ExceptionLocator and use XML::SAX::ExpatXS as your SAX parser. This module is much more useful if you can tell where your errors are, so using these modules is highly recommeded!
Download (0.052MB)
Added: 2006-09-15 License: Perl Artistic License Price:
1142 downloads
pixiliate 0.4.2
Pixilate is a commandline packet generation utility . more>>
Pixilate is a commandline packet generation utility that reads Cisco PIX 6.2x or Cisco IOS ACLs as input and generates the appropriate packets.
pixilate is currently capable of generating TCP/UDP/ICMP (various ICMP types), and IGMP utilizing the Libnet 1.1.x library available from http://www.packetfactory.net. NOTE: Libnet 1.0.x is NOT compatible."
The primary goal of pixilate is to validate firewall ACLs. Pixilate accomplishes this by generating the appropriate packets for each access list entry. Since the source address will often be spoofed, pixilate does not contain any packet capturing capability. If you are generating access lists by hand and specify the source address to be either your actual
IP address or an IP address on your network that you are capable of sniffing via promiscuous mode or a spanned port on a switch, you must provide your own sniffer. Tcpdump or ethereal are excellent choices.
Pixilate requires a remote sniffer capable of receiving all traffic with a destination behind the firewall. This will typically be a spanned port on the same switch as the firewall itself. This is obviously needed to validate various destination addresses. Packets with a destination of any will be sent to the default destination address supplied by the required -d option.
Enhancements:
- Update to support libnet 1.1.2 api changes which are incompatible with previous versions.
<<lesspixilate is currently capable of generating TCP/UDP/ICMP (various ICMP types), and IGMP utilizing the Libnet 1.1.x library available from http://www.packetfactory.net. NOTE: Libnet 1.0.x is NOT compatible."
The primary goal of pixilate is to validate firewall ACLs. Pixilate accomplishes this by generating the appropriate packets for each access list entry. Since the source address will often be spoofed, pixilate does not contain any packet capturing capability. If you are generating access lists by hand and specify the source address to be either your actual
IP address or an IP address on your network that you are capable of sniffing via promiscuous mode or a spanned port on a switch, you must provide your own sniffer. Tcpdump or ethereal are excellent choices.
Pixilate requires a remote sniffer capable of receiving all traffic with a destination behind the firewall. This will typically be a spanned port on the same switch as the firewall itself. This is obviously needed to validate various destination addresses. Packets with a destination of any will be sent to the default destination address supplied by the required -d option.
Enhancements:
- Update to support libnet 1.1.2 api changes which are incompatible with previous versions.
Download (0.11MB)
Added: 2006-07-13 License: GPL (GNU General Public License) Price:
1200 downloads
RailsTidy 0.1
RailsTidy is a plugin for Ruby On Rails. more>>
RailsTidy project is a plugin for Ruby On Rails.
Main features:
- validate your rhtml templates,
- validate the html output of your functional tests,
- clean the html generated by rails.
<<lessMain features:
- validate your rhtml templates,
- validate the html output of your functional tests,
- clean the html generated by rails.
Download (0.011MB)
Added: 2006-02-16 License: MIT/X Consortium License Price:
1345 downloads
OVal 1.0
OVal is a generic validation frameworks for any kind of Java objects. more>>
OVal is a generic Java 5 based object validation framework that uses annotations to express constraints and AspectJ to handle automatic validation (programming by contract).
OVal allows you to:
- to specify constraints for class fields and method return values
- to easily validate objects on demand
- to specify constraints for constructor parameters that are automatically checked when the constructor is called
- to specify constraints for method parameters that are automatically checked when the method is called
- to enforce full object validation after an object instance has been created
- to enforce full object validation before a method of the object is called
- to enforce full object validation after a method of the object is called
- to either let OVal throw constraint violation exceptions during automatic checks or alternatively notify constraint violation listeners.
- to easily create custom constraints
Enhancements:
New features:
+ New constraints (@NotBlank)
+ Support for OGNL and MVEL as constraint expression language
0.9 to 1.0 Migration Notes:
a) Validator.setMessageResolver and Validator.getMessageResolver are now static, this means the same message resolver instance is used with all Validator/Guard instances
b) Class net.sf.oval.collection.CollectionFactoryHolder has been moved to package net.sf.oval.internal.
This class should not be used directly, the collection factory in use can be retrieved via the static method Validator.getCollectionFactory and set with the static method Validator.setCollectionFactory
c) @Guarded.applyFieldConstraintsToSetter has been renamed to @Guarded.applyFieldConstraintsToSetters
d) JPAAnnotationsConfigurer constraint mappings extended:
@javax.persistence.OneToOne => @net.sf.oval.constraints.AssertValid
@javax.persistence.OneToMany => @net.sf.oval.constraints.AssertValid
@javax.persistence.ManyToOne => @net.sf.oval.constraints.AssertValid
<<lessOVal allows you to:
- to specify constraints for class fields and method return values
- to easily validate objects on demand
- to specify constraints for constructor parameters that are automatically checked when the constructor is called
- to specify constraints for method parameters that are automatically checked when the method is called
- to enforce full object validation after an object instance has been created
- to enforce full object validation before a method of the object is called
- to enforce full object validation after a method of the object is called
- to either let OVal throw constraint violation exceptions during automatic checks or alternatively notify constraint violation listeners.
- to easily create custom constraints
Enhancements:
New features:
+ New constraints (@NotBlank)
+ Support for OGNL and MVEL as constraint expression language
0.9 to 1.0 Migration Notes:
a) Validator.setMessageResolver and Validator.getMessageResolver are now static, this means the same message resolver instance is used with all Validator/Guard instances
b) Class net.sf.oval.collection.CollectionFactoryHolder has been moved to package net.sf.oval.internal.
This class should not be used directly, the collection factory in use can be retrieved via the static method Validator.getCollectionFactory and set with the static method Validator.setCollectionFactory
c) @Guarded.applyFieldConstraintsToSetter has been renamed to @Guarded.applyFieldConstraintsToSetters
d) JPAAnnotationsConfigurer constraint mappings extended:
@javax.persistence.OneToOne => @net.sf.oval.constraints.AssertValid
@javax.persistence.OneToMany => @net.sf.oval.constraints.AssertValid
@javax.persistence.ManyToOne => @net.sf.oval.constraints.AssertValid
Download (0.64MB)
Added: 2007-07-23 License: Eclipse Public License Price:
498 downloads
ArbitroWeb 0.6
ArbitroWeb is a Web anonymizer written in PHP. more>>
ArbitroWeb is a Web anonymizer written in PHP. ArbitroWeb will redirect all web requests thru its set of scripts, all URLs contained will be adjusted/mangled to its own scripts.
ArbitroWeb is known to be working on following configurations:
1) Linux i386 Box (Kernel 2.4.7, Mandrake 8.0).
Apache v1.3.20 - With DSO Support
PHP v4.0.6 - Installed as DSO Module
2) Sun Solaris 8 Sparc Box.
Apache v1.3.20 - With DSO Support
PHP v4.0.6 - Installed as DSO Module
3) Microsoft Windows 2000 Professional Intel
Apache v1.3.20 - Default Installation of Win32 binaries.
PHP v4.0.6 - Configured as a Module with LoadModule Directive.
ArbitroWeb WILL NOT WORK if you have PHP configured to run in CGI mode. Apache users (Win32 and Linux) should change from using ScriptAlias and Action httpd.conf directives, to using the LoadModule directive. (See the INSTALL.txt for more information on this subject)
Enhancements:
- BUG FIX - Using URLs without a path caused errors. Such as "http://www.cnn.com", Fix will now add the root path if it is not provided.
- BUG FIX - index.php would accept anything as a valid URL. Now index.php will attempt to validate the URL before using it.
- BUG FIX - meta tag refreshing is now filtered.
- Meta Tags for ArbitroWeb keyword and description added to index.php
- Added error notification when php is in CGI mode.
- Made log file output conform to apaches access log format.
<<lessArbitroWeb is known to be working on following configurations:
1) Linux i386 Box (Kernel 2.4.7, Mandrake 8.0).
Apache v1.3.20 - With DSO Support
PHP v4.0.6 - Installed as DSO Module
2) Sun Solaris 8 Sparc Box.
Apache v1.3.20 - With DSO Support
PHP v4.0.6 - Installed as DSO Module
3) Microsoft Windows 2000 Professional Intel
Apache v1.3.20 - Default Installation of Win32 binaries.
PHP v4.0.6 - Configured as a Module with LoadModule Directive.
ArbitroWeb WILL NOT WORK if you have PHP configured to run in CGI mode. Apache users (Win32 and Linux) should change from using ScriptAlias and Action httpd.conf directives, to using the LoadModule directive. (See the INSTALL.txt for more information on this subject)
Enhancements:
- BUG FIX - Using URLs without a path caused errors. Such as "http://www.cnn.com", Fix will now add the root path if it is not provided.
- BUG FIX - index.php would accept anything as a valid URL. Now index.php will attempt to validate the URL before using it.
- BUG FIX - meta tag refreshing is now filtered.
- Meta Tags for ArbitroWeb keyword and description added to index.php
- Added error notification when php is in CGI mode.
- Made log file output conform to apaches access log format.
Download (0.007MB)
Added: 2006-06-24 License: GPL (GNU General Public License) Price:
1217 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above validate search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
