[Springframework-developer] demo/tutorial(s)

[Ken K. <kk...@kk...>]

It's great to hear so much input on this subject over the last few days.

A few of my own opinions:

1. We need to make a decision fairly soon about which server/database 
platforms to use.
Doing this will allow us to better focus the energy of the group on the 
much more significant decisions that need to be made regarding the 
content of the demo/tutorial(s). Presumably Rod will either make the 
final decision or set up a framework for doing so.

2. When making these platform choices, we should strive to maximize 
potential developer buy-in to Spring.
It seems clear to me that the best way to achieve this is to make it as 
easy as possible for potential developers of all skill levels to get up 
to speed, particularly for the "entry-level" version of the 
demo/tutorial. Tomcat probably is an easy winner for the server platform 
in the "entry-level" version because virtually everybody has it already 
installed and its so easy to setup and administer. As to the "advanced" 
version server platform, I really don't have a good opinion as I don't 
know all the issues. We should however consider popularity of the 
platform as well as ease-of-use and configuration. Unless there is 
widespread hostility for a particular platform that would reduce 
potential buy-in, we should probably try to avoid the politics of what 
is truly open-source. With regard to the database platform, it seems 
that either mySQL or  HSQL  would be good, popular choices. The fact 
that HSQL is lightweight and can be run in-process without requiring 
user configuration is certainly advantageous for its use in a demo. The 
fact that it supports transactions out-of-the-box is also a plus.

3. We very much need to clearly articulate the needs that Spring is 
trying to address with each of its core elements and what the advantages 
are to developers.
This "document" should be the frontpiece of the website. It should also 
emphasize the unobtrusive nature of the framework and that its parts can 
be used to advantage with other frameworks, even in non-J2EE 
applications. The demo/tutorial(s) ahould attempt to reinforce these 
ideas and clearly demonstrate as many of them as is practicable.

Ken