This is a rough rendering of a page from the old Prevayler wiki. Please see the new wiki for current documentation.

#Read the PrevalenceSkepticalFAQ.
#Download Prevayler.
#Take a look at the Demos included.
#Take a look at the javadoc included.
#Read a few Articles (optional).
#Write your own Prevalent System.
#Take a look at the code (optional). It is minimal.
#Browse this site and leave your questions and comments. See: StartingPoints.
#Sign the PrevalentManifesto.
#Join the Prevayler news MailingList.
#Join the Prevayler discussion MailingList (optional).
#Shutdown your database. @8)

@:o Please make sure you have read the PrevalenceSkepticalFAQ to avoid asking redundant questions below. Thanks. --PrevaylerTeam

You need a tutorial of some sort.

I shall ask the Presto team to write a tutorial, as if they were implementing it from scratch. Presto's CVS is a good place to look for a CRUD web app example. --KlausWuestefeld

Why does org.prevayler.demos.demo1NumberStorageCommand.execute() return null?

Because it has to return something. In Prevayler 2.0 (CVS only) that is no longer necessary.

What's a "system" in this context:  'A system that implements this interface can be made transparently persistent with Prevayler.'?

A determistic business system, a "root" business object referencing only other BusinessObjects.

What are the memory requirements, and general hardware requirements for an efficient use of such technique?

Memory requirements: enought to hold all your BusinessObjects plus a little for your VM and CommunicationObjects.
General hardware requirements: Typically a third to a fourth of the processing power required for your database + appserver configuration. That depends on the application, though, and on what else will be running on your system's VM: RMI? CORBA? JSPs? Servlets?