Free apache cayenne 2.0.3 3.0m1 software for linux

Apache Cayenne project is a free object-relational persistence framework written in Java. Its goal is to make development of database Java applications faster and more consistent with the Object Oriented Programming concept.
Some of the ideas used in Cayenne have been inspired by the persistence mechanism of NeXTs (and now Apples) WebObjects application server.
Whats New in 2.0.3 Stable Release:
- This release features a number of bugfixes, including some serious synchronization issues.
- It is a recommended upgrade.
Whats New in 3.0M1 Development Release:
- This is the first milestone release of Cayenne 3.0.
- The most visible addition to Cayenne is a JSR-220 Java Persistence API Provider (a.k.a. JPA), but significant enhancements have been made to performance and flexibility.
- It is already in production within several products.

Jakarta Projects goal is to provide commercial-quality server solutions based on the Java Platform that are developed in an open and cooperative fashion.

Tomcat 3.x is an implementation of the Java Servlet 2.2 and JavaServer Pages 1.1 Specifications.

Tomcat 4.x is an implementation of the Java Servlet 2.3 and JavaServer Pages 1.2 Specifications, and is a re-implementation of the Tomcat servlet engine from the ground up.

Apache::Cache is a cache data accessible between Apache childrens.

SYNOPSIS

use Apache::Cache qw(:status);

my $cache = new Apache::Cache(default_expires_in=>"5 minutes");

# if the if the next line is called within 10 minutes, then this
# will return the cache value overwise, this will return undef and the
# status method will be equal to the constant EXPIRED (exported by Apache::Cache
# on demande via the :status tag)

# the next line try to get the data from the cache, if the data is stored in
# in the cache and if it not expired, then this return the data. Otherwise
# if data have never been store in the cache, or if its expired, this will
# return undef and the status() method will be equal to constant EXPIRED (exported
# by Apache::Cache on demand, via the :status tag)

my $value = $cache->get(Key);

if($cache->status eq EXPIRED)
{
# cant get the data from the cache, we will need to get it by the normal way
# (via database, from file...)
$value = get_my_data(Key); # here, the get_my_data() function is a function of your
# programe that generate a fresh value

# this data have to expires in 30 secondes
my $expires_in = 30 secondes;
$cache->set(Key => $value, $expires_in);
}
elsif($cache->status eq FAILURE)
{
# dont use cache, cache maybe busy by another child or something goes wrong
$value = get_my_data(Key);
}

This module allows you to cache data easily through shared memory. Whithin the framework of an apache/mod_perl use, this cache is accessible from any child process. The data validity is managed in the Cache::Cache model, but as well based on time than on size or number of keys.

Additionnally, you can implement a cache with Apache::Cache in your module without the risk of namespace clash because Apache::Cache is enclosed in the constructors packages caller (see Apache::SharedMem for more details).

Cayenne is a powerful, full-featured Java Object Relational Mapping framework. Cayenne project is open source and completely free. One of the main Cayenne distinctions is that it comes with cross-platform modeling GUI tools.
This places Cayenne in the league of its own, making it a very attractive choice over both closed source commercial products and traditional "edit your own XML" open source solutions.
Enhancements:
- This release fixes a number of bugs in 1.2.

Apache::ePerl is a fast emulated Embedded Perl (ePerl) facility.

SYNOPSIS

# Apaches httpd.conf file
# mandatory: activation of Apache::ePerl
PerlModule Apache::ePerl
< Files ~ "/root/of/webmaster/area/.+.iphtml$" >
Options +ExecCGI
SetHandler perl-script
PerlHandler Apache::ePerl
< /Files >
# optional: configuration of Apache::ePerl
< Perl >
$Apache::ePerl::Config->{BeginDelimiter} = $Apache::ePerl::Config->{EndDelimiter} = !>;
$Apache::ePerl::Config->{CaseDelimiters} = 0;
$Apache::ePerl::Config->{ConvertEntities} = 1;
< /Perl >
# optional: activation of Apache::Status for Apache::ePerl
< Location /perl-status >
Options +ExecCGI
SetHandler perl-script
PerlHandler Apache::Status
< /Location >

This packages provides a handler function for Apache/mod_perl which can be used to emulate the stand-alone Server-Side-Scripting-Language ePerl (see eperl(3) for more details) in a very fast way. This is not a real 100% replacement for nph-eperl because of reduced functionality under some special cases, principal runtime restrictions and speedup decisions. For instance this variant does not (and cannot) provide the SetUID feature of ePerl nor does it check for allowed filename extensions (speedup!), etc. Instead it uses further features like object caching which ePerl does not use.

But the accepted bristled source file format is exactly the same as with the regular ePerl facility, because Apache::ePerl uses the Parse::ePerl package which provides the original ePerl parser and translator. So, any valid ePerl which works under nph-eperl can also be used under Apache::ePerl.

The intent is to use this special variant of ePerl for scripts which are directly under control of the webmaster. In this situation no real security problems exists for him, because all risk is at his own hands. For the average user you should not use Apache::ePerl. Instead additionally install the regular stand-alone ePerl facility (nph-eperl) for those users.

So, the advantage of Apache::ePerl against the regular nph-eperl is better performance and nothing else. Actually scripts executed under Apache::ePerl are at least twice as fast as under nph-eperl. The reason its not that ePerl itself is faster. The reason is the runtime in-core environment of Apache/mod_perl which does not have any forking overhead.

Apache::Language is a Perl transparent language support for Apache modules and mod_perl scripts.

SYNOPSIS

In YourModule.pm:

sub handler {
my $r = shift;
use Apache::Language;
my $lang = Apache::Language->new($extra_args);
#$lang is now a hash ref that will automacigally pick the right language

print $lang->{Error01} if exists $lang->{Error01};

foreach ( keys %$lang ){
print "$_ is " . $lang->{$_};
}

[...]
}

The goal of this module is to provide a simple way for mod_perl module writers to include support for multiple language requests.

This is version 0.03, and its a complete rewrite from the ground-up of the previous release. Its still backward-compatible with the other releases, but now its much more advanced.

An Apache::Language object acts like a language-aware hash. It stores key/language/values triplets. Using the Accept-Language: field sent by the web-client, it can pick the best fit language for that specific client. Its usage is transparent and should prove to be quite convenient (and hopefully, efficient).

The method used to store/fetch information is now completely modular and will allow easy creation of new storage methods thru a simple API (see the API section).

Apache::Storage is Perl module containing simple functions to store and retrieve information from within the Apache process.

Apache::MyConfig is a Perl module created to build options access.

SYNOPSIS

use Apache::MyConfig;
die unless $Apache::MyConfig::Setup{PERL_FILE_API};

Apache::MyConfig module provides access to the various hooks and features set when mod_perl is built. This circumvents the need to set up a live server just to find out if a certain callback hook is available.

Itterate through %Apache::MyConfig::Setup to get obtain build information then see Appendix B of the Eagle book for more detail on each key.