> I think you are confusing Hibernate with HSQLDB or some other 
> in-memory Db.  I've no objections to shipping a Java-DB - but 
> so far as we know Roller & Hsqldb will no longer work 
> together because of the SQL LIMIT issue (Hibernate may have 
> fixed this, dunno).

Yeah, I meant to say Hsqldb. Hibernate/HSQLDB should be cooperating now
too. 

> As to the rest, I think you and I have different opinions on 
> what our target developer-audience should be.  I would say 
> that I had little experience *deploying* webapps yet I had 
> Roller up and running inside of 15 minutes when I first tried 
> it out (okay, I already had everything downloaded and knew 
> how to create tables in mySql).  But if you can make it a 
> drop-and-go scenario, that's cool - just don't do so at the 
> expense of the "standard config".
> 

Well, that's the idea. My vision is this: Drop in the .war file into
tomcat/webapps. Load up http://localhost:8080/roller in the browser, and
you'll see a first time configuration wizard. This wizard will allow two
different paths. The easy or beginner path, and the no-holds-barred
advanced path. In either case, this wizard can be run without any
database present. The beginer path will use hsqldb by default, and use
the built in datasource. You can basically hit ok and start using the
app right away. The advanced path will let you choose between
container-managed security and application-managed security. So, there
will be one "extra-step" to do if you want a more advanced usage
scenerio. That step will be picking the roller datasource. There will be
reasonable defaults for all options. (The default datasource will be old
datasource reference: java:comp/env/jdbc/rollerdb, for example) This
will also let you pick a dialect for hibernate - and whatever the
equivalent is for castor. There will a utility to create the database
schema from this wizard, and/or run schema migration scripts. There will
also be a "test datasource connection" button to validate the all the
drivers classes are located, and able to be used. Both beginner and
advanced usages can be completed by pressing the "finish" button on the
respective page. For example, clicking finish on the beginnger page =
built in db, drop and go. Clicking finish on the advanged page =
datasource java:comp/env/jdbc/rollerdb, mysql dialect, hibernate
persistence, container-managed security. The configuration wizard would
be disabled after the finish button is pressed. 

Would this be a good enough to accommodate both advanced and beginner
users? This really wouldn't prevent the "standard config." You'd just
have to go click through the advanced page (which would set up roller
exactly how it is now.) I'd like some constructive critisism. If there
is something you don't agree with, please state your reason and some
alternatives. 

Thanks,

Min Idzelis

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 8/19/2003

-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0