[Springframework-developer] Petclinic, skeletons, and sample apps

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

Lars,

Regarding your ongoing questions about Petclinic and the skeletons:

It was decided quite some time ago that the 1st iteration of Petclinic 
would focus on the more rudimentary aspects of using Spring: beans, 
context, jdbc, and web mvc. That is why there are no examples of aop, 
transactions, or ejb in it. Its purpose is simply to help developers get 
started.

The current version of Petclinic does not not have a separation of 
business and persistence layers because the business layer is soooo very 
thin. At one point it was separated but this was removed because the 
business API was almost a duplicate of the persistence API. As it stands 
now, it really is only about data access.

The skeletons themselves actually came along after most of Petclinic had 
been done. As of now the skeletons are simply starting points for 
configuration files.

I would be interested in your feedback (and that of anybody else) on:
- how well does the ****current**** version of Petclinic help developers 
get started with Spring ? Is it effective and  what do you think should 
be done to improve it. Feel free to show no mercy ;-) .
- what would you want to see in a next version of Petclinic, preferably 
with suggestions for use cases to implement ?
- do you think it would best to morph the skeletons into actual tiny 
sample apps or roll associated demonstrations into bigger sample apps ?

Ken