Free avalon hollywood software for linux

avalon-harvest provides an Avalon-based integration package.
Harvest is a very simple Java-based program to asynchronously copy data from one location to another.
The data can be anything that can be represented as a Java bean, for example, files or database records.
Data can be anything, including files, database records, data available from networks, JMS messages, or whatever you can imagine and represent as java bean.
Main features:
- Assynchronious system integration, where no other solution exists.
- Data replication between databases
- Fetching data from unusable datasources (html pages, documents, other files) into database (or any kind of device capable of storing data)
- Any other scenarios where you may need assynchronious copy of data.

Excalibur is an open source software project of The Apache Software Foundation. Our primary product is a lightweight, embeddable Inversion of Control container named Fortress that is written in java.

Inversion of control, also known as the hollywood principle ("dont call us, well call you"), is a simple but powerful concept. The idea is that we dont "wire up" all the pieces that make up an application (the "components") by writing lots of this-component-uses-that-one-like-so code, nor do we use some kind of lookup directory (like JNDI, for example) where each component decides what components to interact with itself. Instead, we instruct a smart piece of software, the container, to tell the components how to interact.

Fortress (and also its predecessor, "ECM") is such a container. It is lightweight, by which we mean that it doesnt need a lot of resources, take a lot of disk or memory, or impose all sorts of demands on its environment. Fortress is also embeddable, by which we mean that you can use fortress inside just about every java environment. More concretely, you can use it as the basis of a large standalone development platform (like the Keel project), at the core of a servlet-based web application (like Cocoon) or even as the basis of a GUI application (like GuiApp).

Fortress knows how to manage components that have been developed using a rigid lifecycle contract called Avalon-Framework. In the next upcoming release, fortress will also be able to manage ordinary javabeans, and support for other kinds of Inversion of Control are planned.

Besides providing fortress, excalibur also provides a small library of very useful components. We also distribute some of the libraries used to build fortress (and some other containers) seperately. This selection of libraries is called containerkit.

So why is excalibur an interesting project?

Heres a few partial answers.

good code. Code that comes from the mature avalon project (everything that used to be branded as "Avalon Excalibur" and "Avalon Fortress"). This includes two lightweight Inversion of Control containers. One of these powers, among other things, Cocoon. The other ("fortress") is the basis of projects like Keel. Excalibur also includes powerful and mature reusable "components" and "libraries", handling tasks ranging from thread management to component pooling to (URI-and-similar-) source resolving.

smart developers. Most of these people are or have been active in the avalon project in various roles. Several of them are apache members. Together they have loads and loads experience under their belts related to inversion of control development. In fact, Im confident to say this list includes some of the biggest experts on inversion-of-control-style container development.

exciting community. Several open source and commercial projects (both at apache and elsewhere) depend on and contribute to the excalibur project. A strong team of enthousiastic developers (with strong ties to several other projects in the same problem domain) has various big and small plans with excalibur. One of the leading open source organisations in the world, The Apache Software Foundation, is hosting the project, providing insight, advice, infrastructure, legal backing, a time- and battle-proven development process, and much more.

Geo::Coder::Google is a Perl module for Google Maps Geocoding API.

SYNOPSIS

use Geo::Coder::Google;

my $geocoder = Geo::Coder::Google->new(apikey => Your API Key);
my $location = $geocoder->geocode( location => Hollywood and Highland, Los Angeles, CA );

Geo::Coder::Google provides a geocoding functionality using Google Maps API.

METHODS

new

$geocoder = Geo::Coder::Google->new(apikey => Your API Key);
$geocoder = Geo::Coder::Google->new(apikey => Your API Key, host => maps.google.co.jp);

Creates a new geocoding object. You should pass a valid Google Maps API Key as apikey parameter.

When youd like to query Japanese address, you might want to set host parameter, which should point to maps.google.co.jp. I think this also applies to other countries like UK (maps.google.co.uk), but so far I only tested with .com and .co.jp.

geocode

$location = $geocoder->geocode(location => $location);
@location = $geocoder->geocode(location => $location);

Queries $location to Google Maps geocoding API and returns hash refernece returned back from API server. When you cann the method in an array context, it returns all the candidates got back, while it returns the 1st one in a scalar context.
When youd like to pass non-ascii string as a location, you should pass it as either UTF-8 bytes or Unicode flagged string.

Returned data structure is as follows:

{
AddressDetails => {
Country => {
AdministrativeArea => {
SubAdministrativeArea => {
SubAdministrativeAreaName => San Francisco,
Locality => {
PostalCode => {
PostalCodeNumber => 94107
},
LocalityName => San Francisco,
Thoroughfare => {
ThoroughfareName => 548 4th St
}
}
},
AdministrativeAreaName => CA
},
CountryNameCode => US
}
},
address => 548 4th St, San Francisco, CA 94107, USA,
Point => {
coordinates => [
-122.397323,
37.778993,
0
]
}
}

HttpdBase4J is an embeddable Java web server framework that supports HTTP, HTTPS, templated content and serving content from inside an archive.

The classes are easy to extend as they utilize the Hollywood dont call us, well call you principle to allow the user to overide the framework behaviour during all the different phases of the HTTP transaction.

Note:HttpdBase4J uses the Java 6 com.sun.net.httpserver classes so it wont currently work under earlier versions of Java.

Usage Examples:

The simplest use case is to create an embedded web server on port 8088 with its home directory at htdocs in the local filesystem and a root url at / ie / maps onto htdocs:

homeDir = new java.io.File("./htdocs");
httpd = new FileHttpd(homeDir, 10); // Creates a server with a threadpool of 10
httpd.setLogger(System.err); // Log to console
httpd.start(8088, "/");

Creating a HTTPS server equivalent the the HTTP server above requires passing a keystore and password to start. Passing null will generate a certificate free keystore if you only need the encryption capabilities of HTTPS and not the certificate capability:

httpd = new FileHttpd(homeDir, 10);
m_httpd.start(8089, "/", keystore, password);

Serving content from inside an archive or from a jar or zip in the Java classpath requires creating an ArchiveHttpd instance instead of a FileHttpd. To serve content located in a jar or zip in the class path you need only specify the resource directory in the classpath where the content islocated, for example:

httpd = new ArchiveHttpd("/resources/htdocs", 10);
httpd.start(8088, "/");

To serve content from within a specific archive specify the archive as a Java File when constructing the ArchiveHttpd:

httpd = new ArchiveHttpd(new File("content.zip"), "/resources/htdocs", 10);
httpd.start(8088, "/");

Creating web content using templates is also supported. Currently only the StringTemplate library (http://www.stringtemplate.org) is is supported but it should be relatively easy to create user derived classes for other template implementations. To create an HTTP embedded web server on serving templated content from resources/htdocs in the classpath and having a template file handler (A Java class implenting the Templatable interface that is used to fill the templates) in net.homeip.donaldm.test.templates.

httpd = new ArchiveHttpd("resources/htdocs", 10);

StringTemplateHandler stHandler = new ArchiveStringTemplateHandler(httpd,
"net.homeip.donaldm.test.templates");

httpd.addHandler(".st", stHandler); // .st extension = template files
httpd.start(m_port, "/");

The HTTP transaction handling can be customized at any point by overiding any of the methods in the HttpHandleable interface or by overiding onCreateRequestHandler in Httpd in order to provide your own request handler. A simple example of overiding HttpHandleable methods:

httpd = new TestOverideHttpd(m_homeDir, 10);
httpd.start(m_port, "/");

class TestOverideHttpd extends FileHttpd
{
public HttpResponse onServeHeaders(long id, HttpExchange ex, Request request)
{
//Create or amend content
}
public InputStream onServeBody(long id, HttpExchange ex, Request request)
{
//Return amended or created content
}
}

ip-filter-cgi is a set of perl script to modify rules of IP Filter (IP Filter is a TCP/IP packet filter cf: http://coombs.anu.edu.au/~avalon/ip-filter.html). If you make any improvement, correction send it back to. The scripts is not complete and is provided for testing purpose.
adulau@metatix.com .
Main features:
- Perl 5.0 (+CGI.pm)
- a HTTP server (Apache)

Jetty is a 100% Java HTTP Server and Servlet Container. This means that you do not need to configure and run a separate web server (like Apache) in order to use java, servlets and JSPs to generate dynamic content.
Jetty is a fully featured web server for static and dynamic content. Unlike separate server/container solutions, this means that your web server and web application run in the same process, without interconnection overheads and complications.
Furthermore, as a pure java component, Jetty can be simply included in your application for demonstration, distribution or deployment. Jetty is available on all Java supported platforms.
Jetty is devloped under the guidance of Mort Bay Consulting and released under the Apache 2.0 License . Full source code is included in all releases. The License puts few restrictions on usage of Jetty, which is free for commercial use and distribution.
The developers of Jetty ask users to inform themselves of the issues, political, legal or otherwise that motivate and threaten the development of Open Source and Free Software. The Jetty user and development community is active and welcomes new contributors.
Jetty has been widely used in commercial and open source projects and applications, ranging across the full spectrum of runtime environments from hand helds to main frames. To illustrate this diversity, we have put together a (far from exhaustive) list of Jetty Powered products. Here are just a few highlights:
- Integrated with J2EE application servers such as Geronimo, JBoss, and JOnAS.
- Bundled with the JXTA, Tapestry, Cocoon and numerous other Open Source projects.
- Integrated with projects such as Jelly executable XML, Avalon Phoenix micro kernel and Maven project managment.
- Included in many products including IBM Tivoli, Sonic MQ and Cisco SESM.
Jetty has been optimized by commercial and experimental use since 1995 and a small and efficient server is the result:
- A HTTP/1.1 server can be configured in a jar file under 350KB.
- Jetty consistently benchmarks as one of the fastest servlet servers.
- Jetty servers scale well to thousands of simultaneous connections
- Server performance degrades gracefully under stress.
For many applications, HTTP is just another interface protocol. Jetty can easily be embedded in such applications and products without adopting a WWW centric application architecture. Examples of embedded Jetty usage include:
- Integrated with J2EE application servers such as Geronimo, JBoss, and JOnAS.
- Bundled with the JXTA project as the basis for its HTTP transport.
- Included in many products products including IBM tivolli, Sonic MQ and Cisco SESM.
- Used for the CD demo disk in several books on XML and Servlets.
- Run on embedded systems and handheld devices.
Enhancements:
- Added support for TLS_DHE_RSA_WITH_AES_256_CBC_SHA
- Upgraded session ID generation to use SecureRandom
- Quote single quotes in cookies
- AJP protected against bad requests from mod_jk
- JETTY-154 Cookies ignore single quotes