RE : [Springframework-developer] Release 1.0 M1

[Jean-Pierre <jp...@jp...>]

<quote>
Hi everybody,
  
Spring Framework 1.0 M1 has just been released. This first milestone
release towards 1.0 introduces org.springframework as package name,
superseding com.interface21 which still dated back to the original
version from the book. Of course, it offers a myriad of improvements and
new features - see the change log for details.
 
In encourage everyone to migrate from 0.9.x to 1.0 M1, which should
typically just involve a search-and-replace from com.interface21 to
org.springframework in both source code and XML bean definition files.
 
BTW, I've also significantly revised the Spring article in the Hibernate
community area today. Check it out if you're interested.
 
And now, I'm leaving for my 4 week trip to Australia. 5 hours to go
until lift-off ;-)
 
Regards,
Juergen

</quote>

It's a great date!!! 

Juergen,
Once more, thanks for your great work into the team. Now, we will have
to live a month without you :-(. I wish you a good trip :-))!

<COUNTRIES AND LIGHT-COUNTRIES SAMPLES>
The discussion of these last nays showed that one way of our efforts
will to minimize the learning curve. For a first step, this give me the
idea of 'light-countries' which is the Countries without any database
use and therefore hassle as I would it primarily. But the actual
implementation in the CVS is absolutely temporary as they are in most
part redundant. So I will relatively quickly make the following changes.

- Sharing the packages names
- Have the 'Light-Countries' as basic project to allow the study of the
Spring MVC without any database handling
- Refactoring the "Countries" project to be an enhancement of
"Light-Countries". 
  * On the java part, it will add some Classes, subclass others and
simply use the lasts from the "light" project.
  * On the web part, it will pick the common files from the "light"
project and only define the changed and new ones.

So, the new user will be able to study and understand our basic
configuration scheme and internals with a first sample and go the jdbc
handling in a second. The "Countries" will be very light and
concentrated on the add of database support. By the way, the application
subclassing by itself can light some possibilities.

<GENERAL SAMPLES>
Generally, as time pass, we will have more samples. For help at best
users, I consider we will to have specialized samples that don't force
the user to embrass too many aspects of the framework. And then samples
considering the basics understood to go into an advanced area or
all-together real life like ones.

In this optic, concerning Petclinic, I don't advocate including
Hibernate in it what would confuse the user. Instead, a Hibernate
version could be added, maybe taking the same approach as
'light-Countries/Countries'.

For now: an ascending learning order could be:

1) Step-by-step
2) Light-Countries
3) Petclinic and Countries
4) Upcoming Hibernate sample?
5) AOP and transactions samples, by the way, the "Spring" way to replace
EJBs?

And last but not least, in parallel, when time comes to create
applications, the skeletons part of the samples.


Regards,
Jean-Pierre