|
| Overview |
UserPreferences |
| JicarillaWiki | FrontPage | Overview | Articles | GetStarted | Sourceforge Project Page | RecentChanges |
This wiki is in 'slumber' mode, just like its associated sourceforge project. Edits are disabled, the content is potentially stale and is not maintained. That said, it contains some really useful stuff still. Enjoy!
An overview of the cool stuff coming to fruition in the Jicarilla Sandbox.
If you want to get your hands on some sources or binaries, read this page.
The sourceforge project page for Jicarilla. Contains information about the ![[WWW]](/oldwikiskin/img/moin-www.gif){kind=small}
mailing lists, Source Repository, an RSS Feed with project news, and more information.
The javadocs for the complete Jicarilla Platform. Most of the Jicarilla documentation is kept in the javadocs. A good place to start reading is the Framework Description.
Frequently Asked Questions (FAQ)
The unofficial FAQ about Jicarilla, maintained (hopefully) by the user community. Please post your questions here, and try and provide answers to questions posted by others.
A basic architectural/structural overview
Some outdated schematics describing the general system pattern. This will be updated and expanded when the project structure solidifies.
How to submit patches and bug reports
If you've found a bug in Jicarilla or have created an enhancement, please read this page.
Unit test coverage reports on all of the Jicarilla Platform code. These are usually a good indication of the stability of a package (higher coverage means more stable code).
The Jicarilla-Framework builds upon Type-3 IoC, adding an Active interface to better support multi-threaded components. Besides some pretty generic utility code (like a set of base classes for nested exceptions), it adds basic abstractions for the building blocks of lightweight event-based systems, like sources, sinks, stages, multicasters, etc.
The Jicarilla-Container is a lightweight, extensible IoC / COP container. It supports Type-1, Type-2 and Type-3 IoC, and several variants of those. In other words, you can use Jicarilla-Container to run Avalon-Framework components, WebWork components, PicoContainer components, and others. Furthermore, Jicarilla-Container is specifically designed to make it easy to host even more widely varying types of components.
A small package that aims to provide for no-brainer conversion between the various collection-style objects that make java interoperability such a pain at times (ie, convert a DOM tree to a Properties instance or an Avalon-Framework configuration, and back again).
A componentized, scriptable, event-based webserver, based on the JDK 1.4 New I/O (nio) package and on Jicarilla-Framework.
Currently still inside the Jicarilla-HTTP package, this package provides a basic nio socket server component.
Several buttons you can use to show your software uses, or is compatible with, jicarilla. There's also a "convert" button you can display on your weblog (for example), if you think Jicarilla is really cool.
A list, with short descriptions, of projects somehow related to Jicarilla.
