springframework-developer — Spring Framework developers list

RE: [Springframework-developer] Example classes needed

[<jue...@we...>]

Countdown to 1.0 M1... It's "spring" instead of "spring-full", and jar =
files with manifest entries but no version numbers in the names if there =
aren't any serious objections in the next few hours...=20

Thomas, I've just seen that you already adapted the file names in the =
MVC tutorial to "spring.jar". If there should be any change of mind this =
afternoon, I'll care for the proper name in the tutorial.

Juergen


-----Original Message-----
From: tri...@tr... [mailto:tri...@tr...]
Sent: Thursday, August 28, 2003 7:41 PM
To: j=FCrgen h=F6ller [werk3AT]
Cc: spr...@li...
Subject: RE: [Springframework-developer] Example classes needed


Juergen,

I like the manifest entry and I also like jars without version numbers.

Thomas

> I've just added a manifest entry "Spring-Version" to our build =
scripts. This
> means that a "spring.jar" for 1.0 M1 will include a =
"Spring-Version=3D1.0m1"
> entry in its META-INF/manifest.mf file. So if you've got jar files =
lying
> around, you can always check the exact version. With this included, I =
tend to
> drop version numbers even more. Thanks for the idea, Rob - I just =
guess it's
> simpler to make a manifest entry than to include an extra file.
>=20
> We all seem to agree we prefer "spring.jar" over "spring-full.jar", =
but are
> about 50:50 regarding version numbers in the name. So let's focus on =
the
> latter: Would anyone *mind* no version number in the name, given that =
it's
> mentioned in the manifest file? Everyone is free to rename the files =
any way
> he wants anyway, it's just about the shipped jars. As for me, I would =
mind
> the full version number "1.0m1" - in the meantime, I even prefer
> "spring.jar".
>=20
> To keep the fire burning, some examples for no version numbers that I =
know
> of: Servlet, JUnit, JavaMail, Xerces, JSTL, Commons Logging, Commons =
DBCP,
> XAPool, Hibernate, COS, GLUE, Ant, Tomcat, JBoss, Clover. =
Counterexamples
> with version numbers in the jar name: JTA, CGLIB, BCEL, Log4J, Castor, =
Tyrex,
> Velocity, Tapestry, Hessian, iText, MySQL JDBC driver.
>=20
> In the end, one can argue for all options. There is no obvious =
solution. So
> we should try to settle on one option and stick with it.
>=20
> Juergen
>=20
>=20
> -----Original Message-----
> From: Rob Butler [mailto:rob...@ve...]
> Sent: Thursday, August 28, 2003 6:34 PM
> To: j=FCrgen h=F6ller [werk3AT]; Lars Fischer
> Cc: spr...@li...; =
tri...@tr...;
> rod...@in...
> Subject: RE: [Springframework-developer] Example classes needed
>=20
>=20
> Hello all,
>=20
> Since spring is modular, why not break it down even further into =
chuncks.
>=20
> spring-common.jar ->Basic stuff that is used everywhere in spring
> spring-beans.jar -> contains ONLY the Spring Beans stuff.
> spring-aop.jar -> contains ONLY the Spring AOP stuff.
> spring-jdbc -> contains ONLY the Spring JDBC stuff.
> spring-orm.jar -> contains ONLY the Spring ORM stuff.
> spring-context.jar -> contains ONLY the Spring context stuff.
> spring-mvc.jar -> contains ONLY the spring MVC stuff.
>=20
> If spring-orm.jar is dependent upon spring-common.jar then the user =
will need
> to download and include spring-common.jar in the classpath too.  In =
this way
> people can pick and choose the exact parts they want, but you don't =
have to
> come up with a million different package combinations...  i.e. no =
packages
> that include ORM & JDBC, but not MVC.  Another one that has ORM, JDBC,
> context, but not MVC.  Another one that has ORM, jdbc & MVC.  Another =
one
> that has ORM, JDBC, context & MVC.  See where I am going with this?
> People should be smart enough to take the parts they want, and to get =
the
> dependencies they need.
>=20
> Now as far as the file name goes, why not just use a name WITHOUT the =
version
> name in it, and then include a file (or directory) in the root of the =
jar
> called VERSION-1.0.1 or some such thing.  That way people will not =
need to
> worry about changing build scripts to use a newer version of the jar =
that is
> API compatible, and they can still easiliy determine what version they =
are
> using by looking in the jar itself.  the only time the jar file name =
should
> change is if the API has LARGE changes that renders the new jar =
completely
> incompatible with the old API.  Minor changes to the API should =
probably not
> have the jar file names changed.
>=20
> Just some ideas and my 2 cents.
>=20
> Later
> Rob
>=20
> > From: j=FCrgen h=F6ller [werk3AT] <jue...@we...>
> > Date: 2003/08/28 Thu PM 12:07:42 EDT
> > To: "Lars Fischer" <lar...@gm...>
> > CC: <spr...@li...>,=20
> > 	<tri...@tr...>,=20
> > 	<rod...@in...>
> > Subject: RE: [Springframework-developer] Example classes needed
> >=20
> > Lars,
> >=20
> > The problem is that we have multiple jar files:
> > - spring-beans.jar
> > - spring-aop.jar
> > - spring-jdbc.jar
> > - spring-orm.jar
> > - spring-context.jar
> > - spring-full.jar
> >=20
> > "full" indicates that it includes all of Spring. We could name it
> "spring.jar" of course, I'm quite inclined towards this if others =
agree. What
> does everybody think?
> >=20
> > Regarding Colin's argument on in-between numbering: I wouldn't mind
> dropping the version number altogether, in Hibernate/Ant/Servlet =
style. I'm
> just not a fan of very specific file names.
> >=20
> > So 2 questions:
> > 1. a) "spring-full.jar" or b) "spring.jar" for the complete jar file
> > 2. a) "spring-beans-1.0m1.jar", b) "spring-beans-1.0.jar" or c)
> "spring-beans.jar"
> >=20
> > In the meantime, I tend to vote 1b and 2c. I wouldn't mind 1a or 2b =
either,
> though.
> >=20
> > Juergen
> >=20
> >=20
> > -----Original Message-----
> > From: Lars Fischer [mailto:lar...@gm...]
> > Sent: Thursday, August 28, 2003 5:56 PM
> > To: j=FCrgen h=F6ller [werk3AT]
> > Cc: spr...@li...; =
tri...@tr...;
> > rod...@in...
> > Subject: RE: [Springframework-developer] Example classes needed
> >=20
> >=20
> > What about spring.jar, spring2.jar ? I don't like this "-full".
> >=20
> >=20
> > > Hmmm, not much response yet... I still tend to prefer "sp
> > > ring-full-1.0.jar", for easy drop-in. IMO, a jar file doe
> > > s not need to reflect the exact detail version. I conside
> > > r it fine enough if it indicates the major version. See s
> > > ervlet.jar, hibernate2.jar. Can we please decide on this=20
> > > until *tomorrow*? :-)
> > > =20
> > > Juergen
> > > =20
> > > =20
> > >=20
> > > -----Original=20
> > > Message-----
> > > From: j=C3=BCrgen h=C3=B6ller [werk3AT]=20
> > > Sent: Mon
> > > day, August 25, 2003 11:50 PM
> > > To: Lars Fischer; springfr
> > > ame...@li...
> > > Cc: trisberg@tri
> > > db.com
> > > Subject: Re: [Springframework-developer] Example=20
> > > classes needed
> > >=20
> > >=20
> > > Let's vote on this. I don't mind eith
> > > er naming strategy for jar files. Anybody else prefering=20
> > > the spring-full-1.0m1 style?
> > > =20
> > > BTW, Hibernate uses hibe
> > > rnate2.jar for its whole 2.x tree. Log4J uses log4j-1.2.8
> > > .jar for the specific version. 2 examples for opposite en
> > > ds, I guess.
> > > =20
> > > Juergen
> > > =20
> > > =20
> > >=20
> > > -----Urspr=C3=BCngliche Nac
> > > hricht-----=20
> > > Von: Lars Fischer [mailto:lars.fischer@gmxp
> > > ro.net]=20
> > > Gesendet: Mo 25.08.2003 23:18=20
> > > An: springframe
> > > wor...@li...=20
> > > Cc: j=C3=BCrgen h=C3=B6lle
> > > r [werk3AT]; tri...@tr...=20
> > > Betreff: Re: [Springfra
> > > mework-developer] Example classes needed
> > >=20
> > >=20
> > >=20
> > > I agree w
> > > ith Thomas, I once made a mistake because I didn't realiz
> > > e
> > > that I was using an older version. The jar-files shoul
> > > d be named after
> > > the version.
> > >=20
> > > > Juergen,
> > > >
> > > > The dr
> > > awback then is that you can't tell from the jar file if i
> > > t is M1, M2
> > > > or
> > > > the release jar.
> > > >
> > > > Thomas
> > > >
> > > >=20
> > > > It's gonna be "spring-framework-1.0m1" and "spring-full
> > > -1.0.jar", if we
> > > > stick
> > > > > to the current plan. We've
> > >  used the same naming strategy for 0.9.x, e.g.
> > > > > "spri
> > > ng-framework-0.9.1" but still "spring-full-0.9.jar". I pr
> > > efer that
> > > > way
> > > > > to ease drop-in replacement in the=20
> > > literal sense :-) The build
> > > > properties
> > > > > reflect th
> > > is in "spring-version=3D1.0" and "spring-version-detail=3D1.0
> > > m1".
> > > > >=20
> > > > > Juergen
> > > > >=20
> > > > >=20
> > > > >
> > > > >     -----Ur
> > > spr=C3f=C2=BCngliche Nachricht-----
> > > > >     Von: trisberg@trid
> > > b.com [ mailto:tri...@tr...]
> > > > >     Gesendet: Mo=20
> > > 25.08.2003 19:21
> > > > >     An: j=C3f=C2=BCrgen h=C3f=C2=B6ller [werk3A
> > > T]
> > > > >     Cc: Lars Fischer; springframework-developer@l
> > > ists.sourceforge.net
> > > > >     Betreff: RE: [Springframewo
> > > rk-developer] Example classes needed
> > > > >   =20
> > > > >   =20
> > > >
> > >  >
> > > > >     Juergen,
> > > > >   =20
> > > > >     > Anyway, ContextL
> > > oaderServlet *will* be in 1.0 M1, to be released at
> > > > th
> > > e
> > > > > end
> > > > >     > of this week if there aren't any ma
> > > jor obstacles. BTW, can everybody
> > > > > please
> > > > >     >=20
> > > test the current CVS contents against own applications?
> > > > >     >
> > > > >   =20
> > > > >     I am updating the Step-by-ste
> > > p-MVC document - what will the exact name
> > > > of
> > > > > the
> > >=20
> > > > >     directory and the jar file be?  I'm assuming 'sp
> > > ring-framework-1.0M1'
> > > > and
> > > > >     'spring-full-1.0M1.
> > > jar'.
> > > > >   =20
> > > > >     Thomas
> > > > >   =20
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >=20
> > >=20
> > >=20
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Springframework-developer mailing list
> > Spr...@li...
> > =
https://lists.sourceforge.net/lists/listinfo/springframework-developer
> >=20
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20

[Springframework-developer] Re: Thanks to all the Spring developers

[Gary S. <lit...@ea...>]

Spring's concepts are clearly explained. Configuration is the confusing 
part. Snapshots of working configurations showing where config files 
belong in a directory tree or jar, war, ear file and example sets of 
config files should be straight forward to provide while being the most 
concrete guide for Spring users. I'd think you could come up with a good 
set from existing configurations.

Gary

Re: [Springframework-developer] Thanks to all the Spring developers

[Lars F. <lar...@gm...>]

Rob and Rod :-)

see below

> First and foremost more, better, free(hopefully) documentation, preferably
> as a PDF so it can be printed.  Your book is excellent, and well worth the
> price and I haven't even finished it.  (I've been swamped with stuff so I
> am only at the beginning of chapter 7, so I haven't even gotten to the
> juicy stuff.)  But, having to read a 680 page book in order to use a
framework
> sucks.

You can use the book without the framework and the framework without
the book. The framework outlined in the book is for the implementation
part but I agree that the book helps understanding the core concepts of
Spring.
 
> Even worse is that the framework has evolved since the time the book was
> printed (it doesn't cover hibernate, etc).  As time goes on I am sure the
> book, and the development of the framework will diverge even more.  A PDF
> available on the website could be kept up to date as the project evolves
and
> always be a valuable resource for newbies to the framework, or a good
> reference for those who have been using it for a while.

IMO every book about software technology is outdated the day it is released.
I would be sad if the framework didn't evolve in the meantime. 
A PDF would be great but this should be no problem once the documentation
is ready.

> I would definetly recommend creating the doc in PDF format because it is
> much easier to read / digest offline, and can act as a good resource when
> internet access is not available.  HTML never prints nicely, even pages
that
> are "printer friendly".  The PDF docs available from the Hibernate project
> are excellent examples of quality free documentation for a project.

I agree, the whole Hibernate project is an excellent example how software
projects should be handled and it might even kill companies like the
producers
of CocoBase.

> I think a quality set of documentation with some good examples would go
> along way in making the use / understanding of Spring much easier.  It
would
> also help the frameworks user base grow.  Again, your book is worth every
> cent, and I highly recommend everyone get it, but not everyone is willing
to
> (or can) shell out $60 for a book on every framework and technology they
> are trying out or considering for use.

We should not forget that Spring is beta and documentation will grow as time
goes by and the user base grows. For many frameworks there isn't any book
at all (so it could be worse).
I think the tutorial is very important -  new users  should get started very
fast
without having to try for hours to get the whole thing working. 
There is a lot of documentation (even in the source) which is great but
sometimes
I think it's too abstract to get an immediate result.

My wishlist:

- One big example showing all the stuff at enterprise level
- Many small examples where you can lookup specific things (this
   is one point where WebWork 1 is great). I would like to have 
   examples for Hibernate and several of the template classes.
- The examples should reflect the skeletons (Petclinic doesn't use 
   transactions and so on)
- One thing I don't like is this XML hell (just like in EJBs) . The sad
   thing is I don't know how to do it better. For a web application there
   are many things you have to configure (several resolvers, etc.). This is 
   where WebWork (1) is much easier to understand.

> A second reason to provide quality docs is it reflects well on the
> project.  I investigated Hibernate and Object Bridge.  Eventually I
decided that
> Hibernate was the way to go (for many many reasons).  But what immediately
> impressed me with the Hibernate project was the quality of its
> documentation.  I immediately felt that the project was going to be high
in quality
> because the time, effort and quality of the (free) documentation was very
high.
>  
> 
> Also consider that there are many other frameworks around on the net, all
> of them just a click away.  Sometimes you only have a few precious seconds
> to impress a potential user before they click onto the next project. 
Other
> frameworks like Struts have an abundance of free documentation and
> tutorials as articles on a variety of websites.  Plus Struts has a variety
of
> books available too.  These are even more reasons to create high quality
> documentation for spring in addition to your existing book.

I don't know any framework comparable to Spring. Many of them are only
MVC frameworks and can't be compared to Spring. Others are proprietary,
expensive or just not good enough. 

I cannot say anything about Struts because I never used it for technical
reasons. How is the quality of the books ? 8 out of 10 computer books
are just reflections of APIs and this is where Rod's book (and Spring) is
different.

All the users can help Spring improve because Spring developers care
about the given input. And that's a key to success ...

Regards
Lars
 
> > 
> > From: "Rod Johnson" <rod...@in...>
> > Date: 2003/08/28 Thu PM 03:34:50 EDT
> > To: "Lars Fischer" <lar...@gm...>, 
> >         <spr...@li...>
> > Subject: Re: [Springframework-developer] Thanks to all the Spring
> developers
> > 
> > Lars,
> > 
> > Thanks for your kind words.
> > 
> > Regarding the learning curve, any suggestions on what we can do to make
> > Spring easier to learn are welcome. I don't think Spring is inherently
> > complex, although it does do a lot. But I do appreciate that getting to
> > grips with it--especially in combination with other products such as
> > Hibernate--may be a challenge, and I want to try to change that.
> > 
> > Regards,
> > Rod
> > 
> > ----- Original Message -----
> > From: "Lars Fischer" <lar...@gm...>
> > To: <spr...@li...>
> > Sent: Thursday, August 28, 2003 8:12 PM
> > Subject: [Springframework-developer] Thanks to all the Spring developers
> > 
> > 
> > > This is a message to all Spring developers and potential users of
> Spring.
> > >
> > > This week I've managed to get a first prototype with Spring and
> Hibernate
> > > (two completely new technologies for me) working.  The biggest problem
> > > was to get the configuration working (and a 'little' WebLogic
> problem).
> > >
> > > Spring has a high learning curve at the beginning because it's a full
> > > featured
> > > framework for nearly all your needs.
> > >
> > > If you are willing to invest some time and get things working you will
> > > understand
> > > more and more what it's all about.
> > >
> > > Spring can help you to get rid of all these annoying problems with
> EJBs
> > and
> > > the related patterns only used to avoid performance problems. And
> despite
> > > the
> > > fact that the learning curve maybe high, you just have to learn ONE
> > > framework.
> > >
> > > If you want to keep existing technologies Spring is fine too (just use
> > > the needed parts).
> > >
> > > As a result of my experriences I can highly recommend the use of the
> > Spring
> > > framework, for me this is an outstanding peace of software with
> > > outstanding developers.
> > >
> > > In the past year I've developed a larger application with EJBs. It's
> > working
> > > very well (emtremely fast, scalable and stable).  Today I'd use Spring
> > which
> > > is
> > > much more elegant and makes you independant of the application server
> > > vendor.
> > >
> > > If someone reading this is in the situation of deciding whether to use
> > > Spring or
> > > not, my recommandation is to give it a try and you won't be
> disappointed !
> > >
> > > My thanks go to all Spring developers for providing such a great
> framework
> > !
> > >
> > > Regards
> > > Lars
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > Springframework-developer mailing list
> > > Spr...@li...
> > > https://lists.sourceforge.net/lists/listinfo/springframework-developer
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Springframework-developer mailing list
> > Spr...@li...
> > https://lists.sourceforge.net/lists/listinfo/springframework-developer
> > 
> 

Re: [Springframework-developer] Thanks to all the Spring developers

[<jue...@we...>]

Rmlyc3Qgb2YgYWxsLCB0aGFua3MgZm9yIHRoZSBwcmFpc2UsIExhcnMhIEl0J3MgYSBwbGVhc3Vy
ZSB0byBzZWUgdGhhdCB5b3UgZmluYWxseSBtYW5hZ2VkIHRvIGdldCBhIFNwcmluZy9IaWJlcm5h
dGUgY29tYm8gcnVuIG9uIFdlYkxvZ2ljLiBJIGhvcGUgeW91ciB1cGNvbWluZyBlZmZvcnRzIHdp
dGggU3ByaW5nIHdpbGwgbm90IGNhdXNlIHNvIG11Y2ggaGVhZGFjaGUgOy0pDQogDQpSb2IsIHJl
Z2FyZGluZyBkb2N1bWVudGF0aW9uOiBJIGZ1bGx5IGFncmVlIHRoYXQgdGhlcmUncyBzdGlsbCBh
IGxvdCB0byBkbyBpbiB0aGF0IHJlc3BlY3QuIE9mIGNvdXJzZSwgbm9vbmUgb2YgdXMgaXMgd29y
a2luZyBvbiBTcHJpbmcgZnVsbCB0aW1lIG9yIGdldHRpbmcgcGFpZCBmb3IgdGhlIGNvbW11bml0
eSBlZmZvcnRzLiBJIHBlcnNvbmFsbHkgYWltIHRvIHdyaXRlIGFzIG11Y2ggZG9jdW1lbnRhdGlv
biBhcyBwb3NzaWJsZSwgYnV0IHRpbWUgaXMgbGltaXRlZCwgYW5kIHRoZXJlJ3Mgc3RpbGwgc28g
bXVjaCBmcmFtZXdvcmsgZGV2ZWxvcG1lbnQgZ29pbmcgb24uIEknbSBhd2FyZSB0aGF0IHRoZSBj
dXJyZW50IGFydGljbGVzIG9uIG91ciB3ZWJzaXRlIGFyZSBqdXN0IGEgc3RhcnQuIFdlIGRvIG5l
ZWQgbW9yZSBjb21wcmVoZW5zaXZlIGRvY3MgdGhhdCBmaXQgZXZlcnl0aGluZyB0b2dldGhlci4N
CiANCkJUVywgd2UgaGF2ZSBzb21lIHBsYW5zIGZvciBhdXR1bW46IEEgVFNTIGFydGljbGUgb24g
U3ByaW5nIGlzIGNvbWluZyBzb29uLCBhbmQgd2UndmUgYmVlbiBpbnZpdGVkIHRvIGNyZWF0ZSBh
IFNwcmluZy9IaWJlcm5hdGUgc2FtcGxlIGFwcCBmb3IgaW5jbHVzaW9uIGluIHRoZSBIaWJlcm5h
dGUgRXhhbXBsZXMgZGlzdHJpYnV0aW9uLiBJIGFsc28gcGxhbiB0byB0dXJuIHRoZSBhcnRpY2xl
IGluIHRoZSBIaWJlcm5hdGUgY29tbXVuaXR5IGFyZWEgaW50byBhIHdob2xlIFNwcmluZyBzZWN0
aW9uIHdpdGggbXVsdGlwbGUgYXJ0aWNsZXMgYW5kIGV4YW1wbGVzLg0KIA0KVGhlIGFidW5kYW5j
ZSBvZiBkb2N1bWVudGF0aW9uIGlzIFN0cnV0cycgYmlnZ2VzdCBwbHVzLCBJTU8uIFdlYldvcmsg
YW5kIG90aGVycyBhcmUgZmFyIGJlaGluZCBpbiB0aGF0IHJlc3BlY3QsIGFuZCBzbyBhcmUgd2Ug
aW4gdGVybXMgb2Ygb3VyIHdlYiBNVkMuIE9mIGNvdXJzZSwgd2UndmUgZ290IHRoZSBhZHZhbnRh
Z2UgdGhhdCBTcHJpbmcgY2FuIGFsc28gc2VydmUgYXMgbWlkZGxlIHRpZXIgZnJhbWV3b3JrIGZv
ciBhIFN0cnV0cyBhcHBsaWNhdGlvbiwgYXMgaXQgb2ZmZXJzIG11Y2ggbW9yZSBraW5kcyBvZiBm
dW5jdGlvbmFsaXR5LiBUaGF0J3MgZ2VuZXJhbGx5IG9uZSBvZiBvdXIgYmlnZ2VzdCBzdHJlbmd0
aHM6IFdlIG9mZmVyIHVuaXF1ZSBmZWF0dXJlcyB0aGF0IGRvbid0IGhhdmUgbXVjaCBjb21wZXRp
dGlvbiB5ZXQuDQogDQpBcyBhbiBhc2lkZSwgaGF2ZSB5b3Ugbm90aWNlZCB0aGF0IExvZzRKJ3Mg
ZG9jdW1lbnRhdGlvbiBpcyBzdGlsbCBwcmV0dHkgc3BhcnNlIGRlc3BpdGUgaXRzIGxvbmcgdHJh
Y2sgcmVjb3JkPyBPSywgdGhlcmUncyBhIGJvb2sgb3V0IG9uIGl0LCBidXQgYmFzaWNhbGx5IGV2
ZXJ5b25lIGxlYXJucyBob3cgdG8gY29uZmlndXJlIGl0IGJ5IGV4YW1wbGUgb3IgZnJvbSBzY3Jh
dGNoLiBNb3JlIGRldGFpbGVkIGRvY3Mgd291bGQgYmUgbmljZSB0aGVyZSwgdG9vLg0KIA0KSnVl
cmdlbg0KIA0KIA0KDQoJLS0tLS1VcnNwcsO8bmdsaWNoZSBOYWNocmljaHQtLS0tLSANCglWb246
IFJvYiBCdXRsZXIgW21haWx0bzpyb2JlcnQuYnV0bGVyNUB2ZXJpem9uLm5ldF0gDQoJR2VzZW5k
ZXQ6IERvIDI4LjA4LjIwMDMgMjI6NDIgDQoJQW46IHNwcmluZ2ZyYW1ld29yay1kZXZlbG9wZXJA
bGlzdHMuc291cmNlZm9yZ2UubmV0IA0KCUNjOiByb2Quam9obnNvbkBpbnRlcmZhY2UyMS5jb207
IGxhcnMuZmlzY2hlckBnbXhwcm8ubmV0IA0KCUJldHJlZmY6IFJlOiBbU3ByaW5nZnJhbWV3b3Jr
LWRldmVsb3Blcl0gVGhhbmtzIHRvIGFsbCB0aGUgU3ByaW5nIGRldmVsb3BlcnMNCgkNCgkNCg0K
CVJvZCwNCgkNCglGaXJzdCBhbmQgZm9yZW1vc3QgbW9yZSwgYmV0dGVyLCBmcmVlKGhvcGVmdWxs
eSkgZG9jdW1lbnRhdGlvbiwgcHJlZmVyYWJseSBhcyBhIFBERiBzbyBpdCBjYW4gYmUgcHJpbnRl
ZC4gIFlvdXIgYm9vayBpcyBleGNlbGxlbnQsIGFuZCB3ZWxsIHdvcnRoIHRoZSBwcmljZSBhbmQg
SSBoYXZlbid0IGV2ZW4gZmluaXNoZWQgaXQuICAoSSd2ZSBiZWVuIHN3YW1wZWQgd2l0aCBzdHVm
ZiBzbyBJIGFtIG9ubHkgYXQgdGhlIGJlZ2lubmluZyBvZiBjaGFwdGVyIDcsIHNvIEkgaGF2ZW4n
dCBldmVuIGdvdHRlbiB0byB0aGUganVpY3kgc3R1ZmYuKSAgQnV0LCBoYXZpbmcgdG8gcmVhZCBh
IDY4MCBwYWdlIGJvb2sgaW4gb3JkZXIgdG8gdXNlIGEgZnJhbWV3b3JrIHN1Y2tzLg0KCQ0KCUV2
ZW4gd29yc2UgaXMgdGhhdCB0aGUgZnJhbWV3b3JrIGhhcyBldm9sdmVkIHNpbmNlIHRoZSB0aW1l
IHRoZSBib29rIHdhcyBwcmludGVkIChpdCBkb2Vzbid0IGNvdmVyIGhpYmVybmF0ZSwgZXRjKS4g
IEFzIHRpbWUgZ29lcyBvbiBJIGFtIHN1cmUgdGhlIGJvb2ssIGFuZCB0aGUgZGV2ZWxvcG1lbnQg
b2YgdGhlIGZyYW1ld29yayB3aWxsIGRpdmVyZ2UgZXZlbiBtb3JlLiAgQSBQREYgYXZhaWxhYmxl
IG9uIHRoZSB3ZWJzaXRlIGNvdWxkIGJlIGtlcHQgdXAgdG8gZGF0ZSBhcyB0aGUgcHJvamVjdCBl
dm9sdmVzIGFuZCBhbHdheXMgYmUgYSB2YWx1YWJsZSByZXNvdXJjZSBmb3IgbmV3YmllcyB0byB0
aGUgZnJhbWV3b3JrLCBvciBhIGdvb2QgcmVmZXJlbmNlIGZvciB0aG9zZSB3aG8gaGF2ZSBiZWVu
IHVzaW5nIGl0IGZvciBhIHdoaWxlLg0KCQ0KCUkgd291bGQgZGVmaW5ldGx5IHJlY29tbWVuZCBj
cmVhdGluZyB0aGUgZG9jIGluIFBERiBmb3JtYXQgYmVjYXVzZSBpdCBpcyBtdWNoIGVhc2llciB0
byByZWFkIC8gZGlnZXN0IG9mZmxpbmUsIGFuZCBjYW4gYWN0IGFzIGEgZ29vZCByZXNvdXJjZSB3
aGVuIGludGVybmV0IGFjY2VzcyBpcyBub3QgYXZhaWxhYmxlLiAgSFRNTCBuZXZlciBwcmludHMg
bmljZWx5LCBldmVuIHBhZ2VzIHRoYXQgYXJlICJwcmludGVyIGZyaWVuZGx5Ii4gIFRoZSBQREYg
ZG9jcyBhdmFpbGFibGUgZnJvbSB0aGUgSGliZXJuYXRlIHByb2plY3QgYXJlIGV4Y2VsbGVudCBl
eGFtcGxlcyBvZiBxdWFsaXR5IGZyZWUgZG9jdW1lbnRhdGlvbiBmb3IgYSBwcm9qZWN0Lg0KCQ0K
CUkgdGhpbmsgYSBxdWFsaXR5IHNldCBvZiBkb2N1bWVudGF0aW9uIHdpdGggc29tZSBnb29kIGV4
YW1wbGVzIHdvdWxkIGdvIGFsb25nIHdheSBpbiBtYWtpbmcgdGhlIHVzZSAvIHVuZGVyc3RhbmRp
bmcgb2YgU3ByaW5nIG11Y2ggZWFzaWVyLiAgSXQgd291bGQgYWxzbyBoZWxwIHRoZSBmcmFtZXdv
cmtzIHVzZXIgYmFzZSBncm93LiAgQWdhaW4sIHlvdXIgYm9vayBpcyB3b3J0aCBldmVyeSBjZW50
LCBhbmQgSSBoaWdobHkgcmVjb21tZW5kIGV2ZXJ5b25lIGdldCBpdCwgYnV0IG5vdCBldmVyeW9u
ZSBpcyB3aWxsaW5nIHRvIChvciBjYW4pIHNoZWxsIG91dCAkNjAgZm9yIGEgYm9vayBvbiBldmVy
eSBmcmFtZXdvcmsgYW5kIHRlY2hub2xvZ3kgdGhleSBhcmUgdHJ5aW5nIG91dCBvciBjb25zaWRl
cmluZyBmb3IgdXNlLg0KCQ0KCUEgc2Vjb25kIHJlYXNvbiB0byBwcm92aWRlIHF1YWxpdHkgZG9j
cyBpcyBpdCByZWZsZWN0cyB3ZWxsIG9uIHRoZSBwcm9qZWN0LiAgSSBpbnZlc3RpZ2F0ZWQgSGli
ZXJuYXRlIGFuZCBPYmplY3QgQnJpZGdlLiAgRXZlbnR1YWxseSBJIGRlY2lkZWQgdGhhdCBIaWJl
cm5hdGUgd2FzIHRoZSB3YXkgdG8gZ28gKGZvciBtYW55IG1hbnkgcmVhc29ucykuICBCdXQgd2hh
dCBpbW1lZGlhdGVseSBpbXByZXNzZWQgbWUgd2l0aCB0aGUgSGliZXJuYXRlIHByb2plY3Qgd2Fz
IHRoZSBxdWFsaXR5IG9mIGl0cyBkb2N1bWVudGF0aW9uLiAgSSBpbW1lZGlhdGVseSBmZWx0IHRo
YXQgdGhlIHByb2plY3Qgd2FzIGdvaW5nIHRvIGJlIGhpZ2ggaW4gcXVhbGl0eSBiZWNhdXNlIHRo
ZSB0aW1lLCBlZmZvcnQgYW5kIHF1YWxpdHkgb2YgdGhlIChmcmVlKSBkb2N1bWVudGF0aW9uIHdh
cyB2ZXJ5IGhpZ2guIA0KCQ0KCUFsc28gY29uc2lkZXIgdGhhdCB0aGVyZSBhcmUgbWFueSBvdGhl
ciBmcmFtZXdvcmtzIGFyb3VuZCBvbiB0aGUgbmV0LCBhbGwgb2YgdGhlbSBqdXN0IGEgY2xpY2sg
YXdheS4gIFNvbWV0aW1lcyB5b3Ugb25seSBoYXZlIGEgZmV3IHByZWNpb3VzIHNlY29uZHMgdG8g
aW1wcmVzcyBhIHBvdGVudGlhbCB1c2VyIGJlZm9yZSB0aGV5IGNsaWNrIG9udG8gdGhlIG5leHQg
cHJvamVjdC4gIE90aGVyIGZyYW1ld29ya3MgbGlrZSBTdHJ1dHMgaGF2ZSBhbiBhYnVuZGFuY2Ug
b2YgZnJlZSBkb2N1bWVudGF0aW9uIGFuZCB0dXRvcmlhbHMgYXMgYXJ0aWNsZXMgb24gYSB2YXJp
ZXR5IG9mIHdlYnNpdGVzLiAgUGx1cyBTdHJ1dHMgaGFzIGEgdmFyaWV0eSBvZiBib29rcyBhdmFp
bGFibGUgdG9vLiAgVGhlc2UgYXJlIGV2ZW4gbW9yZSByZWFzb25zIHRvIGNyZWF0ZSBoaWdoIHF1
YWxpdHkgZG9jdW1lbnRhdGlvbiBmb3Igc3ByaW5nIGluIGFkZGl0aW9uIHRvIHlvdXIgZXhpc3Rp
bmcgYm9vay4NCgkNCglKdXN0IG15IG9waW5pb24uDQoJDQoJTGF0ZXINCglSb2INCgkNCgk+DQoJ
PiBGcm9tOiAiUm9kIEpvaG5zb24iIDxyb2Quam9obnNvbkBpbnRlcmZhY2UyMS5jb20+DQoJPiBE
YXRlOiAyMDAzLzA4LzI4IFRodSBQTSAwMzozNDo1MCBFRFQNCgk+IFRvOiAiTGFycyBGaXNjaGVy
IiA8bGFycy5maXNjaGVyQGdteHByby5uZXQ+LA0KCT4gICAgICAgICA8c3ByaW5nZnJhbWV3b3Jr
LWRldmVsb3BlckBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQ+DQoJPiBTdWJqZWN0OiBSZTogW1Nwcmlu
Z2ZyYW1ld29yay1kZXZlbG9wZXJdIFRoYW5rcyB0byBhbGwgdGhlIFNwcmluZyBkZXZlbG9wZXJz
DQoJPg0KCT4gTGFycywNCgk+DQoJPiBUaGFua3MgZm9yIHlvdXIga2luZCB3b3Jkcy4NCgk+DQoJ
PiBSZWdhcmRpbmcgdGhlIGxlYXJuaW5nIGN1cnZlLCBhbnkgc3VnZ2VzdGlvbnMgb24gd2hhdCB3
ZSBjYW4gZG8gdG8gbWFrZQ0KCT4gU3ByaW5nIGVhc2llciB0byBsZWFybiBhcmUgd2VsY29tZS4g
SSBkb24ndCB0aGluayBTcHJpbmcgaXMgaW5oZXJlbnRseQ0KCT4gY29tcGxleCwgYWx0aG91Z2gg
aXQgZG9lcyBkbyBhIGxvdC4gQnV0IEkgZG8gYXBwcmVjaWF0ZSB0aGF0IGdldHRpbmcgdG8NCgk+
IGdyaXBzIHdpdGggaXQtLWVzcGVjaWFsbHkgaW4gY29tYmluYXRpb24gd2l0aCBvdGhlciBwcm9k
dWN0cyBzdWNoIGFzDQoJPiBIaWJlcm5hdGUtLW1heSBiZSBhIGNoYWxsZW5nZSwgYW5kIEkgd2Fu
dCB0byB0cnkgdG8gY2hhbmdlIHRoYXQuDQoJPg0KCT4gUmVnYXJkcywNCgk+IFJvZA0KCT4NCgk+
IC0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCgk+IEZyb206ICJMYXJzIEZpc2NoZXIiIDxs
YXJzLmZpc2NoZXJAZ214cHJvLm5ldD4NCgk+IFRvOiA8c3ByaW5nZnJhbWV3b3JrLWRldmVsb3Bl
ckBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQ+DQoJPiBTZW50OiBUaHVyc2RheSwgQXVndXN0IDI4LCAy
MDAzIDg6MTIgUE0NCgk+IFN1YmplY3Q6IFtTcHJpbmdmcmFtZXdvcmstZGV2ZWxvcGVyXSBUaGFu
a3MgdG8gYWxsIHRoZSBTcHJpbmcgZGV2ZWxvcGVycw0KCT4NCgk+DQoJPiA+IFRoaXMgaXMgYSBt
ZXNzYWdlIHRvIGFsbCBTcHJpbmcgZGV2ZWxvcGVycyBhbmQgcG90ZW50aWFsIHVzZXJzIG9mIFNw
cmluZy4NCgk+ID4NCgk+ID4gVGhpcyB3ZWVrIEkndmUgbWFuYWdlZCB0byBnZXQgYSBmaXJzdCBw
cm90b3R5cGUgd2l0aCBTcHJpbmcgYW5kIEhpYmVybmF0ZQ0KCT4gPiAodHdvIGNvbXBsZXRlbHkg
bmV3IHRlY2hub2xvZ2llcyBmb3IgbWUpIHdvcmtpbmcuICBUaGUgYmlnZ2VzdCBwcm9ibGVtDQoJ
PiA+IHdhcyB0byBnZXQgdGhlIGNvbmZpZ3VyYXRpb24gd29ya2luZyAoYW5kIGEgJ2xpdHRsZScg
V2ViTG9naWMgcHJvYmxlbSkuDQoJPiA+DQoJPiA+IFNwcmluZyBoYXMgYSBoaWdoIGxlYXJuaW5n
IGN1cnZlIGF0IHRoZSBiZWdpbm5pbmcgYmVjYXVzZSBpdCdzIGEgZnVsbA0KCT4gPiBmZWF0dXJl
ZA0KCT4gPiBmcmFtZXdvcmsgZm9yIG5lYXJseSBhbGwgeW91ciBuZWVkcy4NCgk+ID4NCgk+ID4g
SWYgeW91IGFyZSB3aWxsaW5nIHRvIGludmVzdCBzb21lIHRpbWUgYW5kIGdldCB0aGluZ3Mgd29y
a2luZyB5b3Ugd2lsbA0KCT4gPiB1bmRlcnN0YW5kDQoJPiA+IG1vcmUgYW5kIG1vcmUgd2hhdCBp
dCdzIGFsbCBhYm91dC4NCgk+ID4NCgk+ID4gU3ByaW5nIGNhbiBoZWxwIHlvdSB0byBnZXQgcmlk
IG9mIGFsbCB0aGVzZSBhbm5veWluZyBwcm9ibGVtcyB3aXRoIEVKQnMNCgk+IGFuZA0KCT4gPiB0
aGUgcmVsYXRlZCBwYXR0ZXJucyBvbmx5IHVzZWQgdG8gYXZvaWQgcGVyZm9ybWFuY2UgcHJvYmxl
bXMuIEFuZCBkZXNwaXRlDQoJPiA+IHRoZQ0KCT4gPiBmYWN0IHRoYXQgdGhlIGxlYXJuaW5nIGN1
cnZlIG1heWJlIGhpZ2gsIHlvdSBqdXN0IGhhdmUgdG8gbGVhcm4gT05FDQoJPiA+IGZyYW1ld29y
ay4NCgk+ID4NCgk+ID4gSWYgeW91IHdhbnQgdG8ga2VlcCBleGlzdGluZyB0ZWNobm9sb2dpZXMg
U3ByaW5nIGlzIGZpbmUgdG9vIChqdXN0IHVzZQ0KCT4gPiB0aGUgbmVlZGVkIHBhcnRzKS4NCgk+
ID4NCgk+ID4gQXMgYSByZXN1bHQgb2YgbXkgZXhwZXJyaWVuY2VzIEkgY2FuIGhpZ2hseSByZWNv
bW1lbmQgdGhlIHVzZSBvZiB0aGUNCgk+IFNwcmluZw0KCT4gPiBmcmFtZXdvcmssIGZvciBtZSB0
aGlzIGlzIGFuIG91dHN0YW5kaW5nIHBlYWNlIG9mIHNvZnR3YXJlIHdpdGgNCgk+ID4gb3V0c3Rh
bmRpbmcgZGV2ZWxvcGVycy4NCgk+ID4NCgk+ID4gSW4gdGhlIHBhc3QgeWVhciBJJ3ZlIGRldmVs
b3BlZCBhIGxhcmdlciBhcHBsaWNhdGlvbiB3aXRoIEVKQnMuIEl0J3MNCgk+IHdvcmtpbmcNCgk+
ID4gdmVyeSB3ZWxsIChlbXRyZW1lbHkgZmFzdCwgc2NhbGFibGUgYW5kIHN0YWJsZSkuICBUb2Rh
eSBJJ2QgdXNlIFNwcmluZw0KCT4gd2hpY2gNCgk+ID4gaXMNCgk+ID4gbXVjaCBtb3JlIGVsZWdh
bnQgYW5kIG1ha2VzIHlvdSBpbmRlcGVuZGFudCBvZiB0aGUgYXBwbGljYXRpb24gc2VydmVyDQoJ
PiA+IHZlbmRvci4NCgk+ID4NCgk+ID4gSWYgc29tZW9uZSByZWFkaW5nIHRoaXMgaXMgaW4gdGhl
IHNpdHVhdGlvbiBvZiBkZWNpZGluZyB3aGV0aGVyIHRvIHVzZQ0KCT4gPiBTcHJpbmcgb3INCgk+
ID4gbm90LCBteSByZWNvbW1hbmRhdGlvbiBpcyB0byBnaXZlIGl0IGEgdHJ5IGFuZCB5b3Ugd29u
J3QgYmUgZGlzYXBwb2ludGVkICENCgk+ID4NCgk+ID4gTXkgdGhhbmtzIGdvIHRvIGFsbCBTcHJp
bmcgZGV2ZWxvcGVycyBmb3IgcHJvdmlkaW5nIHN1Y2ggYSBncmVhdCBmcmFtZXdvcmsNCgk+ICEN
Cgk+ID4NCgk+ID4gUmVnYXJkcw0KCT4gPiBMYXJzDQoJPiA+DQoJPiA+DQoJPiA+DQoJPiA+IC0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCgk+
ID4gVGhpcyBzZi5uZXQgZW1haWwgaXMgc3BvbnNvcmVkIGJ5OlRoaW5rR2Vlaw0KCT4gPiBXZWxj
b21lIHRvIGdlZWsgaGVhdmVuLg0KCT4gPiBodHRwOi8vdGhpbmtnZWVrLmNvbS9zZg0KCT4gPiBf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KCT4gPiBTcHJp
bmdmcmFtZXdvcmstZGV2ZWxvcGVyIG1haWxpbmcgbGlzdA0KCT4gPiBTcHJpbmdmcmFtZXdvcmst
ZGV2ZWxvcGVyQGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KCT4gPiBodHRwczovL2xpc3RzLnNvdXJj
ZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9zcHJpbmdmcmFtZXdvcmstZGV2ZWxvcGVyDQoJPg0K
CT4NCgk+DQoJPg0KCT4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLQ0KCT4gVGhpcyBzZi5uZXQgZW1haWwgaXMgc3BvbnNvcmVkIGJ5OlRoaW5r
R2Vlaw0KCT4gV2VsY29tZSB0byBnZWVrIGhlYXZlbi4NCgk+IGh0dHA6Ly90aGlua2dlZWsuY29t
L3NmDQoJPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K
CT4gU3ByaW5nZnJhbWV3b3JrLWRldmVsb3BlciBtYWlsaW5nIGxpc3QNCgk+IFNwcmluZ2ZyYW1l
d29yay1kZXZlbG9wZXJAbGlzdHMuc291cmNlZm9yZ2UubmV0DQoJPiBodHRwczovL2xpc3RzLnNv
dXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9zcHJpbmdmcmFtZXdvcmstZGV2ZWxvcGVyDQoJ
Pg0KCQ0KCQ0KCQ0KCS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0NCglUaGlzIHNmLm5ldCBlbWFpbCBpcyBzcG9uc29yZWQgYnk6VGhpbmtHZWVr
DQoJV2VsY29tZSB0byBnZWVrIGhlYXZlbi4NCglodHRwOi8vdGhpbmtnZWVrLmNvbS9zZg0KCV9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoJU3ByaW5nZnJh
bWV3b3JrLWRldmVsb3BlciBtYWlsaW5nIGxpc3QNCglTcHJpbmdmcmFtZXdvcmstZGV2ZWxvcGVy
QGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KCWh0dHBzOi8vbGlzdHMuc291cmNlZm9yZ2UubmV0L2xp
c3RzL2xpc3RpbmZvL3NwcmluZ2ZyYW1ld29yay1kZXZlbG9wZXINCgkNCg0K

Re: [Springframework-developer] Example classes needed

[<jue...@we...>]

T29wcywgSSBkaWQgaW50ZW5kIHRvIGNvbW1lbnQgb24gdGhhdCBidXQgZm9yZ290IHNvbWVob3cg
Oy0pDQogDQpXZSd2ZSBkaXNjdXNzZWQgdGhhdCBhdCBudW1lcm91cyB0aW1lcyBhbHJlYWR5LCBh
bmQgaXQgc2VlbXMgdGhhdCB0aGVyZSBhcmUgMiBiYXNpYyBzdHJhdGVnaWVzIGZvciBtdWx0aXBs
ZSBqYXIgZmlsZXM6DQogDQotIHNlcGFyYXRpb24gYnkgcGFja2FnZXMvY29tcG9uZW50cyBwbHVz
IG9uZSB3aXRoIGV2ZXJ5dGhpbmc6IHdpdGggdGhlIG5lZWQgdG8gY29tYmluZSBtdWx0aXBsZSBq
YXJzIGludG8gd29ya2luZyBsaWJyYXJpZXMgKHdlIGhhZCB0aGF0IGJlZm9yZSAwLjkpOw0KIA0K
LSB2YXJpb3VzIGphcnMgZm9yIGRpZmZlcmVudCB1c2FnZSBzY2VuYXJpb3MgaW5jbHVkaW5nIG9u
ZSB3aXRoIGV2ZXJ5dGhpbmc6IG9uZSBhcHByb3ByaWF0ZSBsaWJyYXJ5IHBlciBzY2VuYXJpbywg
YnV0IG92ZXJsYXBwaW5nIGNvbnRlbnRzIChzaW5jZSAwLjkpLg0KIA0KTGFzdCB0aW1lIHdlIGRp
c2N1c3NlZCB0aGVzZSBpc3N1ZXMsIHdlIHNldHRsZWQgb24gdGhlIGxhdHRlciwgYXMgaXQgc2Vl
bXMgZWFzaWVyIHRvIGFwcGx5LiBGb3IgZXhhbXBsZSwgc3ByaW5nLWJlYW5zIGhhcyBqdXN0IHRo
ZSBiYXJlIG1pbmltdW0gb2YgY29tbW9uIGNsYXNzZXMsIHRvIGZpdCB0aGUgY29yZSBiZWFuIGNv
bnRhaW5lciBpbiB+OTAgS0IgKGUuZy4gZm9yIHVzYWdlIHdpdGhpbiBhcHBsZXRzKS4gQSBzcHJp
bmctY29tbW9uIHdpdGggY29yZSBhbmQgdXRpbCBwYWNrYWdlcyBwbHVzIHNwcmluZy1iZWFucyB3
aXRoIGp1c3QgdGhlIGJlYW5zIHBhY2thZ2Ugd291bGQgYmUgPjExMCBLQi4NCiANCkJUVywgdGhh
dCBhcHBsZXQgZXhhbXBsZSBpc24ndCBtYWRlIHVwOiBXZSdyZSBhY3R1YWxseSB1c2luZyB0aGF0
IGF0IHdlcmszQVQgdG8gd2lyZSB1cCBiZWFucyB3aXRoaW4gYW4gaW1hZ2UgbWFuYWdlbWVudCBh
cHBsZXQuIFRoYXQgd29ya3MgbmljZWx5IHdpdGggYW4gWG1sQmVhbkZhY3RvcnkgYW5kIGFuIFhN
TCBmaWxlIGluIHRoZSBjbGFzc3BhdGguDQogDQpGb3IgMS4wIE0xLCBJJ3ZlIGluY3JlYXNlZCB0
aGUgbnVtYmVyIG9mIGphciBmaWxlcyB0byBwYXkgcmVzcGVjdCB0byBtb3JlIHNjZW5hcmlvcy4g
SSd2ZSBqdXN0IGRyb3BwZWQgc3ByaW5nLW9ybSB0aG91Z2gsIGFzIGl0IGRvZXNuJ3Qgc2VlbSBy
ZWFzb25hYmxlIG9uIHNlY29uZCB0aG91Z2h0LiBIaWJlcm5hdGUgYWxvbmUgaGFzIH43MDAgS0Ig
cGx1cyBhIGxvdCBvZiBleHRyYSBkZXBlbmRlbmNpZXMsIHNvIHdoeSBzYXZlIGEgZmV3IEtCIGZv
ciB1c2FnZSBvZiBTcHJpbmcgYXMgT1JNIGxpYnJhcnkuIHNwcmluZy1jb250ZXh0IGlzIGdvb2Qg
ZW5vdWdoIGZvciB0aGF0IHRvby4gU28gd2Ugbm93IGhhdmU6DQogDQotIHNwcmluZy1iZWFuczog
OTIgS0INCi0gc3ByaW5nLWFvcCAoaW5jbHVkaW5nIEpOREkgYW5kIEVKQiBzdXBwb3J0KTogMTc2
IEtCDQotIHNwcmluZy1qZGJjIChpbmNsdWRpbmcgdHJhbnNhY3Rpb24gc3VwcG9ydCk6IDMwNCBL
Qg0KLSBzcHJpbmctY29udGV4dCAoZXZlcnl0aGluZyB3aXRob3V0IHdlYiBNVkMpOiA0MzMgS0IN
Ci0gc3ByaW5nKC1mdWxsKTogNTYzIEtCDQogDQpUaGUgZXhhY3QgY29udGVudHMgYW5kIHRhcmdl
dHMgYXJlIG91dGxpbmVkIGluIHRoZSByZWFkbWUgZmlsZS4gV2l0aCB0aG9zZSA1IGphcnMsIGV2
ZXJ5IGJpZ2dlciBqYXIgaXMgYSBzdXBlcnNldCBvZiB0aGUgbG93ZXIgb25lcywgZS5nLiBzcHJp
bmctamRiYyBjb250YWlucyBldmVyeXRoaW5nIGZyb20gc3ByaW5nLWFvcCBhbmQgbW9yZS4NCiAN
Ckp1ZXJnZW4NCiANCiANCg0KCS0tLS0tVXJzcHLDvG5nbGljaGUgTmFjaHJpY2h0LS0tLS0gDQoJ
Vm9uOiBSb2IgQnV0bGVyIFttYWlsdG86cm9iZXJ0LmJ1dGxlcjVAdmVyaXpvbi5uZXRdIA0KCUdl
c2VuZGV0OiBEbyAyOC4wOC4yMDAzIDE5OjU0IA0KCUFuOiBqw7xyZ2VuIGjDtmxsZXIgW3dlcmsz
QVRdOyBsYXJzLmZpc2NoZXJAZ214cHJvLm5ldCANCglDYzogc3ByaW5nZnJhbWV3b3JrLWRldmVs
b3BlckBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQ7IHRyaXNiZXJnQHRyaWRiLmNvbTsgcm9kLmpvaG5z
b25AaW50ZXJmYWNlMjEuY29tIA0KCUJldHJlZmY6IFJFOiBbU3ByaW5nZnJhbWV3b3JrLWRldmVs
b3Blcl0gRXhhbXBsZSBjbGFzc2VzIG5lZWRlZA0KCQ0KCQ0KDQoNCglXaGF0IGFib3V0IHRoZSBv
dGhlciBpZGVhIG9mIHNwbGl0dGluZyBzcHJpbmcgdXAgaW50byBpdHMgImNvbXBvbmVudCIgcGll
Y2VzIHNvIHRoYXQgdXNlcnMgY2FuIHBpY2sgYW5kIGNob29zZSB0aGUgcGFydHMgdGhleSB3YW50
Pw0KCQ0KCUxhdGVyDQoJUm9iDQoJDQoJPg0KCT4gRnJvbTogasO8cmdlbiBow7ZsbGVyIFt3ZXJr
M0FUXSA8anVlcmdlbi5ob2VsbGVyQHdlcmszYXQuY29tPg0KCT4gRGF0ZTogMjAwMy8wOC8yOCBU
aHUgUE0gMDE6MTk6MjYgRURUDQoJPiBUbzogIlJvYiBCdXRsZXIiIDxyb2JlcnQuYnV0bGVyNUB2
ZXJpem9uLm5ldD4sDQoJPiAgICAgICAiTGFycyBGaXNjaGVyIiA8bGFycy5maXNjaGVyQGdteHBy
by5uZXQ+DQoJPiBDQzogPHNwcmluZ2ZyYW1ld29yay1kZXZlbG9wZXJAbGlzdHMuc291cmNlZm9y
Z2UubmV0PiwNCgk+ICAgICAgIDx0cmlzYmVyZ0B0cmlkYi5jb20+LA0KCT4gICAgICAgPHJvZC5q
b2huc29uQGludGVyZmFjZTIxLmNvbT4NCgk+IFN1YmplY3Q6IFJFOiBbU3ByaW5nZnJhbWV3b3Jr
LWRldmVsb3Blcl0gRXhhbXBsZSBjbGFzc2VzIG5lZWRlZA0KCT4NCgk+IEkndmUganVzdCBhZGRl
ZCBhIG1hbmlmZXN0IGVudHJ5ICJTcHJpbmctVmVyc2lvbiIgdG8gb3VyIGJ1aWxkIHNjcmlwdHMu
IFRoaXMgbWVhbnMgdGhhdCBhICJzcHJpbmcuamFyIiBmb3IgMS4wIE0xIHdpbGwgaW5jbHVkZSBh
ICJTcHJpbmctVmVyc2lvbj0xLjBtMSIgZW50cnkgaW4gaXRzIE1FVEEtSU5GL21hbmlmZXN0Lm1m
IGZpbGUuIFNvIGlmIHlvdSd2ZSBnb3QgamFyIGZpbGVzIGx5aW5nIGFyb3VuZCwgeW91IGNhbiBh
bHdheXMgY2hlY2sgdGhlIGV4YWN0IHZlcnNpb24uIFdpdGggdGhpcyBpbmNsdWRlZCwgSSB0ZW5k
IHRvIGRyb3AgdmVyc2lvbiBudW1iZXJzIGV2ZW4gbW9yZS4gVGhhbmtzIGZvciB0aGUgaWRlYSwg
Um9iIC0gSSBqdXN0IGd1ZXNzIGl0J3Mgc2ltcGxlciB0byBtYWtlIGEgbWFuaWZlc3QgZW50cnkg
dGhhbiB0byBpbmNsdWRlIGFuIGV4dHJhIGZpbGUuDQoJPg0KCT4gV2UgYWxsIHNlZW0gdG8gYWdy
ZWUgd2UgcHJlZmVyICJzcHJpbmcuamFyIiBvdmVyICJzcHJpbmctZnVsbC5qYXIiLCBidXQgYXJl
IGFib3V0IDUwOjUwIHJlZ2FyZGluZyB2ZXJzaW9uIG51bWJlcnMgaW4gdGhlIG5hbWUuIFNvIGxl
dCdzIGZvY3VzIG9uIHRoZSBsYXR0ZXI6IFdvdWxkIGFueW9uZSAqbWluZCogbm8gdmVyc2lvbiBu
dW1iZXIgaW4gdGhlIG5hbWUsIGdpdmVuIHRoYXQgaXQncyBtZW50aW9uZWQgaW4gdGhlIG1hbmlm
ZXN0IGZpbGU/IEV2ZXJ5b25lIGlzIGZyZWUgdG8gcmVuYW1lIHRoZSBmaWxlcyBhbnkgd2F5IGhl
IHdhbnRzIGFueXdheSwgaXQncyBqdXN0IGFib3V0IHRoZSBzaGlwcGVkIGphcnMuIEFzIGZvciBt
ZSwgSSB3b3VsZCBtaW5kIHRoZSBmdWxsIHZlcnNpb24gbnVtYmVyICIxLjBtMSIgLSBpbiB0aGUg
bWVhbnRpbWUsIEkgZXZlbiBwcmVmZXIgInNwcmluZy5qYXIiLg0KCT4NCgk+IFRvIGtlZXAgdGhl
IGZpcmUgYnVybmluZywgc29tZSBleGFtcGxlcyBmb3Igbm8gdmVyc2lvbiBudW1iZXJzIHRoYXQg
SSBrbm93IG9mOiBTZXJ2bGV0LCBKVW5pdCwgSmF2YU1haWwsIFhlcmNlcywgSlNUTCwgQ29tbW9u
cyBMb2dnaW5nLCBDb21tb25zIERCQ1AsIFhBUG9vbCwgSGliZXJuYXRlLCBDT1MsIEdMVUUsIEFu
dCwgVG9tY2F0LCBKQm9zcywgQ2xvdmVyLiBDb3VudGVyZXhhbXBsZXMgd2l0aCB2ZXJzaW9uIG51
bWJlcnMgaW4gdGhlIGphciBuYW1lOiBKVEEsIENHTElCLCBCQ0VMLCBMb2c0SiwgQ2FzdG9yLCBU
eXJleCwgVmVsb2NpdHksIFRhcGVzdHJ5LCBIZXNzaWFuLCBpVGV4dCwgTXlTUUwgSkRCQyBkcml2
ZXIuDQoJPg0KCT4gSW4gdGhlIGVuZCwgb25lIGNhbiBhcmd1ZSBmb3IgYWxsIG9wdGlvbnMuIFRo
ZXJlIGlzIG5vIG9idmlvdXMgc29sdXRpb24uIFNvIHdlIHNob3VsZCB0cnkgdG8gc2V0dGxlIG9u
IG9uZSBvcHRpb24gYW5kIHN0aWNrIHdpdGggaXQuDQoJPg0KCT4gSnVlcmdlbg0KCT4NCgk+DQoJ
PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KCT4gRnJvbTogUm9iIEJ1dGxlciBbbWFpbHRv
OnJvYmVydC5idXRsZXI1QHZlcml6b24ubmV0XQ0KCT4gU2VudDogVGh1cnNkYXksIEF1Z3VzdCAy
OCwgMjAwMyA2OjM0IFBNDQoJPiBUbzogasO8cmdlbiBow7ZsbGVyIFt3ZXJrM0FUXTsgTGFycyBG
aXNjaGVyDQoJPiBDYzogc3ByaW5nZnJhbWV3b3JrLWRldmVsb3BlckBsaXN0cy5zb3VyY2Vmb3Jn
ZS5uZXQ7IHRyaXNiZXJnQHRyaWRiLmNvbTsNCgk+IHJvZC5qb2huc29uQGludGVyZmFjZTIxLmNv
bQ0KCT4gU3ViamVjdDogUkU6IFtTcHJpbmdmcmFtZXdvcmstZGV2ZWxvcGVyXSBFeGFtcGxlIGNs
YXNzZXMgbmVlZGVkDQoJPg0KCT4NCgk+IEhlbGxvIGFsbCwNCgk+DQoJPiBTaW5jZSBzcHJpbmcg
aXMgbW9kdWxhciwgd2h5IG5vdCBicmVhayBpdCBkb3duIGV2ZW4gZnVydGhlciBpbnRvIGNodW5j
a3MuDQoJPg0KCT4gc3ByaW5nLWNvbW1vbi5qYXIgLT5CYXNpYyBzdHVmZiB0aGF0IGlzIHVzZWQg
ZXZlcnl3aGVyZSBpbiBzcHJpbmcNCgk+IHNwcmluZy1iZWFucy5qYXIgLT4gY29udGFpbnMgT05M
WSB0aGUgU3ByaW5nIEJlYW5zIHN0dWZmLg0KCT4gc3ByaW5nLWFvcC5qYXIgLT4gY29udGFpbnMg
T05MWSB0aGUgU3ByaW5nIEFPUCBzdHVmZi4NCgk+IHNwcmluZy1qZGJjIC0+IGNvbnRhaW5zIE9O
TFkgdGhlIFNwcmluZyBKREJDIHN0dWZmLg0KCT4gc3ByaW5nLW9ybS5qYXIgLT4gY29udGFpbnMg
T05MWSB0aGUgU3ByaW5nIE9STSBzdHVmZi4NCgk+IHNwcmluZy1jb250ZXh0LmphciAtPiBjb250
YWlucyBPTkxZIHRoZSBTcHJpbmcgY29udGV4dCBzdHVmZi4NCgk+IHNwcmluZy1tdmMuamFyIC0+
IGNvbnRhaW5zIE9OTFkgdGhlIHNwcmluZyBNVkMgc3R1ZmYuDQoJPg0KCT4gSWYgc3ByaW5nLW9y
bS5qYXIgaXMgZGVwZW5kZW50IHVwb24gc3ByaW5nLWNvbW1vbi5qYXIgdGhlbiB0aGUgdXNlciB3
aWxsIG5lZWQgdG8gZG93bmxvYWQgYW5kIGluY2x1ZGUgc3ByaW5nLWNvbW1vbi5qYXIgaW4gdGhl
IGNsYXNzcGF0aCB0b28uICBJbiB0aGlzIHdheSBwZW9wbGUgY2FuIHBpY2sgYW5kIGNob29zZSB0
aGUgZXhhY3QgcGFydHMgdGhleSB3YW50LCBidXQgeW91IGRvbid0IGhhdmUgdG8gY29tZSB1cCB3
aXRoIGEgbWlsbGlvbiBkaWZmZXJlbnQgcGFja2FnZSBjb21iaW5hdGlvbnMuLi4gIGkuZS4gbm8g
cGFja2FnZXMgdGhhdCBpbmNsdWRlIE9STSAmIEpEQkMsIGJ1dCBub3QgTVZDLiAgQW5vdGhlciBv
bmUgdGhhdCBoYXMgT1JNLCBKREJDLCBjb250ZXh0LCBidXQgbm90IE1WQy4gIEFub3RoZXIgb25l
IHRoYXQgaGFzIE9STSwgamRiYyAmIE1WQy4gIEFub3RoZXIgb25lIHRoYXQgaGFzIE9STSwgSkRC
QywgY29udGV4dCAmIE1WQy4gIFNlZSB3aGVyZSBJIGFtIGdvaW5nIHdpdGggdGhpcz8NCgk+IFBl
b3BsZSBzaG91bGQgYmUgc21hcnQgZW5vdWdoIHRvIHRha2UgdGhlIHBhcnRzIHRoZXkgd2FudCwg
YW5kIHRvIGdldCB0aGUgZGVwZW5kZW5jaWVzIHRoZXkgbmVlZC4NCgk+DQoJPiBOb3cgYXMgZmFy
IGFzIHRoZSBmaWxlIG5hbWUgZ29lcywgd2h5IG5vdCBqdXN0IHVzZSBhIG5hbWUgV0lUSE9VVCB0
aGUgdmVyc2lvbiBuYW1lIGluIGl0LCBhbmQgdGhlbiBpbmNsdWRlIGEgZmlsZSAob3IgZGlyZWN0
b3J5KSBpbiB0aGUgcm9vdCBvZiB0aGUgamFyIGNhbGxlZCBWRVJTSU9OLTEuMC4xIG9yIHNvbWUg
c3VjaCB0aGluZy4gIFRoYXQgd2F5IHBlb3BsZSB3aWxsIG5vdCBuZWVkIHRvIHdvcnJ5IGFib3V0
IGNoYW5naW5nIGJ1aWxkIHNjcmlwdHMgdG8gdXNlIGEgbmV3ZXIgdmVyc2lvbiBvZiB0aGUgamFy
IHRoYXQgaXMgQVBJIGNvbXBhdGlibGUsIGFuZCB0aGV5IGNhbiBzdGlsbCBlYXNpbGl5IGRldGVy
bWluZSB3aGF0IHZlcnNpb24gdGhleSBhcmUgdXNpbmcgYnkgbG9va2luZyBpbiB0aGUgamFyIGl0
c2VsZi4gIHRoZSBvbmx5IHRpbWUgdGhlIGphciBmaWxlIG5hbWUgc2hvdWxkIGNoYW5nZSBpcyBp
ZiB0aGUgQVBJIGhhcyBMQVJHRSBjaGFuZ2VzIHRoYXQgcmVuZGVycyB0aGUgbmV3IGphciBjb21w
bGV0ZWx5IGluY29tcGF0aWJsZSB3aXRoIHRoZSBvbGQgQVBJLiAgTWlub3IgY2hhbmdlcyB0byB0
aGUgQVBJIHNob3VsZCBwcm9iYWJseSBub3QgaGF2ZSB0aGUgamFyIGZpbGUgbmFtZXMgY2hhbmdl
ZC4NCgk+DQoJPiBKdXN0IHNvbWUgaWRlYXMgYW5kIG15IDIgY2VudHMuDQoJPg0KCT4gTGF0ZXIN
Cgk+IFJvYg0KCT4NCgk+ID4gRnJvbTogasO8cmdlbiBow7ZsbGVyIFt3ZXJrM0FUXSA8anVlcmdl
bi5ob2VsbGVyQHdlcmszYXQuY29tPg0KCT4gPiBEYXRlOiAyMDAzLzA4LzI4IFRodSBQTSAxMjow
Nzo0MiBFRFQNCgk+ID4gVG86ICJMYXJzIEZpc2NoZXIiIDxsYXJzLmZpc2NoZXJAZ214cHJvLm5l
dD4NCgk+ID4gQ0M6IDxzcHJpbmdmcmFtZXdvcmstZGV2ZWxvcGVyQGxpc3RzLnNvdXJjZWZvcmdl
Lm5ldD4sDQoJPiA+ICAgICA8dHJpc2JlcmdAdHJpZGIuY29tPiwNCgk+ID4gICAgIDxyb2Quam9o
bnNvbkBpbnRlcmZhY2UyMS5jb20+DQoJPiA+IFN1YmplY3Q6IFJFOiBbU3ByaW5nZnJhbWV3b3Jr
LWRldmVsb3Blcl0gRXhhbXBsZSBjbGFzc2VzIG5lZWRlZA0KCT4gPg0KCT4gPiBMYXJzLA0KCT4g
Pg0KCT4gPiBUaGUgcHJvYmxlbSBpcyB0aGF0IHdlIGhhdmUgbXVsdGlwbGUgamFyIGZpbGVzOg0K
CT4gPiAtIHNwcmluZy1iZWFucy5qYXINCgk+ID4gLSBzcHJpbmctYW9wLmphcg0KCT4gPiAtIHNw
cmluZy1qZGJjLmphcg0KCT4gPiAtIHNwcmluZy1vcm0uamFyDQoJPiA+IC0gc3ByaW5nLWNvbnRl
eHQuamFyDQoJPiA+IC0gc3ByaW5nLWZ1bGwuamFyDQoJPiA+DQoJPiA+ICJmdWxsIiBpbmRpY2F0
ZXMgdGhhdCBpdCBpbmNsdWRlcyBhbGwgb2YgU3ByaW5nLiBXZSBjb3VsZCBuYW1lIGl0ICJzcHJp
bmcuamFyIiBvZiBjb3Vyc2UsIEknbSBxdWl0ZSBpbmNsaW5lZCB0b3dhcmRzIHRoaXMgaWYgb3Ro
ZXJzIGFncmVlLiBXaGF0IGRvZXMgZXZlcnlib2R5IHRoaW5rPw0KCT4gPg0KCT4gPiBSZWdhcmRp
bmcgQ29saW4ncyBhcmd1bWVudCBvbiBpbi1iZXR3ZWVuIG51bWJlcmluZzogSSB3b3VsZG4ndCBt
aW5kIGRyb3BwaW5nIHRoZSB2ZXJzaW9uIG51bWJlciBhbHRvZ2V0aGVyLCBpbiBIaWJlcm5hdGUv
QW50L1NlcnZsZXQgc3R5bGUuIEknbSBqdXN0IG5vdCBhIGZhbiBvZiB2ZXJ5IHNwZWNpZmljIGZp
bGUgbmFtZXMuDQoJPiA+DQoJPiA+IFNvIDIgcXVlc3Rpb25zOg0KCT4gPiAxLiBhKSAic3ByaW5n
LWZ1bGwuamFyIiBvciBiKSAic3ByaW5nLmphciIgZm9yIHRoZSBjb21wbGV0ZSBqYXIgZmlsZQ0K
CT4gPiAyLiBhKSAic3ByaW5nLWJlYW5zLTEuMG0xLmphciIsIGIpICJzcHJpbmctYmVhbnMtMS4w
LmphciIgb3IgYykgInNwcmluZy1iZWFucy5qYXIiDQoJPiA+DQoJPiA+IEluIHRoZSBtZWFudGlt
ZSwgSSB0ZW5kIHRvIHZvdGUgMWIgYW5kIDJjLiBJIHdvdWxkbid0IG1pbmQgMWEgb3IgMmIgZWl0
aGVyLCB0aG91Z2guDQoJPiA+DQoJPiA+IEp1ZXJnZW4NCgk+ID4NCgk+ID4NCgk+ID4gLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCgk+ID4gRnJvbTogTGFycyBGaXNjaGVyIFttYWlsdG86bGFy
cy5maXNjaGVyQGdteHByby5uZXRdDQoJPiA+IFNlbnQ6IFRodXJzZGF5LCBBdWd1c3QgMjgsIDIw
MDMgNTo1NiBQTQ0KCT4gPiBUbzogasO8cmdlbiBow7ZsbGVyIFt3ZXJrM0FUXQ0KCT4gPiBDYzog
c3ByaW5nZnJhbWV3b3JrLWRldmVsb3BlckBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQ7IHRyaXNiZXJn
QHRyaWRiLmNvbTsNCgk+ID4gcm9kLmpvaG5zb25AaW50ZXJmYWNlMjEuY29tDQoJPiA+IFN1Ympl
Y3Q6IFJFOiBbU3ByaW5nZnJhbWV3b3JrLWRldmVsb3Blcl0gRXhhbXBsZSBjbGFzc2VzIG5lZWRl
ZA0KCT4gPg0KCT4gPg0KCT4gPiBXaGF0IGFib3V0IHNwcmluZy5qYXIsIHNwcmluZzIuamFyID8g
SSBkb24ndCBsaWtlIHRoaXMgIi1mdWxsIi4NCgk+ID4NCgk+ID4NCgk+ID4gPiBIbW1tLCBub3Qg
bXVjaCByZXNwb25zZSB5ZXQuLi4gSSBzdGlsbCB0ZW5kIHRvIHByZWZlciAic3ANCgk+ID4gPiBy
aW5nLWZ1bGwtMS4wLmphciIsIGZvciBlYXN5IGRyb3AtaW4uIElNTywgYSBqYXIgZmlsZSBkb2UN
Cgk+ID4gPiBzIG5vdCBuZWVkIHRvIHJlZmxlY3QgdGhlIGV4YWN0IGRldGFpbCB2ZXJzaW9uLiBJ
IGNvbnNpZGUNCgk+ID4gPiByIGl0IGZpbmUgZW5vdWdoIGlmIGl0IGluZGljYXRlcyB0aGUgbWFq
b3IgdmVyc2lvbi4gU2VlIHMNCgk+ID4gPiBlcnZsZXQuamFyLCBoaWJlcm5hdGUyLmphci4gQ2Fu
IHdlIHBsZWFzZSBkZWNpZGUgb24gdGhpcw0KCT4gPiA+IHVudGlsICp0b21vcnJvdyo/IDotKQ0K
CT4gPiA+IA0KCT4gPiA+IEp1ZXJnZW4NCgk+ID4gPiANCgk+ID4gPiANCgk+ID4gPg0KCT4gPiA+
IC0tLS0tT3JpZ2luYWwNCgk+ID4gPiBNZXNzYWdlLS0tLS0NCgk+ID4gPiBGcm9tOiBqw4PCvHJn
ZW4gaMODwrZsbGVyIFt3ZXJrM0FUXQ0KCT4gPiA+IFNlbnQ6IE1vbg0KCT4gPiA+IGRheSwgQXVn
dXN0IDI1LCAyMDAzIDExOjUwIFBNDQoJPiA+ID4gVG86IExhcnMgRmlzY2hlcjsgc3ByaW5nZnIN
Cgk+ID4gPiBhbWV3b3JrLWRldmVsb3BlckBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCgk+ID4gPiBD
YzogdHJpc2JlcmdAdHJpDQoJPiA+ID4gZGIuY29tDQoJPiA+ID4gU3ViamVjdDogUmU6IFtTcHJp
bmdmcmFtZXdvcmstZGV2ZWxvcGVyXSBFeGFtcGxlDQoJPiA+ID4gY2xhc3NlcyBuZWVkZWQNCgk+
ID4gPg0KCT4gPiA+DQoJPiA+ID4gTGV0J3Mgdm90ZSBvbiB0aGlzLiBJIGRvbid0IG1pbmQgZWl0
aA0KCT4gPiA+IGVyIG5hbWluZyBzdHJhdGVneSBmb3IgamFyIGZpbGVzLiBBbnlib2R5IGVsc2Ug
cHJlZmVyaW5nDQoJPiA+ID4gdGhlIHNwcmluZy1mdWxsLTEuMG0xIHN0eWxlPw0KCT4gPiA+IA0K
CT4gPiA+IEJUVywgSGliZXJuYXRlIHVzZXMgaGliZQ0KCT4gPiA+IHJuYXRlMi5qYXIgZm9yIGl0
cyB3aG9sZSAyLnggdHJlZS4gTG9nNEogdXNlcyBsb2c0ai0xLjIuOA0KCT4gPiA+IC5qYXIgZm9y
IHRoZSBzcGVjaWZpYyB2ZXJzaW9uLiAyIGV4YW1wbGVzIGZvciBvcHBvc2l0ZSBlbg0KCT4gPiA+
IGRzLCBJIGd1ZXNzLg0KCT4gPiA+IA0KCT4gPiA+IEp1ZXJnZW4NCgk+ID4gPiANCgk+ID4gPiAN
Cgk+ID4gPg0KCT4gPiA+IC0tLS0tVXJzcHLDg8K8bmdsaWNoZSBOYWMNCgk+ID4gPiBocmljaHQt
LS0tLQ0KCT4gPiA+IFZvbjogTGFycyBGaXNjaGVyIFttYWlsdG86bGFycy5maXNjaGVyQGdteHAN
Cgk+ID4gPiByby5uZXRdDQoJPiA+ID4gR2VzZW5kZXQ6IE1vIDI1LjA4LjIwMDMgMjM6MTgNCgk+
ID4gPiBBbjogc3ByaW5nZnJhbWUNCgk+ID4gPiB3b3JrLWRldmVsb3BlckBsaXN0cy5zb3VyY2Vm
b3JnZS5uZXQNCgk+ID4gPiBDYzogasODwrxyZ2VuIGjDg8K2bGxlDQoJPiA+ID4gciBbd2VyazNB
VF07IHRyaXNiZXJnQHRyaWRiLmNvbQ0KCT4gPiA+IEJldHJlZmY6IFJlOiBbU3ByaW5nZnJhDQoJ
PiA+ID4gbWV3b3JrLWRldmVsb3Blcl0gRXhhbXBsZSBjbGFzc2VzIG5lZWRlZA0KCT4gPiA+DQoJ
PiA+ID4NCgk+ID4gPg0KCT4gPiA+IEkgYWdyZWUgdw0KCT4gPiA+IGl0aCBUaG9tYXMsIEkgb25j
ZSBtYWRlIGEgbWlzdGFrZSBiZWNhdXNlIEkgZGlkbid0IHJlYWxpeg0KCT4gPiA+IGUNCgk+ID4g
PiB0aGF0IEkgd2FzIHVzaW5nIGFuIG9sZGVyIHZlcnNpb24uIFRoZSBqYXItZmlsZXMgc2hvdWwN
Cgk+ID4gPiBkIGJlIG5hbWVkIGFmdGVyDQoJPiA+ID4gdGhlIHZlcnNpb24uDQoJPiA+ID4NCgk+
ID4gPiA+IEp1ZXJnZW4sDQoJPiA+ID4gPg0KCT4gPiA+ID4gVGhlIGRyDQoJPiA+ID4gYXdiYWNr
IHRoZW4gaXMgdGhhdCB5b3UgY2FuJ3QgdGVsbCBmcm9tIHRoZSBqYXIgZmlsZSBpZiBpDQoJPiA+
ID4gdCBpcyBNMSwgTTINCgk+ID4gPiA+IG9yDQoJPiA+ID4gPiB0aGUgcmVsZWFzZSBqYXIuDQoJ
PiA+ID4gPg0KCT4gPiA+ID4gVGhvbWFzDQoJPiA+ID4gPg0KCT4gPiA+ID4NCgk+ID4gPiA+IEl0
J3MgZ29ubmEgYmUgInNwcmluZy1mcmFtZXdvcmstMS4wbTEiIGFuZCAic3ByaW5nLWZ1bGwNCgk+
ID4gPiAtMS4wLmphciIsIGlmIHdlDQoJPiA+ID4gPiBzdGljaw0KCT4gPiA+ID4gPiB0byB0aGUg
Y3VycmVudCBwbGFuLiBXZSd2ZQ0KCT4gPiA+ICB1c2VkIHRoZSBzYW1lIG5hbWluZyBzdHJhdGVn
eSBmb3IgMC45LngsIGUuZy4NCgk+ID4gPiA+ID4gInNwcmkNCgk+ID4gPiBuZy1mcmFtZXdvcmst
MC45LjEiIGJ1dCBzdGlsbCAic3ByaW5nLWZ1bGwtMC45LmphciIuIEkgcHINCgk+ID4gPiBlZmVy
IHRoYXQNCgk+ID4gPiA+IHdheQ0KCT4gPiA+ID4gPiB0byBlYXNlIGRyb3AtaW4gcmVwbGFjZW1l
bnQgaW4gdGhlDQoJPiA+ID4gbGl0ZXJhbCBzZW5zZSA6LSkgVGhlIGJ1aWxkDQoJPiA+ID4gPiBw
cm9wZXJ0aWVzDQoJPiA+ID4gPiA+IHJlZmxlY3QgdGgNCgk+ID4gPiBpcyBpbiAic3ByaW5nLXZl
cnNpb249MS4wIiBhbmQgInNwcmluZy12ZXJzaW9uLWRldGFpbD0xLjANCgk+ID4gPiBtMSIuDQoJ
PiA+ID4gPiA+DQoJPiA+ID4gPiA+IEp1ZXJnZW4NCgk+ID4gPiA+ID4NCgk+ID4gPiA+ID4NCgk+
ID4gPiA+ID4NCgk+ID4gPiA+ID4gICAgIC0tLS0tVXINCgk+ID4gPiBzcHLDg2bDgsK8bmdsaWNo
ZSBOYWNocmljaHQtLS0tLQ0KCT4gPiA+ID4gPiAgICAgVm9uOiB0cmlzYmVyZ0B0cmlkDQoJPiA+
ID4gYi5jb20gWyBtYWlsdG86dHJpc2JlcmdAdHJpZGIuY29tXQ0KCT4gPiA+ID4gPiAgICAgR2Vz
ZW5kZXQ6IE1vDQoJPiA+ID4gMjUuMDguMjAwMyAxOToyMQ0KCT4gPiA+ID4gPiAgICAgQW46IGrD
g2bDgsK8cmdlbiBow4Nmw4LCtmxsZXIgW3dlcmszQQ0KCT4gPiA+IFRdDQoJPiA+ID4gPiA+ICAg
ICBDYzogTGFycyBGaXNjaGVyOyBzcHJpbmdmcmFtZXdvcmstZGV2ZWxvcGVyQGwNCgk+ID4gPiBp
c3RzLnNvdXJjZWZvcmdlLm5ldA0KCT4gPiA+ID4gPiAgICAgQmV0cmVmZjogUkU6IFtTcHJpbmdm
cmFtZXdvDQoJPiA+ID4gcmstZGV2ZWxvcGVyXSBFeGFtcGxlIGNsYXNzZXMgbmVlZGVkDQoJPiA+
ID4gPiA+ICAgDQoJPiA+ID4gPiA+ICAgDQoJPiA+ID4gPg0KCT4gPiA+ICA+DQoJPiA+ID4gPiA+
ICAgICBKdWVyZ2VuLA0KCT4gPiA+ID4gPiAgIA0KCT4gPiA+ID4gPiAgICAgPiBBbnl3YXksIENv
bnRleHRMDQoJPiA+ID4gb2FkZXJTZXJ2bGV0ICp3aWxsKiBiZSBpbiAxLjAgTTEsIHRvIGJlIHJl
bGVhc2VkIGF0DQoJPiA+ID4gPiB0aA0KCT4gPiA+IGUNCgk+ID4gPiA+ID4gZW5kDQoJPiA+ID4g
PiA+ICAgICA+IG9mIHRoaXMgd2VlayBpZiB0aGVyZSBhcmVuJ3QgYW55IG1hDQoJPiA+ID4gam9y
IG9ic3RhY2xlcy4gQlRXLCBjYW4gZXZlcnlib2R5DQoJPiA+ID4gPiA+IHBsZWFzZQ0KCT4gPiA+
ID4gPiAgICAgPg0KCT4gPiA+IHRlc3QgdGhlIGN1cnJlbnQgQ1ZTIGNvbnRlbnRzIGFnYWluc3Qg
b3duIGFwcGxpY2F0aW9ucz8NCgk+ID4gPiA+ID4gICAgID4NCgk+ID4gPiA+ID4gICANCgk+ID4g
PiA+ID4gICAgIEkgYW0gdXBkYXRpbmcgdGhlIFN0ZXAtYnktc3RlDQoJPiA+ID4gcC1NVkMgZG9j
dW1lbnQgLSB3aGF0IHdpbGwgdGhlIGV4YWN0IG5hbWUNCgk+ID4gPiA+IG9mDQoJPiA+ID4gPiA+
IHRoZQ0KCT4gPiA+DQoJPiA+ID4gPiA+ICAgICBkaXJlY3RvcnkgYW5kIHRoZSBqYXIgZmlsZSBi
ZT8gIEknbSBhc3N1bWluZyAnc3ANCgk+ID4gPiByaW5nLWZyYW1ld29yay0xLjBNMScNCgk+ID4g
PiA+IGFuZA0KCT4gPiA+ID4gPiAgICAgJ3NwcmluZy1mdWxsLTEuME0xLg0KCT4gPiA+IGphcicu
DQoJPiA+ID4gPiA+ICAgDQoJPiA+ID4gPiA+ICAgICBUaG9tYXMNCgk+ID4gPiA+ID4gICANCgk+
ID4gPiA+ID4NCgk+ID4gPiA+ID4NCgk+ID4gPiA+DQoJPiA+ID4gPg0KCT4gPiA+ID4NCgk+ID4g
Pg0KCT4gPiA+DQoJPiA+ID4NCgk+ID4NCgk+ID4NCgk+ID4NCgk+ID4gLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KCT4gPiBUaGlzIHNmLm5l
dCBlbWFpbCBpcyBzcG9uc29yZWQgYnk6VGhpbmtHZWVrDQoJPiA+IFdlbGNvbWUgdG8gZ2VlayBo
ZWF2ZW4uDQoJPiA+IGh0dHA6Ly90aGlua2dlZWsuY29tL3NmDQoJPiA+IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoJPiA+IFNwcmluZ2ZyYW1ld29yay1k
ZXZlbG9wZXIgbWFpbGluZyBsaXN0DQoJPiA+IFNwcmluZ2ZyYW1ld29yay1kZXZlbG9wZXJAbGlz
dHMuc291cmNlZm9yZ2UubmV0DQoJPiA+IGh0dHBzOi8vbGlzdHMuc291cmNlZm9yZ2UubmV0L2xp
c3RzL2xpc3RpbmZvL3NwcmluZ2ZyYW1ld29yay1kZXZlbG9wZXINCgk+ID4NCgk+DQoJPg0KCQ0K
CQ0KDQo=

Re: [Springframework-developer] Thanks to all the Spring developers

[Rob B. <rob...@ve...>]

Rod,

First and foremost more, better, free(hopefully) documentation, preferably as a PDF so it can be printed.  Your book is excellent, and well worth the price and I haven't even finished it.  (I've been swamped with stuff so I am only at the beginning of chapter 7, so I haven't even gotten to the juicy stuff.)  But, having to read a 680 page book in order to use a framework sucks.

Even worse is that the framework has evolved since the time the book was printed (it doesn't cover hibernate, etc).  As time goes on I am sure the book, and the development of the framework will diverge even more.  A PDF available on the website could be kept up to date as the project evolves and always be a valuable resource for newbies to the framework, or a good reference for those who have been using it for a while.

I would definetly recommend creating the doc in PDF format because it is much easier to read / digest offline, and can act as a good resource when internet access is not available.  HTML never prints nicely, even pages that are "printer friendly".  The PDF docs available from the Hibernate project are excellent examples of quality free documentation for a project.

I think a quality set of documentation with some good examples would go along way in making the use / understanding of Spring much easier.  It would also help the frameworks user base grow.  Again, your book is worth every cent, and I highly recommend everyone get it, but not everyone is willing to (or can) shell out $60 for a book on every framework and technology they are trying out or considering for use.

A second reason to provide quality docs is it reflects well on the project.  I investigated Hibernate and Object Bridge.  Eventually I decided that Hibernate was the way to go (for many many reasons).  But what immediately impressed me with the Hibernate project was the quality of its documentation.  I immediately felt that the project was going to be high in quality because the time, effort and quality of the (free) documentation was very high.  

Also consider that there are many other frameworks around on the net, all of them just a click away.  Sometimes you only have a few precious seconds to impress a potential user before they click onto the next project.  Other frameworks like Struts have an abundance of free documentation and tutorials as articles on a variety of websites.  Plus Struts has a variety of books available too.  These are even more reasons to create high quality documentation for spring in addition to your existing book.

Just my opinion.

Later
Rob

> 
> From: "Rod Johnson" <rod...@in...>
> Date: 2003/08/28 Thu PM 03:34:50 EDT
> To: "Lars Fischer" <lar...@gm...>, 
>         <spr...@li...>
> Subject: Re: [Springframework-developer] Thanks to all the Spring developers
> 
> Lars,
> 
> Thanks for your kind words.
> 
> Regarding the learning curve, any suggestions on what we can do to make
> Spring easier to learn are welcome. I don't think Spring is inherently
> complex, although it does do a lot. But I do appreciate that getting to
> grips with it--especially in combination with other products such as
> Hibernate--may be a challenge, and I want to try to change that.
> 
> Regards,
> Rod
> 
> ----- Original Message -----
> From: "Lars Fischer" <lar...@gm...>
> To: <spr...@li...>
> Sent: Thursday, August 28, 2003 8:12 PM
> Subject: [Springframework-developer] Thanks to all the Spring developers
> 
> 
> > This is a message to all Spring developers and potential users of Spring.
> >
> > This week I've managed to get a first prototype with Spring and Hibernate
> > (two completely new technologies for me) working.  The biggest problem
> > was to get the configuration working (and a 'little' WebLogic problem).
> >
> > Spring has a high learning curve at the beginning because it's a full
> > featured
> > framework for nearly all your needs.
> >
> > If you are willing to invest some time and get things working you will
> > understand
> > more and more what it's all about.
> >
> > Spring can help you to get rid of all these annoying problems with EJBs
> and
> > the related patterns only used to avoid performance problems. And despite
> > the
> > fact that the learning curve maybe high, you just have to learn ONE
> > framework.
> >
> > If you want to keep existing technologies Spring is fine too (just use
> > the needed parts).
> >
> > As a result of my experriences I can highly recommend the use of the
> Spring
> > framework, for me this is an outstanding peace of software with
> > outstanding developers.
> >
> > In the past year I've developed a larger application with EJBs. It's
> working
> > very well (emtremely fast, scalable and stable).  Today I'd use Spring
> which
> > is
> > much more elegant and makes you independant of the application server
> > vendor.
> >
> > If someone reading this is in the situation of deciding whether to use
> > Spring or
> > not, my recommandation is to give it a try and you won't be disappointed !
> >
> > My thanks go to all Spring developers for providing such a great framework
> !
> >
> > Regards
> > Lars
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Springframework-developer mailing list
> > Spr...@li...
> > https://lists.sourceforge.net/lists/listinfo/springframework-developer
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
> 

Re: [Springframework-developer] Thanks to all the Spring developers

[Rod J. <rod...@in...>]

Lars,

Thanks for your kind words.

Regarding the learning curve, any suggestions on what we can do to make
Spring easier to learn are welcome. I don't think Spring is inherently
complex, although it does do a lot. But I do appreciate that getting to
grips with it--especially in combination with other products such as
Hibernate--may be a challenge, and I want to try to change that.

Regards,
Rod

----- Original Message -----
From: "Lars Fischer" <lar...@gm...>
To: <spr...@li...>
Sent: Thursday, August 28, 2003 8:12 PM
Subject: [Springframework-developer] Thanks to all the Spring developers


> This is a message to all Spring developers and potential users of Spring.
>
> This week I've managed to get a first prototype with Spring and Hibernate
> (two completely new technologies for me) working.  The biggest problem
> was to get the configuration working (and a 'little' WebLogic problem).
>
> Spring has a high learning curve at the beginning because it's a full
> featured
> framework for nearly all your needs.
>
> If you are willing to invest some time and get things working you will
> understand
> more and more what it's all about.
>
> Spring can help you to get rid of all these annoying problems with EJBs
and
> the related patterns only used to avoid performance problems. And despite
> the
> fact that the learning curve maybe high, you just have to learn ONE
> framework.
>
> If you want to keep existing technologies Spring is fine too (just use
> the needed parts).
>
> As a result of my experriences I can highly recommend the use of the
Spring
> framework, for me this is an outstanding peace of software with
> outstanding developers.
>
> In the past year I've developed a larger application with EJBs. It's
working
> very well (emtremely fast, scalable and stable).  Today I'd use Spring
which
> is
> much more elegant and makes you independant of the application server
> vendor.
>
> If someone reading this is in the situation of deciding whether to use
> Spring or
> not, my recommandation is to give it a try and you won't be disappointed !
>
> My thanks go to all Spring developers for providing such a great framework
!
>
> Regards
> Lars
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

[Springframework-developer] Thanks to all the Spring developers

[Lars F. <lar...@gm...>]

This is a message to all Spring developers and potential users of Spring.

This week I've managed to get a first prototype with Spring and Hibernate
(two completely new technologies for me) working.  The biggest problem
was to get the configuration working (and a 'little' WebLogic problem).

Spring has a high learning curve at the beginning because it's a full
featured
framework for nearly all your needs. 

If you are willing to invest some time and get things working you will
understand
more and more what it's all about.

Spring can help you to get rid of all these annoying problems with EJBs and 
the related patterns only used to avoid performance problems. And despite
the
fact that the learning curve maybe high, you just have to learn ONE
framework.

If you want to keep existing technologies Spring is fine too (just use
the needed parts).

As a result of my experriences I can highly recommend the use of the Spring
framework, for me this is an outstanding peace of software with 
outstanding developers.

In the past year I've developed a larger application with EJBs. It's working
very well (emtremely fast, scalable and stable).  Today I'd use Spring which
is
much more elegant and makes you independant of the application server
vendor.

If someone reading this is in the situation of deciding whether to use
Spring or
not, my recommandation is to give it a try and you won't be disappointed !

My thanks go to all Spring developers for providing such a great framework !

Regards
Lars

RE: [Springframework-developer] Example classes needed

[Rob B. <rob...@ve...>]

What about the other idea of splitting spring up into its "component" pie=
ces so that users can pick and choose the parts they want?

Later
Rob

> =

> From: j=FCrgen h=F6ller [werk3AT] <jue...@we...>
> Date: 2003/08/28 Thu PM 01:19:26 EDT
> To: "Rob Butler" <rob...@ve...>, =

> 	"Lars Fischer" <lar...@gm...>
> CC: <spr...@li...>, =

> 	<tri...@tr...>, =

> 	<rod...@in...>
> Subject: RE: [Springframework-developer] Example classes needed
> =

> I've just added a manifest entry "Spring-Version" to our build scripts.=
 This means that a "spring.jar" for 1.0 M1 will include a "Spring-Version=
=3D1.0m1" entry in its META-INF/manifest.mf file. So if you've got jar fi=
les lying around, you can always check the exact version. With this inclu=
ded, I tend to drop version numbers even more. Thanks for the idea, Rob -=
 I just guess it's simpler to make a manifest entry than to include an ex=
tra file.
> =

> We all seem to agree we prefer "spring.jar" over "spring-full.jar", but=
 are about 50:50 regarding version numbers in the name. So let's focus on=
 the latter: Would anyone *mind* no version number in the name, given tha=
t it's mentioned in the manifest file? Everyone is free to rename the fil=
es any way he wants anyway, it's just about the shipped jars. As for me, =
I would mind the full version number "1.0m1" - in the meantime, I even pr=
efer "spring.jar".
> =

> To keep the fire burning, some examples for no version numbers that I k=
now of: Servlet, JUnit, JavaMail, Xerces, JSTL, Commons Logging, Commons =
DBCP, XAPool, Hibernate, COS, GLUE, Ant, Tomcat, JBoss, Clover. Counterex=
amples with version numbers in the jar name: JTA, CGLIB, BCEL, Log4J, Cas=
tor, Tyrex, Velocity, Tapestry, Hessian, iText, MySQL JDBC driver.
> =

> In the end, one can argue for all options. There is no obvious solution=
=2E So we should try to settle on one option and stick with it.
> =

> Juergen
> =

> =

> -----Original Message-----
> From: Rob Butler [mailto:rob...@ve...]
> Sent: Thursday, August 28, 2003 6:34 PM
> To: j=FCrgen h=F6ller [werk3AT]; Lars Fischer
> Cc: spr...@li...; tri...@tr...=
;
> rod...@in...
> Subject: RE: [Springframework-developer] Example classes needed
> =

> =

> Hello all,
> =

> Since spring is modular, why not break it down even further into chunck=
s.
> =

> spring-common.jar ->Basic stuff that is used everywhere in spring
> spring-beans.jar -> contains ONLY the Spring Beans stuff.
> spring-aop.jar -> contains ONLY the Spring AOP stuff.
> spring-jdbc -> contains ONLY the Spring JDBC stuff.
> spring-orm.jar -> contains ONLY the Spring ORM stuff.
> spring-context.jar -> contains ONLY the Spring context stuff.
> spring-mvc.jar -> contains ONLY the spring MVC stuff.
> =

> If spring-orm.jar is dependent upon spring-common.jar then the user wil=
l need to download and include spring-common.jar in the classpath too.  I=
n this way people can pick and choose the exact parts they want, but you =
don't have to come up with a million different package combinations...  i=
=2Ee. no packages that include ORM & JDBC, but not MVC.  Another one that=
 has ORM, JDBC, context, but not MVC.  Another one that has ORM, jdbc & M=
VC.  Another one that has ORM, JDBC, context & MVC.  See where I am going=
 with this?
> People should be smart enough to take the parts they want, and to get t=
he dependencies they need.
> =

> Now as far as the file name goes, why not just use a name WITHOUT the v=
ersion name in it, and then include a file (or directory) in the root of =
the jar called VERSION-1.0.1 or some such thing.  That way people will no=
t need to worry about changing build scripts to use a newer version of th=
e jar that is API compatible, and they can still easiliy determine what v=
ersion they are using by looking in the jar itself.  the only time the ja=
r file name should change is if the API has LARGE changes that renders th=
e new jar completely incompatible with the old API.  Minor changes to the=
 API should probably not have the jar file names changed.
> =

> Just some ideas and my 2 cents.
> =

> Later
> Rob
> =

> > From: j=FCrgen h=F6ller [werk3AT] <jue...@we...>
> > Date: 2003/08/28 Thu PM 12:07:42 EDT
> > To: "Lars Fischer" <lar...@gm...>
> > CC: <spr...@li...>, =

> > 	<tri...@tr...>, =

> > 	<rod...@in...>
> > Subject: RE: [Springframework-developer] Example classes needed
> > =

> > Lars,
> > =

> > The problem is that we have multiple jar files:
> > - spring-beans.jar
> > - spring-aop.jar
> > - spring-jdbc.jar
> > - spring-orm.jar
> > - spring-context.jar
> > - spring-full.jar
> > =

> > "full" indicates that it includes all of Spring. We could name it "sp=
ring.jar" of course, I'm quite inclined towards this if others agree. Wha=
t does everybody think?
> > =

> > Regarding Colin's argument on in-between numbering: I wouldn't mind d=
ropping the version number altogether, in Hibernate/Ant/Servlet style. I'=
m just not a fan of very specific file names.
> > =

> > So 2 questions:
> > 1. a) "spring-full.jar" or b) "spring.jar" for the complete jar file
> > 2. a) "spring-beans-1.0m1.jar", b) "spring-beans-1.0.jar" or c) "spri=
ng-beans.jar"
> > =

> > In the meantime, I tend to vote 1b and 2c. I wouldn't mind 1a or 2b e=
ither, though.
> > =

> > Juergen
> > =

> > =

> > -----Original Message-----
> > From: Lars Fischer [mailto:lar...@gm...]
> > Sent: Thursday, August 28, 2003 5:56 PM
> > To: j=FCrgen h=F6ller [werk3AT]
> > Cc: spr...@li...; trisberg@tridb.c=
om;
> > rod...@in...
> > Subject: RE: [Springframework-developer] Example classes needed
> > =

> > =

> > What about spring.jar, spring2.jar ? I don't like this "-full".
> > =

> > =

> > > Hmmm, not much response yet... I still tend to prefer "sp
> > > ring-full-1.0.jar", for easy drop-in. IMO, a jar file doe
> > > s not need to reflect the exact detail version. I conside
> > > r it fine enough if it indicates the major version. See s
> > > ervlet.jar, hibernate2.jar. Can we please decide on this =

> > > until *tomorrow*? :-)
> > >  =

> > > Juergen
> > >  =

> > >  =

> > > =

> > > -----Original =

> > > Message-----
> > > From: j=C3=BCrgen h=C3=B6ller [werk3AT] =

> > > Sent: Mon
> > > day, August 25, 2003 11:50 PM
> > > To: Lars Fischer; springfr
> > > ame...@li...
> > > Cc: trisberg@tri
> > > db.com
> > > Subject: Re: [Springframework-developer] Example =

> > > classes needed
> > > =

> > > =

> > > Let's vote on this. I don't mind eith
> > > er naming strategy for jar files. Anybody else prefering =

> > > the spring-full-1.0m1 style?
> > >  =

> > > BTW, Hibernate uses hibe
> > > rnate2.jar for its whole 2.x tree. Log4J uses log4j-1.2.8
> > > .jar for the specific version. 2 examples for opposite en
> > > ds, I guess.
> > >  =

> > > Juergen
> > >  =

> > >  =

> > > =

> > > -----Urspr=C3=BCngliche Nac
> > > hricht----- =

> > > Von: Lars Fischer [mailto:lars.fischer@gmxp
> > > ro.net] =

> > > Gesendet: Mo 25.08.2003 23:18 =

> > > An: springframe
> > > wor...@li... =

> > > Cc: j=C3=BCrgen h=C3=B6lle
> > > r [werk3AT]; tri...@tr... =

> > > Betreff: Re: [Springfra
> > > mework-developer] Example classes needed
> > > =

> > > =

> > > =

> > > I agree w
> > > ith Thomas, I once made a mistake because I didn't realiz
> > > e
> > > that I was using an older version. The jar-files shoul
> > > d be named after
> > > the version.
> > > =

> > > > Juergen,
> > > >
> > > > The dr
> > > awback then is that you can't tell from the jar file if i
> > > t is M1, M2
> > > > or
> > > > the release jar.
> > > >
> > > > Thomas
> > > >
> > > > =

> > > > It's gonna be "spring-framework-1.0m1" and "spring-full
> > > -1.0.jar", if we
> > > > stick
> > > > > to the current plan. We've
> > >  used the same naming strategy for 0.9.x, e.g.
> > > > > "spri
> > > ng-framework-0.9.1" but still "spring-full-0.9.jar". I pr
> > > efer that
> > > > way
> > > > > to ease drop-in replacement in the =

> > > literal sense :-) The build
> > > > properties
> > > > > reflect th
> > > is in "spring-version=3D1.0" and "spring-version-detail=3D1.0
> > > m1".
> > > > > =

> > > > > Juergen
> > > > > =

> > > > > =

> > > > >
> > > > >     -----Ur
> > > spr=C3f=C2=BCngliche Nachricht-----
> > > > >     Von: trisberg@trid
> > > b.com [ mailto:tri...@tr...]
> > > > >     Gesendet: Mo =

> > > 25.08.2003 19:21
> > > > >     An: j=C3f=C2=BCrgen h=C3f=C2=B6ller [werk3A
> > > T]
> > > > >     Cc: Lars Fischer; springframework-developer@l
> > > ists.sourceforge.net
> > > > >     Betreff: RE: [Springframewo
> > > rk-developer] Example classes needed
> > > > >    =

> > > > >    =

> > > >
> > >  >
> > > > >     Juergen,
> > > > >    =

> > > > >     > Anyway, ContextL
> > > oaderServlet *will* be in 1.0 M1, to be released at
> > > > th
> > > e
> > > > > end
> > > > >     > of this week if there aren't any ma
> > > jor obstacles. BTW, can everybody
> > > > > please
> > > > >     > =

> > > test the current CVS contents against own applications?
> > > > >     >
> > > > >    =

> > > > >     I am updating the Step-by-ste
> > > p-MVC document - what will the exact name
> > > > of
> > > > > the
> > > =

> > > > >     directory and the jar file be?  I'm assuming 'sp
> > > ring-framework-1.0M1'
> > > > and
> > > > >     'spring-full-1.0M1.
> > > jar'.
> > > > >    =

> > > > >     Thomas
> > > > >    =

> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > =

> > > =

> > > =

> > =

> > =

> > =

> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Springframework-developer mailing list
> > Spr...@li...
> > https://lists.sourceforge.net/lists/listinfo/springframework-develope=
r
> > =

> =

> =

RE: [Springframework-developer] Example classes needed

[<tri...@tr...>]

Juergen,

I like the manifest entry and I also like jars without version numbers.

Thomas

> I've just added a manifest entry "Spring-Version" to our build scripts. This
> means that a "spring.jar" for 1.0 M1 will include a "Spring-Version=1.0m1"
> entry in its META-INF/manifest.mf file. So if you've got jar files lying
> around, you can always check the exact version. With this included, I tend to
> drop version numbers even more. Thanks for the idea, Rob - I just guess it's
> simpler to make a manifest entry than to include an extra file.
> 
> We all seem to agree we prefer "spring.jar" over "spring-full.jar", but are
> about 50:50 regarding version numbers in the name. So let's focus on the
> latter: Would anyone *mind* no version number in the name, given that it's
> mentioned in the manifest file? Everyone is free to rename the files any way
> he wants anyway, it's just about the shipped jars. As for me, I would mind
> the full version number "1.0m1" - in the meantime, I even prefer
> "spring.jar".
> 
> To keep the fire burning, some examples for no version numbers that I know
> of: Servlet, JUnit, JavaMail, Xerces, JSTL, Commons Logging, Commons DBCP,
> XAPool, Hibernate, COS, GLUE, Ant, Tomcat, JBoss, Clover. Counterexamples
> with version numbers in the jar name: JTA, CGLIB, BCEL, Log4J, Castor, Tyrex,
> Velocity, Tapestry, Hessian, iText, MySQL JDBC driver.
> 
> In the end, one can argue for all options. There is no obvious solution. So
> we should try to settle on one option and stick with it.
> 
> Juergen
> 
> 
> -----Original Message-----
> From: Rob Butler [mailto:rob...@ve...]
> Sent: Thursday, August 28, 2003 6:34 PM
> To: jürgen höller [werk3AT]; Lars Fischer
> Cc: spr...@li...; tri...@tr...;
> rod...@in...
> Subject: RE: [Springframework-developer] Example classes needed
> 
> 
> Hello all,
> 
> Since spring is modular, why not break it down even further into chuncks.
> 
> spring-common.jar ->Basic stuff that is used everywhere in spring
> spring-beans.jar -> contains ONLY the Spring Beans stuff.
> spring-aop.jar -> contains ONLY the Spring AOP stuff.
> spring-jdbc -> contains ONLY the Spring JDBC stuff.
> spring-orm.jar -> contains ONLY the Spring ORM stuff.
> spring-context.jar -> contains ONLY the Spring context stuff.
> spring-mvc.jar -> contains ONLY the spring MVC stuff.
> 
> If spring-orm.jar is dependent upon spring-common.jar then the user will need
> to download and include spring-common.jar in the classpath too.  In this way
> people can pick and choose the exact parts they want, but you don't have to
> come up with a million different package combinations...  i.e. no packages
> that include ORM & JDBC, but not MVC.  Another one that has ORM, JDBC,
> context, but not MVC.  Another one that has ORM, jdbc & MVC.  Another one
> that has ORM, JDBC, context & MVC.  See where I am going with this?
> People should be smart enough to take the parts they want, and to get the
> dependencies they need.
> 
> Now as far as the file name goes, why not just use a name WITHOUT the version
> name in it, and then include a file (or directory) in the root of the jar
> called VERSION-1.0.1 or some such thing.  That way people will not need to
> worry about changing build scripts to use a newer version of the jar that is
> API compatible, and they can still easiliy determine what version they are
> using by looking in the jar itself.  the only time the jar file name should
> change is if the API has LARGE changes that renders the new jar completely
> incompatible with the old API.  Minor changes to the API should probably not
> have the jar file names changed.
> 
> Just some ideas and my 2 cents.
> 
> Later
> Rob
> 
> > From: jürgen höller [werk3AT] <jue...@we...>
> > Date: 2003/08/28 Thu PM 12:07:42 EDT
> > To: "Lars Fischer" <lar...@gm...>
> > CC: <spr...@li...>, 
> > 	<tri...@tr...>, 
> > 	<rod...@in...>
> > Subject: RE: [Springframework-developer] Example classes needed
> > 
> > Lars,
> > 
> > The problem is that we have multiple jar files:
> > - spring-beans.jar
> > - spring-aop.jar
> > - spring-jdbc.jar
> > - spring-orm.jar
> > - spring-context.jar
> > - spring-full.jar
> > 
> > "full" indicates that it includes all of Spring. We could name it
> "spring.jar" of course, I'm quite inclined towards this if others agree. What
> does everybody think?
> > 
> > Regarding Colin's argument on in-between numbering: I wouldn't mind
> dropping the version number altogether, in Hibernate/Ant/Servlet style. I'm
> just not a fan of very specific file names.
> > 
> > So 2 questions:
> > 1. a) "spring-full.jar" or b) "spring.jar" for the complete jar file
> > 2. a) "spring-beans-1.0m1.jar", b) "spring-beans-1.0.jar" or c)
> "spring-beans.jar"
> > 
> > In the meantime, I tend to vote 1b and 2c. I wouldn't mind 1a or 2b either,
> though.
> > 
> > Juergen
> > 
> > 
> > -----Original Message-----
> > From: Lars Fischer [mailto:lar...@gm...]
> > Sent: Thursday, August 28, 2003 5:56 PM
> > To: jürgen höller [werk3AT]
> > Cc: spr...@li...; tri...@tr...;
> > rod...@in...
> > Subject: RE: [Springframework-developer] Example classes needed
> > 
> > 
> > What about spring.jar, spring2.jar ? I don't like this "-full".
> > 
> > 
> > > Hmmm, not much response yet... I still tend to prefer "sp
> > > ring-full-1.0.jar", for easy drop-in. IMO, a jar file doe
> > > s not need to reflect the exact detail version. I conside
> > > r it fine enough if it indicates the major version. See s
> > > ervlet.jar, hibernate2.jar. Can we please decide on this 
> > > until *tomorrow*? :-)
> > >  
> > > Juergen
> > >  
> > >  
> > > 
> > > -----Original 
> > > Message-----
> > > From: jürgen höller [werk3AT] 
> > > Sent: Mon
> > > day, August 25, 2003 11:50 PM
> > > To: Lars Fischer; springfr
> > > ame...@li...
> > > Cc: trisberg@tri
> > > db.com
> > > Subject: Re: [Springframework-developer] Example 
> > > classes needed
> > > 
> > > 
> > > Let's vote on this. I don't mind eith
> > > er naming strategy for jar files. Anybody else prefering 
> > > the spring-full-1.0m1 style?
> > >  
> > > BTW, Hibernate uses hibe
> > > rnate2.jar for its whole 2.x tree. Log4J uses log4j-1.2.8
> > > .jar for the specific version. 2 examples for opposite en
> > > ds, I guess.
> > >  
> > > Juergen
> > >  
> > >  
> > > 
> > > -----Ursprüngliche Nac
> > > hricht----- 
> > > Von: Lars Fischer [mailto:lars.fischer@gmxp
> > > ro.net] 
> > > Gesendet: Mo 25.08.2003 23:18 
> > > An: springframe
> > > wor...@li... 
> > > Cc: jürgen hölle
> > > r [werk3AT]; tri...@tr... 
> > > Betreff: Re: [Springfra
> > > mework-developer] Example classes needed
> > > 
> > > 
> > > 
> > > I agree w
> > > ith Thomas, I once made a mistake because I didn't realiz
> > > e
> > > that I was using an older version. The jar-files shoul
> > > d be named after
> > > the version.
> > > 
> > > > Juergen,
> > > >
> > > > The dr
> > > awback then is that you can't tell from the jar file if i
> > > t is M1, M2
> > > > or
> > > > the release jar.
> > > >
> > > > Thomas
> > > >
> > > > 
> > > > It's gonna be "spring-framework-1.0m1" and "spring-full
> > > -1.0.jar", if we
> > > > stick
> > > > > to the current plan. We've
> > >  used the same naming strategy for 0.9.x, e.g.
> > > > > "spri
> > > ng-framework-0.9.1" but still "spring-full-0.9.jar". I pr
> > > efer that
> > > > way
> > > > > to ease drop-in replacement in the 
> > > literal sense :-) The build
> > > > properties
> > > > > reflect th
> > > is in "spring-version=1.0" and "spring-version-detail=1.0
> > > m1".
> > > > > 
> > > > > Juergen
> > > > > 
> > > > > 
> > > > >
> > > > >     -----Ur
> > > sprÃf¼ngliche Nachricht-----
> > > > >     Von: trisberg@trid
> > > b.com [ mailto:tri...@tr...]
> > > > >     Gesendet: Mo 
> > > 25.08.2003 19:21
> > > > >     An: jÃf¼rgen hÃf¶ller [werk3A
> > > T]
> > > > >     Cc: Lars Fischer; springframework-developer@l
> > > ists.sourceforge.net
> > > > >     Betreff: RE: [Springframewo
> > > rk-developer] Example classes needed
> > > > >    
> > > > >    
> > > >
> > >  >
> > > > >     Juergen,
> > > > >    
> > > > >     > Anyway, ContextL
> > > oaderServlet *will* be in 1.0 M1, to be released at
> > > > th
> > > e
> > > > > end
> > > > >     > of this week if there aren't any ma
> > > jor obstacles. BTW, can everybody
> > > > > please
> > > > >     > 
> > > test the current CVS contents against own applications?
> > > > >     >
> > > > >    
> > > > >     I am updating the Step-by-ste
> > > p-MVC document - what will the exact name
> > > > of
> > > > > the
> > > 
> > > > >     directory and the jar file be?  I'm assuming 'sp
> > > ring-framework-1.0M1'
> > > > and
> > > > >     'spring-full-1.0M1.
> > > jar'.
> > > > >    
> > > > >     Thomas
> > > > >    
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Springframework-developer mailing list
> > Spr...@li...
> > https://lists.sourceforge.net/lists/listinfo/springframework-developer
> > 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
> 

RE: [Springframework-developer] Example classes needed

[<jue...@we...>]

I've just added a manifest entry "Spring-Version" to our build scripts. =
This means that a "spring.jar" for 1.0 M1 will include a =
"Spring-Version=3D1.0m1" entry in its META-INF/manifest.mf file. So if =
you've got jar files lying around, you can always check the exact =
version. With this included, I tend to drop version numbers even more. =
Thanks for the idea, Rob - I just guess it's simpler to make a manifest =
entry than to include an extra file.

We all seem to agree we prefer "spring.jar" over "spring-full.jar", but =
are about 50:50 regarding version numbers in the name. So let's focus on =
the latter: Would anyone *mind* no version number in the name, given =
that it's mentioned in the manifest file? Everyone is free to rename the =
files any way he wants anyway, it's just about the shipped jars. As for =
me, I would mind the full version number "1.0m1" - in the meantime, I =
even prefer "spring.jar".

To keep the fire burning, some examples for no version numbers that I =
know of: Servlet, JUnit, JavaMail, Xerces, JSTL, Commons Logging, =
Commons DBCP, XAPool, Hibernate, COS, GLUE, Ant, Tomcat, JBoss, Clover. =
Counterexamples with version numbers in the jar name: JTA, CGLIB, BCEL, =
Log4J, Castor, Tyrex, Velocity, Tapestry, Hessian, iText, MySQL JDBC =
driver.

In the end, one can argue for all options. There is no obvious solution. =
So we should try to settle on one option and stick with it.

Juergen


-----Original Message-----
From: Rob Butler [mailto:rob...@ve...]
Sent: Thursday, August 28, 2003 6:34 PM
To: j=FCrgen h=F6ller [werk3AT]; Lars Fischer
Cc: spr...@li...; tri...@tr...;
rod...@in...
Subject: RE: [Springframework-developer] Example classes needed


Hello all,

Since spring is modular, why not break it down even further into =
chuncks.

spring-common.jar ->Basic stuff that is used everywhere in spring
spring-beans.jar -> contains ONLY the Spring Beans stuff.
spring-aop.jar -> contains ONLY the Spring AOP stuff.
spring-jdbc -> contains ONLY the Spring JDBC stuff.
spring-orm.jar -> contains ONLY the Spring ORM stuff.
spring-context.jar -> contains ONLY the Spring context stuff.
spring-mvc.jar -> contains ONLY the spring MVC stuff.

If spring-orm.jar is dependent upon spring-common.jar then the user will =
need to download and include spring-common.jar in the classpath too.  In =
this way people can pick and choose the exact parts they want, but you =
don't have to come up with a million different package combinations...  =
i.e. no packages that include ORM & JDBC, but not MVC.  Another one that =
has ORM, JDBC, context, but not MVC.  Another one that has ORM, jdbc & =
MVC.  Another one that has ORM, JDBC, context & MVC.  See where I am =
going with this?
People should be smart enough to take the parts they want, and to get =
the dependencies they need.

Now as far as the file name goes, why not just use a name WITHOUT the =
version name in it, and then include a file (or directory) in the root =
of the jar called VERSION-1.0.1 or some such thing.  That way people =
will not need to worry about changing build scripts to use a newer =
version of the jar that is API compatible, and they can still easiliy =
determine what version they are using by looking in the jar itself.  the =
only time the jar file name should change is if the API has LARGE =
changes that renders the new jar completely incompatible with the old =
API.  Minor changes to the API should probably not have the jar file =
names changed.

Just some ideas and my 2 cents.

Later
Rob

> From: j=FCrgen h=F6ller [werk3AT] <jue...@we...>
> Date: 2003/08/28 Thu PM 12:07:42 EDT
> To: "Lars Fischer" <lar...@gm...>
> CC: <spr...@li...>,=20
> 	<tri...@tr...>,=20
> 	<rod...@in...>
> Subject: RE: [Springframework-developer] Example classes needed
>=20
> Lars,
>=20
> The problem is that we have multiple jar files:
> - spring-beans.jar
> - spring-aop.jar
> - spring-jdbc.jar
> - spring-orm.jar
> - spring-context.jar
> - spring-full.jar
>=20
> "full" indicates that it includes all of Spring. We could name it =
"spring.jar" of course, I'm quite inclined towards this if others agree. =
What does everybody think?
>=20
> Regarding Colin's argument on in-between numbering: I wouldn't mind =
dropping the version number altogether, in Hibernate/Ant/Servlet style. =
I'm just not a fan of very specific file names.
>=20
> So 2 questions:
> 1. a) "spring-full.jar" or b) "spring.jar" for the complete jar file
> 2. a) "spring-beans-1.0m1.jar", b) "spring-beans-1.0.jar" or c) =
"spring-beans.jar"
>=20
> In the meantime, I tend to vote 1b and 2c. I wouldn't mind 1a or 2b =
either, though.
>=20
> Juergen
>=20
>=20
> -----Original Message-----
> From: Lars Fischer [mailto:lar...@gm...]
> Sent: Thursday, August 28, 2003 5:56 PM
> To: j=FCrgen h=F6ller [werk3AT]
> Cc: spr...@li...; =
tri...@tr...;
> rod...@in...
> Subject: RE: [Springframework-developer] Example classes needed
>=20
>=20
> What about spring.jar, spring2.jar ? I don't like this "-full".
>=20
>=20
> > Hmmm, not much response yet... I still tend to prefer "sp
> > ring-full-1.0.jar", for easy drop-in. IMO, a jar file doe
> > s not need to reflect the exact detail version. I conside
> > r it fine enough if it indicates the major version. See s
> > ervlet.jar, hibernate2.jar. Can we please decide on this=20
> > until *tomorrow*? :-)
> > =20
> > Juergen
> > =20
> > =20
> >=20
> > -----Original=20
> > Message-----
> > From: j=C3=BCrgen h=C3=B6ller [werk3AT]=20
> > Sent: Mon
> > day, August 25, 2003 11:50 PM
> > To: Lars Fischer; springfr
> > ame...@li...
> > Cc: trisberg@tri
> > db.com
> > Subject: Re: [Springframework-developer] Example=20
> > classes needed
> >=20
> >=20
> > Let's vote on this. I don't mind eith
> > er naming strategy for jar files. Anybody else prefering=20
> > the spring-full-1.0m1 style?
> > =20
> > BTW, Hibernate uses hibe
> > rnate2.jar for its whole 2.x tree. Log4J uses log4j-1.2.8
> > .jar for the specific version. 2 examples for opposite en
> > ds, I guess.
> > =20
> > Juergen
> > =20
> > =20
> >=20
> > -----Urspr=C3=BCngliche Nac
> > hricht-----=20
> > Von: Lars Fischer [mailto:lars.fischer@gmxp
> > ro.net]=20
> > Gesendet: Mo 25.08.2003 23:18=20
> > An: springframe
> > wor...@li...=20
> > Cc: j=C3=BCrgen h=C3=B6lle
> > r [werk3AT]; tri...@tr...=20
> > Betreff: Re: [Springfra
> > mework-developer] Example classes needed
> >=20
> >=20
> >=20
> > I agree w
> > ith Thomas, I once made a mistake because I didn't realiz
> > e
> > that I was using an older version. The jar-files shoul
> > d be named after
> > the version.
> >=20
> > > Juergen,
> > >
> > > The dr
> > awback then is that you can't tell from the jar file if i
> > t is M1, M2
> > > or
> > > the release jar.
> > >
> > > Thomas
> > >
> > >=20
> > > It's gonna be "spring-framework-1.0m1" and "spring-full
> > -1.0.jar", if we
> > > stick
> > > > to the current plan. We've
> >  used the same naming strategy for 0.9.x, e.g.
> > > > "spri
> > ng-framework-0.9.1" but still "spring-full-0.9.jar". I pr
> > efer that
> > > way
> > > > to ease drop-in replacement in the=20
> > literal sense :-) The build
> > > properties
> > > > reflect th
> > is in "spring-version=3D1.0" and "spring-version-detail=3D1.0
> > m1".
> > > >=20
> > > > Juergen
> > > >=20
> > > >=20
> > > >
> > > >     -----Ur
> > spr=C3f=C2=BCngliche Nachricht-----
> > > >     Von: trisberg@trid
> > b.com [ mailto:tri...@tr...]
> > > >     Gesendet: Mo=20
> > 25.08.2003 19:21
> > > >     An: j=C3f=C2=BCrgen h=C3f=C2=B6ller [werk3A
> > T]
> > > >     Cc: Lars Fischer; springframework-developer@l
> > ists.sourceforge.net
> > > >     Betreff: RE: [Springframewo
> > rk-developer] Example classes needed
> > > >   =20
> > > >   =20
> > >
> >  >
> > > >     Juergen,
> > > >   =20
> > > >     > Anyway, ContextL
> > oaderServlet *will* be in 1.0 M1, to be released at
> > > th
> > e
> > > > end
> > > >     > of this week if there aren't any ma
> > jor obstacles. BTW, can everybody
> > > > please
> > > >     >=20
> > test the current CVS contents against own applications?
> > > >     >
> > > >   =20
> > > >     I am updating the Step-by-ste
> > p-MVC document - what will the exact name
> > > of
> > > > the
> >=20
> > > >     directory and the jar file be?  I'm assuming 'sp
> > ring-framework-1.0M1'
> > > and
> > > >     'spring-full-1.0M1.
> > jar'.
> > > >   =20
> > > >     Thomas
> > > >   =20
> > > >
> > > >
> > >
> > >
> > >
> >=20
> >=20
> >=20
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20

RE: [Springframework-developer] Example classes needed

[<rod...@in...>]

>1. a) "spring-full.jar" or b) "spring.jar" for the complete 
jar file 
>2. a) "spring-beans-1.0m1.jar", b) "spring-beans-1.0.jar" or 
c) "spring-beans.jar" 

1b although I don't mind 1a either
2a - I like version info as I tend to dump a bunch of stuff 
in WEB-INF/lib or the like and like to be able to see what 
version I have.

Re: [Springframework-developer] Example classes needed

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

+1 for 1b and 2c. I think excess version info in the names creates more 
problems than it solves.

Ken

jürgen höller [werk3AT] wrote:

>Lars,
>
>The problem is that we have multiple jar files:
>- spring-beans.jar
>- spring-aop.jar
>- spring-jdbc.jar
>- spring-orm.jar
>- spring-context.jar
>- spring-full.jar
>
>"full" indicates that it includes all of Spring. We could name it "spring.jar" of course, I'm quite inclined towards this if others agree. What does everybody think?
>
>Regarding Colin's argument on in-between numbering: I wouldn't mind dropping the version number altogether, in Hibernate/Ant/Servlet style. I'm just not a fan of very specific file names.
>
>So 2 questions:
>1. a) "spring-full.jar" or b) "spring.jar" for the complete jar file
>2. a) "spring-beans-1.0m1.jar", b) "spring-beans-1.0.jar" or c) "spring-beans.jar"
>
>In the meantime, I tend to vote 1b and 2c. I wouldn't mind 1a or 2b either, though.
>
>Juergen
>
>
>  
>

[Springframework-developer] =?iso-8859-1?Q?RE:_[Springframework-developer]_Example_classes_needed?=

[=?iso-8859-1?Q?<jp....@ti...>]

Juergen,=0D=0A=0D=0AWhy could we not have spring-<module_part>.jar for in=
complete jars and spring.jar for the full package?=0D=0A=0D=0AI vote for =
1b and 2c for consistency.=0D=0A2a and 2b are not consistent with the ful=
l package name.=0D=0A=0D=0AJean-Pierre=0D=0A=0D=0A---------- Initial Head=
er -----------=0D=0A=0D=0AFrom      : springframework-developer-admin@lis=
ts.sourceforge.net=0D=0ATo          : "Lars Fischer" <lars.fischer@gmxpro=
.net>=0D=0ACc          : <spr...@li...=
>,<tri...@tr...>,<rod...@in...>=0D=0ADate      : Thu=
, 28 Aug 2003 18:07:42 +0200=0D=0ASubject : RE: [Springframework-develope=
r] Example classes needed=0D=0A=0D=0ALars,=0D=0A=0D=0AThe problem is that=
 we have multiple jar files:=0D=0A- spring-beans.jar=0D=0A- spring-aop.ja=
r=0D=0A- spring-jdbc.jar=0D=0A- spring-orm.jar=0D=0A- spring-context.jar=0D=
=0A- spring-full.jar=0D=0A=0D=0A"full" indicates that it includes all of =
Spring. We could name it "spring.jar" of course, I'm quite inclined towar=
ds this if others agree. What does everybody think?=0D=0A=0D=0ARegarding =
Colin's argument on in-between numbering: I wouldn't mind dropping the ve=
rsion number altogether, in Hibernate/Ant/Servlet style. I'm just not a f=
an of very specific file names.=0D=0A=0D=0ASo 2 questions:=0D=0A1. a) "sp=
ring-full.jar" or b) "spring.jar" for the complete jar file=0D=0A2. a) "s=
pring-beans-1.0m1.jar", b) "spring-beans-1.0.jar" or c) "spring-beans.jar=
"=0D=0A=0D=0AIn the meantime, I tend to vote 1b and 2c. I wouldn't mind 1=
a or 2b either, though.=0D=0A=0D=0AJuergen=0D=0A=0D=0A=0D=0A-----Original=
 Message-----=0D=0AFrom: Lars Fischer [mailto:lar...@gm...]=0D=
=0ASent: Thursday, August 28, 2003 5:56 PM=0D=0ATo: j=FCrgen h=F6ller [we=
rk3AT]=0D=0ACc: spr...@li...; trisberg=
@tridb.com;=0D=...@in...=0D=0ASubject: RE: [Springfra=
mework-developer] Example classes needed=0D=0A=0D=0A=0D=0AWhat about spri=
ng.jar, spring2.jar ? I don't like this "-full".=0D=0A=0D=0A=0D=0A> Hmmm,=
 not much response yet... I still tend to prefer "sp=0D=0A> ring-full-1.0=
.jar", for easy drop-in. IMO, a jar file doe=0D=0A> s not need to reflect=
 the exact detail version. I conside=0D=0A> r it fine enough if it indica=
tes the major version. See s=0D=0A> ervlet.jar, hibernate2.jar. Can we pl=
ease decide on this =0D=0A> until *tomorrow*? :-)=0D=0A>  =0D=0A> Juergen=
=0D=0A>  =0D=0A>  =0D=0A> =0D=0A> -----Original =0D=0A> Message-----=0D=0A=
> From: j=C3=BCrgen h=C3=B6ller [werk3AT] =0D=0A> Sent: Mon=0D=0A> day, A=
ugust 25, 2003 11:50 PM=0D=0A> To: Lars Fischer; springfr=0D=0A> amework-=
dev...@li...=0D=0A> Cc: trisberg@tri=0D=0A> db.com=0D=0A=
> Subject: Re: [Springframework-developer] Example =0D=0A> classes needed=
=0D=0A> =0D=0A> =0D=0A> Let's vote on this. I don't mind eith=0D=0A> er n=
aming strategy for jar files. Anybody else prefering =0D=0A> the spring-f=
ull-1.0m1 style?=0D=0A>  =0D=0A> BTW, Hibernate uses hibe=0D=0A> rnate2.j=
ar for its whole 2.x tree. Log4J uses log4j-1.2.8=0D=0A> .jar for the spe=
cific version. 2 examples for opposite en=0D=0A> ds, I guess.=0D=0A>  =0D=
=0A> Juergen=0D=0A>  =0D=0A>  =0D=0A> =0D=0A> -----Urspr=C3=BCngliche Nac=
=0D=0A> hricht----- =0D=0A> Von: Lars Fischer [mailto:lars.fischer@gmxp=0D=
=0A> ro.net] =0D=0A> Gesendet: Mo 25.08.2003 23:18 =0D=0A> An: springfram=
e=0D=0A> wor...@li... =0D=0A> Cc: j=C3=BCrgen h=C3=
=B6lle=0D=0A> r [werk3AT]; tri...@tr... =0D=0A> Betreff: Re: [Sprin=
gfra=0D=0A> mework-developer] Example classes needed=0D=0A> =0D=0A> =0D=0A=
> =0D=0A> I agree w=0D=0A> ith Thomas, I once made a mistake because I di=
dn't realiz=0D=0A> e=0D=0A> that I was using an older version. The jar-fi=
les shoul=0D=0A> d be named after=0D=0A> the version.=0D=0A> =0D=0A> > Ju=
ergen,=0D=0A> >=0D=0A> > The dr=0D=0A> awback then is that you can't tell=
 from the jar file if i=0D=0A> t is M1, M2=0D=0A> > or=0D=0A> > the relea=
se jar.=0D=0A> >=0D=0A> > Thomas=0D=0A> >=0D=0A> > =0D=0A> > It's gonna b=
e "spring-framework-1.0m1" and "spring-full=0D=0A> -1.0.jar", if we=0D=0A=
> > stick=0D=0A> > > to the current plan. We've=0D=0A>  used the same nam=
ing strategy for 0.9.x, e.g.=0D=0A> > > "spri=0D=0A> ng-framework-0.9.1" =
but still "spring-full-0.9.jar". I pr=0D=0A> efer that=0D=0A> > way=0D=0A=
> > > to ease drop-in replacement in the =0D=0A> literal sense :-) The bu=
ild=0D=0A> > properties=0D=0A> > > reflect th=0D=0A> is in "spring-versio=
n=3D1.0" and "spring-version-detail=3D1.0=0D=0A> m1".=0D=0A> > > =0D=0A> =
> > Juergen=0D=0A> > > =0D=0A> > > =0D=0A> > >=0D=0A> > >     -----Ur=0D=0A=
> spr=C3f=C2=BCngliche Nachricht-----=0D=0A> > >     Von: trisberg@trid=0D=
=0A> b.com [ mailto:tri...@tr...]=0D=0A> > >     Gesendet: Mo =0D=0A=
> 25.08.2003 19:21=0D=0A> > >     An: j=C3f=C2=BCrgen h=C3f=C2=B6ller [we=
rk3A=0D=0A> T]=0D=0A> > >     Cc: Lars Fischer; springframework-developer=
@l=0D=0A> ists.sourceforge.net=0D=0A> > >     Betreff: RE: [Springframewo=
=0D=0A> rk-developer] Example classes needed=0D=0A> > >    =0D=0A> > >   =
 =0D=0A> >=0D=0A>  >=0D=0A> > >     Juergen,=0D=0A> > >    =0D=0A> > >   =
  > Anyway, ContextL=0D=0A> oaderServlet *will* be in 1.0 M1, to be relea=
sed at=0D=0A> > th=0D=0A> e=0D=0A> > > end=0D=0A> > >     > of this week =
if there aren't any ma=0D=0A> jor obstacles. BTW, can everybody=0D=0A> > =
> please=0D=0A> > >     > =0D=0A> test the current CVS contents against o=
wn applications?=0D=0A> > >     >=0D=0A> > >    =0D=0A> > >     I am upda=
ting the Step-by-ste=0D=0A> p-MVC document - what will the exact name=0D=0A=
> > of=0D=0A> > > the=0D=0A> =0D=0A> > >     directory and the jar file b=
e?  I'm assuming 'sp=0D=0A> ring-framework-1.0M1'=0D=0A> > and=0D=0A> > >=
     'spring-full-1.0M1.=0D=0A> jar'.=0D=0A> > >    =0D=0A> > >     Thoma=
s=0D=0A> > >    =0D=0A> > >=0D=0A> > >=0D=0A> >=0D=0A> >=0D=0A> >=0D=0A> =
=0D=0A> =0D=0A> =0D=0A=0D=0A=0D=0A=0D=0A---------------------------------=
----------------------=0D=0AThis sf.net email is sponsored by:ThinkGeek=0D=
=0AWelcome to geek heaven.=0D=0Ahttp://thinkgeek.com/sf=0D=0A____________=
___________________________________=0D=0ASpringframework-developer mailin=
g lis...@li...=0D=0Ahttps://=
lists.sourceforge.net/lists/listinfo/springframework-developer=0D=0A=0A=0A=
********** L'ADSL A 20 EUR/MOIS********** =0AAvec Tiscali, l'ADSL est =E0=
 20 EUR/mois. Vous pourrez chercher longtemps avant de trouver moins cher=
 ! =0APour profiter de cette offre exceptionnelle, cliquez ici : http://r=
egister.tiscali.fr/adsl/=0AOffre soumise =E0 conditions.=0A

RE: [Springframework-developer] Example classes needed

[<tri...@tr...>]

1b and 2c ('spring.jar' and 'spring-beans.jar') +1

Once we decide on a naming structure - I will need a some time to modify the
MVC-step-by-step documents that are part of the release.  So let's finalize this
today if we can :-)

Thomas


> Lars,
> 
> The problem is that we have multiple jar files:
> - spring-beans.jar
> - spring-aop.jar
> - spring-jdbc.jar
> - spring-orm.jar
> - spring-context.jar
> - spring-full.jar
> 
> "full" indicates that it includes all of Spring. We could name it
> "spring.jar" of course, I'm quite inclined towards this if others agree. What
> does everybody think?
> 
> Regarding Colin's argument on in-between numbering: I wouldn't mind dropping
> the version number altogether, in Hibernate/Ant/Servlet style. I'm just not a
> fan of very specific file names.
> 
> So 2 questions:
> 1. a) "spring-full.jar" or b) "spring.jar" for the complete jar file
> 2. a) "spring-beans-1.0m1.jar", b) "spring-beans-1.0.jar" or c)
> "spring-beans.jar"
> 
> In the meantime, I tend to vote 1b and 2c. I wouldn't mind 1a or 2b either,
> though.
> 
> Juergen
> 
> 
> -----Original Message-----
> From: Lars Fischer [mailto:lar...@gm...]
> Sent: Thursday, August 28, 2003 5:56 PM
> To: jürgen höller [werk3AT]
> Cc: spr...@li...; tri...@tr...;
> rod...@in...
> Subject: RE: [Springframework-developer] Example classes needed
> 
> 
> What about spring.jar, spring2.jar ? I don't like this "-full".
> 
> 
> > Hmmm, not much response yet... I still tend to prefer "sp
> > ring-full-1.0.jar", for easy drop-in. IMO, a jar file doe
> > s not need to reflect the exact detail version. I conside
> > r it fine enough if it indicates the major version. See s
> > ervlet.jar, hibernate2.jar. Can we please decide on this 
> > until *tomorrow*? :-)
> >  
> > Juergen
> >  
> >  
> > 
> > -----Original 
> > Message-----
> > From: jürgen höller [werk3AT] 
> > Sent: Mon
> > day, August 25, 2003 11:50 PM
> > To: Lars Fischer; springfr
> > ame...@li...
> > Cc: trisberg@tri
> > db.com
> > Subject: Re: [Springframework-developer] Example 
> > classes needed
> > 
> > 
> > Let's vote on this. I don't mind eith
> > er naming strategy for jar files. Anybody else prefering 
> > the spring-full-1.0m1 style?
> >  
> > BTW, Hibernate uses hibe
> > rnate2.jar for its whole 2.x tree. Log4J uses log4j-1.2.8
> > .jar for the specific version. 2 examples for opposite en
> > ds, I guess.
> >  
> > Juergen
> >  
> >  
> > 
> > -----Ursprüngliche Nac
> > hricht----- 
> > Von: Lars Fischer [mailto:lars.fischer@gmxp
> > ro.net] 
> > Gesendet: Mo 25.08.2003 23:18 
> > An: springframe
> > wor...@li... 
> > Cc: jürgen hölle
> > r [werk3AT]; tri...@tr... 
> > Betreff: Re: [Springfra
> > mework-developer] Example classes needed
> > 
> > 
> > 
> > I agree w
> > ith Thomas, I once made a mistake because I didn't realiz
> > e
> > that I was using an older version. The jar-files shoul
> > d be named after
> > the version.
> > 
> > > Juergen,
> > >
> > > The dr
> > awback then is that you can't tell from the jar file if i
> > t is M1, M2
> > > or
> > > the release jar.
> > >
> > > Thomas
> > >
> > > 
> > > It's gonna be "spring-framework-1.0m1" and "spring-full
> > -1.0.jar", if we
> > > stick
> > > > to the current plan. We've
> >  used the same naming strategy for 0.9.x, e.g.
> > > > "spri
> > ng-framework-0.9.1" but still "spring-full-0.9.jar". I pr
> > efer that
> > > way
> > > > to ease drop-in replacement in the 
> > literal sense :-) The build
> > > properties
> > > > reflect th
> > is in "spring-version=1.0" and "spring-version-detail=1.0
> > m1".
> > > > 
> > > > Juergen
> > > > 
> > > > 
> > > >
> > > >     -----Ur
> > sprÃf¼ngliche Nachricht-----
> > > >     Von: trisberg@trid
> > b.com [ mailto:tri...@tr...]
> > > >     Gesendet: Mo 
> > 25.08.2003 19:21
> > > >     An: jÃf¼rgen hÃf¶ller [werk3A
> > T]
> > > >     Cc: Lars Fischer; springframework-developer@l
> > ists.sourceforge.net
> > > >     Betreff: RE: [Springframewo
> > rk-developer] Example classes needed
> > > >    
> > > >    
> > >
> >  >
> > > >     Juergen,
> > > >    
> > > >     > Anyway, ContextL
> > oaderServlet *will* be in 1.0 M1, to be released at
> > > th
> > e
> > > > end
> > > >     > of this week if there aren't any ma
> > jor obstacles. BTW, can everybody
> > > > please
> > > >     > 
> > test the current CVS contents against own applications?
> > > >     >
> > > >    
> > > >     I am updating the Step-by-ste
> > p-MVC document - what will the exact name
> > > of
> > > > the
> > 
> > > >     directory and the jar file be?  I'm assuming 'sp
> > ring-framework-1.0M1'
> > > and
> > > >     'spring-full-1.0M1.
> > jar'.
> > > >    
> > > >     Thomas
> > > >    
> > > >
> > > >
> > >
> > >
> > >
> > 
> > 
> > 
> 
> 

RE: [Springframework-developer] Example classes needed

[<jue...@we...>]

Lars,

The problem is that we have multiple jar files:
- spring-beans.jar
- spring-aop.jar
- spring-jdbc.jar
- spring-orm.jar
- spring-context.jar
- spring-full.jar

"full" indicates that it includes all of Spring. We could name it =
"spring.jar" of course, I'm quite inclined towards this if others agree. =
What does everybody think?

Regarding Colin's argument on in-between numbering: I wouldn't mind =
dropping the version number altogether, in Hibernate/Ant/Servlet style. =
I'm just not a fan of very specific file names.

So 2 questions:
1. a) "spring-full.jar" or b) "spring.jar" for the complete jar file
2. a) "spring-beans-1.0m1.jar", b) "spring-beans-1.0.jar" or c) =
"spring-beans.jar"

In the meantime, I tend to vote 1b and 2c. I wouldn't mind 1a or 2b =
either, though.

Juergen


-----Original Message-----
From: Lars Fischer [mailto:lar...@gm...]
Sent: Thursday, August 28, 2003 5:56 PM
To: j=FCrgen h=F6ller [werk3AT]
Cc: spr...@li...; tri...@tr...;
rod...@in...
Subject: RE: [Springframework-developer] Example classes needed


What about spring.jar, spring2.jar ? I don't like this "-full".


> Hmmm, not much response yet... I still tend to prefer "sp
> ring-full-1.0.jar", for easy drop-in. IMO, a jar file doe
> s not need to reflect the exact detail version. I conside
> r it fine enough if it indicates the major version. See s
> ervlet.jar, hibernate2.jar. Can we please decide on this=20
> until *tomorrow*? :-)
> =20
> Juergen
> =20
> =20
>=20
> -----Original=20
> Message-----
> From: j=C3=BCrgen h=C3=B6ller [werk3AT]=20
> Sent: Mon
> day, August 25, 2003 11:50 PM
> To: Lars Fischer; springfr
> ame...@li...
> Cc: trisberg@tri
> db.com
> Subject: Re: [Springframework-developer] Example=20
> classes needed
>=20
>=20
> Let's vote on this. I don't mind eith
> er naming strategy for jar files. Anybody else prefering=20
> the spring-full-1.0m1 style?
> =20
> BTW, Hibernate uses hibe
> rnate2.jar for its whole 2.x tree. Log4J uses log4j-1.2.8
> .jar for the specific version. 2 examples for opposite en
> ds, I guess.
> =20
> Juergen
> =20
> =20
>=20
> -----Urspr=C3=BCngliche Nac
> hricht-----=20
> Von: Lars Fischer [mailto:lars.fischer@gmxp
> ro.net]=20
> Gesendet: Mo 25.08.2003 23:18=20
> An: springframe
> wor...@li...=20
> Cc: j=C3=BCrgen h=C3=B6lle
> r [werk3AT]; tri...@tr...=20
> Betreff: Re: [Springfra
> mework-developer] Example classes needed
>=20
>=20
>=20
> I agree w
> ith Thomas, I once made a mistake because I didn't realiz
> e
> that I was using an older version. The jar-files shoul
> d be named after
> the version.
>=20
> > Juergen,
> >
> > The dr
> awback then is that you can't tell from the jar file if i
> t is M1, M2
> > or
> > the release jar.
> >
> > Thomas
> >
> >=20
> > It's gonna be "spring-framework-1.0m1" and "spring-full
> -1.0.jar", if we
> > stick
> > > to the current plan. We've
>  used the same naming strategy for 0.9.x, e.g.
> > > "spri
> ng-framework-0.9.1" but still "spring-full-0.9.jar". I pr
> efer that
> > way
> > > to ease drop-in replacement in the=20
> literal sense :-) The build
> > properties
> > > reflect th
> is in "spring-version=3D1.0" and "spring-version-detail=3D1.0
> m1".
> > >=20
> > > Juergen
> > >=20
> > >=20
> > >
> > >     -----Ur
> spr=C3f=C2=BCngliche Nachricht-----
> > >     Von: trisberg@trid
> b.com [ mailto:tri...@tr...]
> > >     Gesendet: Mo=20
> 25.08.2003 19:21
> > >     An: j=C3f=C2=BCrgen h=C3f=C2=B6ller [werk3A
> T]
> > >     Cc: Lars Fischer; springframework-developer@l
> ists.sourceforge.net
> > >     Betreff: RE: [Springframewo
> rk-developer] Example classes needed
> > >   =20
> > >   =20
> >
>  >
> > >     Juergen,
> > >   =20
> > >     > Anyway, ContextL
> oaderServlet *will* be in 1.0 M1, to be released at
> > th
> e
> > > end
> > >     > of this week if there aren't any ma
> jor obstacles. BTW, can everybody
> > > please
> > >     >=20
> test the current CVS contents against own applications?
> > >     >
> > >   =20
> > >     I am updating the Step-by-ste
> p-MVC document - what will the exact name
> > of
> > > the
>=20
> > >     directory and the jar file be?  I'm assuming 'sp
> ring-framework-1.0M1'
> > and
> > >     'spring-full-1.0M1.
> jar'.
> > >   =20
> > >     Thomas
> > >   =20
> > >
> > >
> >
> >
> >
>=20
>=20
>=20

RE: [Springframework-developer] Example classes needed

[Lars F. <lar...@gm...>]

What about spring.jar, spring2.jar ? I don't like this "-full".


> Hmmm, not much response yet... I still tend to prefer "sp
> ring-full-1.0.jar", for easy drop-in. IMO, a jar file doe
> s not need to reflect the exact detail version. I conside
> r it fine enough if it indicates the major version. See s
> ervlet.jar, hibernate2.jar. Can we please decide on this 
> until *tomorrow*? :-)
>  
> Juergen
>  
>  
> 
> -----Original 
> Message-----
> From: jürgen höller [werk3AT] 
> Sent: Mon
> day, August 25, 2003 11:50 PM
> To: Lars Fischer; springfr
> ame...@li...
> Cc: trisberg@tri
> db.com
> Subject: Re: [Springframework-developer] Example 
> classes needed
> 
> 
> Let's vote on this. I don't mind eith
> er naming strategy for jar files. Anybody else prefering 
> the spring-full-1.0m1 style?
>  
> BTW, Hibernate uses hibe
> rnate2.jar for its whole 2.x tree. Log4J uses log4j-1.2.8
> .jar for the specific version. 2 examples for opposite en
> ds, I guess.
>  
> Juergen
>  
>  
> 
> -----Ursprüngliche Nac
> hricht----- 
> Von: Lars Fischer [mailto:lars.fischer@gmxp
> ro.net] 
> Gesendet: Mo 25.08.2003 23:18 
> An: springframe
> wor...@li... 
> Cc: jürgen hölle
> r [werk3AT]; tri...@tr... 
> Betreff: Re: [Springfra
> mework-developer] Example classes needed
> 
> 
> 
> I agree w
> ith Thomas, I once made a mistake because I didn't realiz
> e
> that I was using an older version. The jar-files shoul
> d be named after
> the version.
> 
> > Juergen,
> >
> > The dr
> awback then is that you can't tell from the jar file if i
> t is M1, M2
> > or
> > the release jar.
> >
> > Thomas
> >
> > 
> > It's gonna be "spring-framework-1.0m1" and "spring-full
> -1.0.jar", if we
> > stick
> > > to the current plan. We've
>  used the same naming strategy for 0.9.x, e.g.
> > > "spri
> ng-framework-0.9.1" but still "spring-full-0.9.jar". I pr
> efer that
> > way
> > > to ease drop-in replacement in the 
> literal sense :-) The build
> > properties
> > > reflect th
> is in "spring-version=1.0" and "spring-version-detail=1.0
> m1".
> > > 
> > > Juergen
> > > 
> > > 
> > >
> > >     -----Ur
> sprüngliche Nachricht-----
> > >     Von: trisberg@trid
> b.com [ mailto:tri...@tr...]
> > >     Gesendet: Mo 
> 25.08.2003 19:21
> > >     An: jürgen höller [werk3A
> T]
> > >     Cc: Lars Fischer; springframework-developer@l
> ists.sourceforge.net
> > >     Betreff: RE: [Springframewo
> rk-developer] Example classes needed
> > >    
> > >    
> >
>  >
> > >     Juergen,
> > >    
> > >     > Anyway, ContextL
> oaderServlet *will* be in 1.0 M1, to be released at
> > th
> e
> > > end
> > >     > of this week if there aren't any ma
> jor obstacles. BTW, can everybody
> > > please
> > >     > 
> test the current CVS contents against own applications?
> > >     >
> > >    
> > >     I am updating the Step-by-ste
> p-MVC document - what will the exact name
> > of
> > > the
> 
> > >     directory and the jar file be?  I'm assuming 'sp
> ring-framework-1.0M1'
> > and
> > >     'spring-full-1.0M1.
> jar'.
> > >    
> > >     Thomas
> > >    
> > >
> > >
> >
> >
> >
> 
> 
> 

[Springframework-developer] =?iso-8859-1?Q?Re:_[Springframework-developer]_Example_classes_needed?=

[=?iso-8859-1?Q?<jp....@ti...>]

+1 for spring-full.jar=0D=0A=0D=0AJean-Pierre=0D=0A=0D=0A---------- Initi=
al Header -----------=0D=0A=0D=0AFrom      : springframework-developer-ad=
mi...@li...=0D=0ATo          : "j=FCrgen h=F6ller [werk3AT]=
" <jue...@we...>=0D=0ACc          : springframework-develo=
pe...@li...=0D=0ADate      : Thu, 28 Aug 2003 09:32:35 -040=
0=0D=0ASubject : Re: [Springframework-developer] Example classes needed=0D=
=0A=0D=0AWell in this case, I think the best choice is probably something=
 like =0D=0Aspring-full.jar for this version, then something like =0D=0As=
pring2-full.jar/spring-full2.jar for the next version which breaks api =0D=
=0Acompatibility, etc. This works on the assumption that people are =0D=0A=
manually managing dependencies, and allows people to slip in new jars =0D=
=0Awithout changing references when the api has not changed. Then for mav=
en =0D=0Ausage, what would happen is that it would be uploaded to ibiblio=
 (or =0D=0Awhatever maven repository) with the full version number, for e=
xample, =0D=0Aspring-full-1.0.1.jar. The maven users would specify the ex=
act version =0D=0Ain the project files.=0D=0A=0D=0AThe alternative, to ha=
ve the full version in the the name, is almost as =0D=0Agood, as the manu=
al people can rename it to whatever they like.=0D=0A=0D=0ABut I don't lik=
e the in-between variant. It's not exact enough for maven =0D=0Ahandling,=
 and too exact for manual handling.=0D=0A=0D=0AAgain, when the api is no =
longer upwards compatible and you have =0D=0Asomething like hibernate vs =
hibernate2, I think that needs to be =0D=0Areflected in the name since I =
basically consider those different =0D=0Aapis/libs, not just different ve=
rsions.=0D=0A=0D=0AJusty my opinion :-)=0D=0A=0D=0A=0D=0Aj=FCrgen h=F6lle=
r [werk3AT] wrote:=0D=0A=0D=0A>We manage our dependencies manually here a=
t werk3AT :-) And as far as I remember, no Hibernate user has complained =
about hibernate2.jar yet.=0D=0A>=0D=0A>Juergen=0D=0A>=0D=0A>=0D=0A>-----O=
riginal Message-----=0D=0A>From: Colin Sampaleanu [mailto:colinml1@exis.c=
om]=0D=0A>Sent: Thursday, August 28, 2003 3:04 PM=0D=0A>To: j=FCrgen h=F6=
ller [werk3AT]=0D=0A>Cc: spr...@li...=0D=
=0A>Subject: Re: [Springframework-developer] Example classes needed=0D=0A=
>=0D=0A>=0D=0A>To throw some water into the fire, :-), I prefer the exact=
 name when =0D=0A>using Maven, since I can enforce what I am getting, but=
 when managing =0D=0A>dependencies manually, I prefer not to have a versi=
on in the name except =0D=0A>when it is something like a major version nu=
mber which indicates a =0D=0A>different api; then I can slip a new versio=
n in as needed without =0D=0A>changing all references.=0D=0A>=0D=0A>j=FCr=
gen h=F6ller [werk3AT] wrote:=0D=0A>=0D=0A>  =0D=0A>=0D=0A>>Hmmm, not muc=
h response yet... I still tend to prefer =0D=0A>>"spring-full-1.0.jar", f=
or easy drop-in. IMO, a jar file does not need =0D=0A>>to reflect the exa=
ct detail version. I consider it fine enough if it =0D=0A>>indicates the =
major version. See servlet.jar, hibernate2.jar. Can we =0D=0A>>please dec=
ide on this until *tomorrow*? :-)=0D=0A>> =0D=0A>>Juergen=0D=0A>> =0D=0A>=
> =0D=0A>>=0D=0A>>    -----Original Message-----=0D=0A>>    *From:* j=FCr=
gen h=F6ller [werk3AT]=0D=0A>>    *Sent:* Monday, August 25, 2003 11:50 P=
M=0D=0A>>    *To:* Lars Fischer; spr...@li...=
rge.net=0D=0A>>    *Cc:* tri...@tr...=0D=0A>>    *Subject:* Re: [Sp=
ringframework-developer] Example classes needed=0D=0A>>=0D=0A>>    Let's =
vote on this. I don't mind either naming strategy for jar=0D=0A>>    file=
s. Anybody else prefering the spring-full-1.0m1 style?=0D=0A>>     =0D=0A=
>>    BTW, Hibernate uses hibernate2.jar for its whole 2.x tree. Log4J=0D=
=0A>>    uses log4j-1.2.8.jar for the specific version. 2 examples for=0D=
=0A>>    opposite ends, I guess.=0D=0A>>     =0D=0A>>    Juergen=0D=0A>> =
    =0D=0A>>     =0D=0A>>=0D=0A>>        -----Urspr=FCngliche Nachricht--=
---=0D=0A>>        *Von:* Lars Fischer [mailto:lar...@gm...]=0D=
=0A>>        *Gesendet:* Mo 25.08.2003 23:18=0D=0A>>        *An:* springf=
ram...@li...=0D=0A>>        *Cc:* j=FCrgen h=F6=
ller [werk3AT]; tri...@tr...=0D=0A>>        *Betreff:* Re: [Springf=
ramework-developer] Example classes needed=0D=0A>>=0D=0A>>        I agree=
 with Thomas, I once made a mistake because I didn't=0D=0A>>        reali=
ze=0D=0A>>        that I was using an older version. The jar-files should=
 be=0D=0A>>        named after=0D=0A>>        the version.=0D=0A>>=0D=0A>=
>        > Juergen,=0D=0A>>        >=0D=0A>>        > The drawback then i=
s that you can't tell from the jar file=0D=0A>>        if it is M1, M2=0D=
=0A>>        > or=0D=0A>>        > the release jar.=0D=0A>>        >=0D=0A=
>>        > Thomas=0D=0A>>        >=0D=0A>>        > > It's gonna be "spr=
ing-framework-1.0m1" and=0D=0A>>        "spring-full-1.0.jar", if we=0D=0A=
>>        > stick=0D=0A>>        > > to the current plan. We've used the =
same naming strategy=0D=0A>>        for 0.9.x, e.g.=0D=0A>>        > > "s=
pring-framework-0.9.1" but still "spring-full-0.9.jar".=0D=0A>>        I =
prefer that=0D=0A>>        > way=0D=0A>>        > > to ease drop-in repla=
cement in the literal sense :-) The build=0D=0A>>        > properties=0D=0A=
>>        > > reflect this in "spring-version=3D1.0" and=0D=0A>>        "=
spring-version-detail=3D1.0m1".=0D=0A>>        > > =0D=0A>>        > > Ju=
ergen=0D=0A>>        > > =0D=0A>>        > > =0D=0A>>        > >=0D=0A>> =
       > >     -----Urspr=C3=BCngliche Nachricht-----=0D=0A>>        > > =
    Von: tri...@tr... [mailto:tri...@tr...]=0D=0A>>        > =
>     Gesendet: Mo 25.08.2003 19:21=0D=0A>>        > >     An: j=C3=BCrge=
n h=C3=B6ller [werk3AT]=0D=0A>>        > >     Cc: Lars Fischer;=0D=0A>> =
       spr...@li...=0D=0A>>        > >=
     Betreff: RE: [Springframework-developer] Example=0D=0A>>        clas=
ses needed=0D=0A>>        > >    =0D=0A>>        > >    =0D=0A>>        >=
 >=0D=0A>>        > >     Juergen,=0D=0A>>        > >    =0D=0A>>        =
> >     > Anyway, ContextLoaderServlet *will* be in 1.0 M1, to=0D=0A>>   =
     be released at=0D=0A>>        > the=0D=0A>>        > > end=0D=0A>>  =
      > >     > of this week if there aren't any major obstacles.=0D=0A>>=
        BTW, can everybody=0D=0A>>        > > please=0D=0A>>        > >  =
   > test the current CVS contents against own applications?=0D=0A>>     =
   > >     >=0D=0A>>        > >    =0D=0A>>        > >     I am updating =
the Step-by-step-MVC document - what=0D=0A>>        will the exact name=0D=
=0A>>        > of=0D=0A>>        > > the=0D=0A>>        > >     directory=
 and the jar file be?  I'm assuming=0D=0A>>        'spring-framework-1.0M=
1'=0D=0A>>        > and=0D=0A>>        > >     'spring-full-1.0M1.jar'.=0D=
=0A>>        > >    =0D=0A>>        > >     Thomas=0D=0A>>        > >    =
=0D=0A>>        > >=0D=0A>>        > >=0D=0A>>        >=0D=0A>>        >=0D=
=0A>>        >=0D=0A>>=0D=0A>>    =0D=0A>>=0D=0A>=0D=0A>=0D=0A>  =0D=0A>=0D=
=0A=0D=0A=0D=0A=0D=0A=0D=0A----------------------------------------------=
---------=0D=0AThis sf.net email is sponsored by:ThinkGeek=0D=0AWelcome t=
o geek heaven.=0D=0Ahttp://thinkgeek.com/sf=0D=0A________________________=
_______________________=0D=0ASpringframework-developer mailing list=0D=0A=
Spr...@li...=0D=0Ahttps://lists.source=
forge.net/lists/listinfo/springframework-developer=0D=0A=0A=0A********** =
L'ADSL A 20 EUR/MOIS**********=0ATiscali propose l'ADSL le moins cher du =
march=E9 : 20 EUR/mois et le modem ADSL offert ! =0APour profiter de cett=
e offre exceptionnelle, cliquez ici : http://register.tiscali.fr/adsl/=0A=
Offre soumise =E0 conditions.=0A

RE: [Springframework-developer] Example classes needed

[Alef A. \(JTeam\) <al...@jt...>]

Colin, you kind of have a point there...

So we basically need to investigate how many people manage dependencies
automatically and how many do it manually and then decide... ;-)

Anyway, I think the version number needs to be in there... (I'm managing
dependencies using a maven-like structure ;-)

Alef


-----Oorspronkelijk bericht-----
Van: spr...@li...
[mailto:spr...@li...] Namens
Colin Sampaleanu
Verzonden: Thursday, August 28, 2003 3:33 PM
Aan: j=FCrgen h=F6ller [werk3AT]
CC: spr...@li...
Onderwerp: Re: [Springframework-developer] Example classes needed


Well in this case, I think the best choice is probably something like=20
spring-full.jar for this version, then something like=20
spring2-full.jar/spring-full2.jar for the next version which breaks api=20
compatibility, etc. This works on the assumption that people are=20
manually managing dependencies, and allows people to slip in new jars=20
without changing references when the api has not changed. Then for maven

usage, what would happen is that it would be uploaded to ibiblio (or=20
whatever maven repository) with the full version number, for example,=20
spring-full-1.0.1.jar. The maven users would specify the exact version=20
in the project files.

The alternative, to have the full version in the the name, is almost as=20
good, as the manual people can rename it to whatever they like.

But I don't like the in-between variant. It's not exact enough for maven

handling, and too exact for manual handling.

Again, when the api is no longer upwards compatible and you have=20
something like hibernate vs hibernate2, I think that needs to be=20
reflected in the name since I basically consider those different=20
apis/libs, not just different versions.

Justy my opinion :-)


j=FCrgen h=F6ller [werk3AT] wrote:

>We manage our dependencies manually here at werk3AT :-) And as far as I

>remember, no Hibernate user has complained about hibernate2.jar yet.
>
>Juergen
>
>
>-----Original Message-----
>From: Colin Sampaleanu [mailto:col...@ex...]
>Sent: Thursday, August 28, 2003 3:04 PM
>To: j=FCrgen h=F6ller [werk3AT]
>Cc: spr...@li...
>Subject: Re: [Springframework-developer] Example classes needed
>
>
>To throw some water into the fire, :-), I prefer the exact name when
>using Maven, since I can enforce what I am getting, but when managing=20
>dependencies manually, I prefer not to have a version in the name
except=20
>when it is something like a major version number which indicates a=20
>different api; then I can slip a new version in as needed without=20
>changing all references.
>
>j=FCrgen h=F6ller [werk3AT] wrote:
>
> =20
>
>>Hmmm, not much response yet... I still tend to prefer
>>"spring-full-1.0.jar", for easy drop-in. IMO, a jar file does not need

>>to reflect the exact detail version. I consider it fine enough if it=20
>>indicates the major version. See servlet.jar, hibernate2.jar. Can we=20
>>please decide on this until *tomorrow*? :-)
>>=20
>>Juergen
>>=20
>>=20
>>
>>    -----Original Message-----
>>    *From:* j=FCrgen h=F6ller [werk3AT]
>>    *Sent:* Monday, August 25, 2003 11:50 PM
>>    *To:* Lars Fischer;
spr...@li...
>>    *Cc:* tri...@tr...
>>    *Subject:* Re: [Springframework-developer] Example classes needed
>>
>>    Let's vote on this. I don't mind either naming strategy for jar
>>    files. Anybody else prefering the spring-full-1.0m1 style?
>>    =20
>>    BTW, Hibernate uses hibernate2.jar for its whole 2.x tree. Log4J
>>    uses log4j-1.2.8.jar for the specific version. 2 examples for
>>    opposite ends, I guess.
>>    =20
>>    Juergen
>>    =20
>>    =20
>>
>>        -----Urspr=FCngliche Nachricht-----
>>        *Von:* Lars Fischer [mailto:lar...@gm...]
>>        *Gesendet:* Mo 25.08.2003 23:18
>>        *An:* spr...@li...
>>        *Cc:* j=FCrgen h=F6ller [werk3AT]; tri...@tr...
>>        *Betreff:* Re: [Springframework-developer] Example classes=20
>> needed
>>
>>        I agree with Thomas, I once made a mistake because I didn't
>>        realize
>>        that I was using an older version. The jar-files should be
>>        named after
>>        the version.
>>
>>        > Juergen,
>>        >
>>        > The drawback then is that you can't tell from the jar file
>>        if it is M1, M2
>>        > or
>>        > the release jar.
>>        >
>>        > Thomas
>>        >
>>        > > It's gonna be "spring-framework-1.0m1" and
>>        "spring-full-1.0.jar", if we
>>        > stick
>>        > > to the current plan. We've used the same naming strategy
>>        for 0.9.x, e.g.
>>        > > "spring-framework-0.9.1" but still "spring-full-0.9.jar".
>>        I prefer that
>>        > way
>>        > > to ease drop-in replacement in the literal sense :-) The
build
>>        > properties
>>        > > reflect this in "spring-version=3D1.0" and
>>        "spring-version-detail=3D1.0m1".
>>        > >=20
>>        > > Juergen
>>        > >=20
>>        > >=20
>>        > >
>>        > >     -----Urspr=C3=BCngliche Nachricht-----
>>        > >     Von: tri...@tr... [mailto:tri...@tr...]
>>        > >     Gesendet: Mo 25.08.2003 19:21
>>        > >     An: j=C3=BCrgen h=C3=B6ller [werk3AT]
>>        > >     Cc: Lars Fischer;
>>        spr...@li...
>>        > >     Betreff: RE: [Springframework-developer] Example
>>        classes needed
>>        > >   =20
>>        > >   =20
>>        > >
>>        > >     Juergen,
>>        > >   =20
>>        > >     > Anyway, ContextLoaderServlet *will* be in 1.0 M1, to
>>        be released at
>>        > the
>>        > > end
>>        > >     > of this week if there aren't any major obstacles.
>>        BTW, can everybody
>>        > > please
>>        > >     > test the current CVS contents against own
applications?
>>        > >     >
>>        > >   =20
>>        > >     I am updating the Step-by-step-MVC document - what
>>        will the exact name
>>        > of
>>        > > the
>>        > >     directory and the jar file be?  I'm assuming
>>        'spring-framework-1.0M1'
>>        > and
>>        > >     'spring-full-1.0M1.jar'.
>>        > >   =20
>>        > >     Thomas
>>        > >   =20
>>        > >
>>        > >
>>        >
>>        >
>>        >
>>
>>   =20
>>
>
>
> =20
>




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

RE: [Springframework-developer] XMLBeanFactory

[<jue...@we...>]

Andreas,

That's a very good idea: I've just included it and generally refined the =
bean factory exception messages on the occasion :-)

Juergen


-----Original Message-----
From: Andreas Rudolf [mailto:an...@mu...]
Sent: Thursday, August 28, 2003 1:54 PM
To: spr...@li...
Subject: [Springframework-developer] XMLBeanFactory


Hi J=FCrgen,

is it possible to add one more catch in the =
loadBeanDefinitions(InputStream=20
is) method?

Currently it just throw SAXException, but then you can't see the =
errorline in=20
the message.
Will be better to add    =20

catch (SAXParseException ex)=20
{
	throw new BeanDefinitionStoreException("XML document is invalid: Line: =
" +=20
ex.getLineNumber(), ex);     =20
}   =20

before the catch(SAXParseException ex).

What do you think?

Best regards
		Andy



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] Example classes needed

[Colin S. <col...@ex...>]

Well in this case, I think the best choice is probably something like 
spring-full.jar for this version, then something like 
spring2-full.jar/spring-full2.jar for the next version which breaks api 
compatibility, etc. This works on the assumption that people are 
manually managing dependencies, and allows people to slip in new jars 
without changing references when the api has not changed. Then for maven 
usage, what would happen is that it would be uploaded to ibiblio (or 
whatever maven repository) with the full version number, for example, 
spring-full-1.0.1.jar. The maven users would specify the exact version 
in the project files.

The alternative, to have the full version in the the name, is almost as 
good, as the manual people can rename it to whatever they like.

But I don't like the in-between variant. It's not exact enough for maven 
handling, and too exact for manual handling.

Again, when the api is no longer upwards compatible and you have 
something like hibernate vs hibernate2, I think that needs to be 
reflected in the name since I basically consider those different 
apis/libs, not just different versions.

Justy my opinion :-)


jürgen höller [werk3AT] wrote:

>We manage our dependencies manually here at werk3AT :-) And as far as I remember, no Hibernate user has complained about hibernate2.jar yet.
>
>Juergen
>
>
>-----Original Message-----
>From: Colin Sampaleanu [mailto:col...@ex...]
>Sent: Thursday, August 28, 2003 3:04 PM
>To: jürgen höller [werk3AT]
>Cc: spr...@li...
>Subject: Re: [Springframework-developer] Example classes needed
>
>
>To throw some water into the fire, :-), I prefer the exact name when 
>using Maven, since I can enforce what I am getting, but when managing 
>dependencies manually, I prefer not to have a version in the name except 
>when it is something like a major version number which indicates a 
>different api; then I can slip a new version in as needed without 
>changing all references.
>
>jürgen höller [werk3AT] wrote:
>
>  
>
>>Hmmm, not much response yet... I still tend to prefer 
>>"spring-full-1.0.jar", for easy drop-in. IMO, a jar file does not need 
>>to reflect the exact detail version. I consider it fine enough if it 
>>indicates the major version. See servlet.jar, hibernate2.jar. Can we 
>>please decide on this until *tomorrow*? :-)
>> 
>>Juergen
>> 
>> 
>>
>>    -----Original Message-----
>>    *From:* jürgen höller [werk3AT]
>>    *Sent:* Monday, August 25, 2003 11:50 PM
>>    *To:* Lars Fischer; spr...@li...
>>    *Cc:* tri...@tr...
>>    *Subject:* Re: [Springframework-developer] Example classes needed
>>
>>    Let's vote on this. I don't mind either naming strategy for jar
>>    files. Anybody else prefering the spring-full-1.0m1 style?
>>     
>>    BTW, Hibernate uses hibernate2.jar for its whole 2.x tree. Log4J
>>    uses log4j-1.2.8.jar for the specific version. 2 examples for
>>    opposite ends, I guess.
>>     
>>    Juergen
>>     
>>     
>>
>>        -----Ursprüngliche Nachricht-----
>>        *Von:* Lars Fischer [mailto:lar...@gm...]
>>        *Gesendet:* Mo 25.08.2003 23:18
>>        *An:* spr...@li...
>>        *Cc:* jürgen höller [werk3AT]; tri...@tr...
>>        *Betreff:* Re: [Springframework-developer] Example classes needed
>>
>>        I agree with Thomas, I once made a mistake because I didn't
>>        realize
>>        that I was using an older version. The jar-files should be
>>        named after
>>        the version.
>>
>>        > Juergen,
>>        >
>>        > The drawback then is that you can't tell from the jar file
>>        if it is M1, M2
>>        > or
>>        > the release jar.
>>        >
>>        > Thomas
>>        >
>>        > > It's gonna be "spring-framework-1.0m1" and
>>        "spring-full-1.0.jar", if we
>>        > stick
>>        > > to the current plan. We've used the same naming strategy
>>        for 0.9.x, e.g.
>>        > > "spring-framework-0.9.1" but still "spring-full-0.9.jar".
>>        I prefer that
>>        > way
>>        > > to ease drop-in replacement in the literal sense :-) The build
>>        > properties
>>        > > reflect this in "spring-version=1.0" and
>>        "spring-version-detail=1.0m1".
>>        > > 
>>        > > Juergen
>>        > > 
>>        > > 
>>        > >
>>        > >     -----Ursprüngliche Nachricht-----
>>        > >     Von: tri...@tr... [mailto:tri...@tr...]
>>        > >     Gesendet: Mo 25.08.2003 19:21
>>        > >     An: jürgen höller [werk3AT]
>>        > >     Cc: Lars Fischer;
>>        spr...@li...
>>        > >     Betreff: RE: [Springframework-developer] Example
>>        classes needed
>>        > >    
>>        > >    
>>        > >
>>        > >     Juergen,
>>        > >    
>>        > >     > Anyway, ContextLoaderServlet *will* be in 1.0 M1, to
>>        be released at
>>        > the
>>        > > end
>>        > >     > of this week if there aren't any major obstacles.
>>        BTW, can everybody
>>        > > please
>>        > >     > test the current CVS contents against own applications?
>>        > >     >
>>        > >    
>>        > >     I am updating the Step-by-step-MVC document - what
>>        will the exact name
>>        > of
>>        > > the
>>        > >     directory and the jar file be?  I'm assuming
>>        'spring-framework-1.0M1'
>>        > and
>>        > >     'spring-full-1.0M1.jar'.
>>        > >    
>>        > >     Thomas
>>        > >    
>>        > >
>>        > >
>>        >
>>        >
>>        >
>>
>>    
>>
>
>
>  
>

[Springframework-developer] XMLBeanFactory

[Andreas R. <an...@mu...>]

Hi J=FCrgen,

is it possible to add one more catch in the loadBeanDefinitions(InputStream=
=20
is) method?

Currently it just throw SAXException, but then you can't see the errorline =
in=20
the message.
Will be better to add    =20

catch (SAXParseException ex)=20
{
	throw new BeanDefinitionStoreException("XML document is invalid: Line: " +=
=20
ex.getLineNumber(), ex);     =20
}   =20

before the catch(SAXParseException ex).

What do you think?

Best regards
		Andy

RE: [Springframework-developer] Example classes needed

[Alef A. \(JTeam\) <al...@jt...>]

+1 for spring-full-1.0.jar=20
=20

-----Oorspronkelijk bericht-----
Van: spr...@li...
[mailto:spr...@li...] Namens
Kopylenko, Dmitry
Verzonden: Thursday, August 28, 2003 2:56 PM
Aan: 'j=FCrgen h=F6ller [werk3AT]';
'spr...@li...'
CC: 'tri...@tr...'; 'rod...@in...'
Onderwerp: RE: [Springframework-developer] Example classes needed


+1 for spring-full-1.0.jar

-----Original Message-----
From: j=FCrgen h=F6ller [werk3AT] [mailto:jue...@we...]=20
Sent: Thursday, August 28, 2003 8:53 AM
To: spr...@li...
Cc: tri...@tr...; rod...@in...
Subject: RE: [Springframework-developer] Example classes needed


Hmmm, not much response yet... I still tend to prefer
"spring-full-1.0.jar", for easy drop-in. IMO, a jar file does not need
to reflect the exact detail version. I consider it fine enough if it
indicates the major version. See servlet.jar, hibernate2.jar. Can we
please decide on this until *tomorrow*? :-)
=20
Juergen
=20
=20

-----Original Message-----
From: j=FCrgen h=F6ller [werk3AT]=20
Sent: Monday, August 25, 2003 11:50 PM
To: Lars Fischer; spr...@li...
Cc: tri...@tr...
Subject: Re: [Springframework-developer] Example classes needed


Let's vote on this. I don't mind either naming strategy for jar files.
Anybody else prefering the spring-full-1.0m1 style?
=20
BTW, Hibernate uses hibernate2.jar for its whole 2.x tree. Log4J uses
log4j-1.2.8.jar for the specific version. 2 examples for opposite ends,
I guess.
=20
Juergen
=20
=20

-----Urspr=FCngliche Nachricht-----=20
Von: Lars Fischer [mailto:lar...@gm...]=20
Gesendet: Mo 25.08.2003 23:18=20
An: spr...@li...=20
Cc: j=FCrgen h=F6ller [werk3AT]; tri...@tr...=20
Betreff: Re: [Springframework-developer] Example classes needed



I agree with Thomas, I once made a mistake because I didn't realize
that I was using an older version. The jar-files should be named after
the version.

> Juergen,
>
> The drawback then is that you can't tell from the jar file if it is
M1, M2
> or
> the release jar.
>
> Thomas
>
> > It's gonna be "spring-framework-1.0m1" and "spring-full-1.0.jar", if
we
> stick
> > to the current plan. We've used the same naming strategy for 0.9.x,
e.g.
> > "spring-framework-0.9.1" but still "spring-full-0.9.jar". I prefer
that
> way
> > to ease drop-in replacement in the literal sense :-) The build
> properties
> > reflect this in "spring-version=3D1.0" and
"spring-version-detail=3D1.0m1".
> >=20
> > Juergen
> >=20
> >=20
> >
> >     -----Urspr=C3=BCngliche Nachricht-----
> >     Von: tri...@tr... [mailto:tri...@tr...]
> >     Gesendet: Mo 25.08.2003 19:21
> >     An: j=C3=BCrgen h=C3=B6ller [werk3AT]
> >     Cc: Lars Fischer;
spr...@li...
> >     Betreff: RE: [Springframework-developer] Example classes needed
> >   =20
> >   =20
> >
> >     Juergen,
> >   =20
> >     > Anyway, ContextLoaderServlet *will* be in 1.0 M1, to be
released at
> the
> > end
> >     > of this week if there aren't any major obstacles. BTW, can
everybody
> > please
> >     > test the current CVS contents against own applications?
> >     >
> >   =20
> >     I am updating the Step-by-step-MVC document - what will the
exact name
> of
> > the
> >     directory and the jar file be?  I'm assuming
'spring-framework-1.0M1'
> and
> >     'spring-full-1.0M1.jar'.
> >   =20
> >     Thomas
> >   =20
> >
> >
>
>
>

RE: [Springframework-developer] Example classes needed

[<jue...@we...>]

V2UgbWFuYWdlIG91ciBkZXBlbmRlbmNpZXMgbWFudWFsbHkgaGVyZSBhdCB3ZXJrM0FUIDotKSBB
bmQgYXMgZmFyIGFzIEkgcmVtZW1iZXIsIG5vIEhpYmVybmF0ZSB1c2VyIGhhcyBjb21wbGFpbmVk
IGFib3V0IGhpYmVybmF0ZTIuamFyIHlldC4NCg0KSnVlcmdlbg0KDQoNCi0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQpGcm9tOiBDb2xpbiBTYW1wYWxlYW51IFttYWlsdG86Y29saW5tbDFAZXhp
cy5jb21dDQpTZW50OiBUaHVyc2RheSwgQXVndXN0IDI4LCAyMDAzIDM6MDQgUE0NClRvOiBqw7xy
Z2VuIGjDtmxsZXIgW3dlcmszQVRdDQpDYzogc3ByaW5nZnJhbWV3b3JrLWRldmVsb3BlckBsaXN0
cy5zb3VyY2Vmb3JnZS5uZXQNClN1YmplY3Q6IFJlOiBbU3ByaW5nZnJhbWV3b3JrLWRldmVsb3Bl
cl0gRXhhbXBsZSBjbGFzc2VzIG5lZWRlZA0KDQoNClRvIHRocm93IHNvbWUgd2F0ZXIgaW50byB0
aGUgZmlyZSwgOi0pLCBJIHByZWZlciB0aGUgZXhhY3QgbmFtZSB3aGVuIA0KdXNpbmcgTWF2ZW4s
IHNpbmNlIEkgY2FuIGVuZm9yY2Ugd2hhdCBJIGFtIGdldHRpbmcsIGJ1dCB3aGVuIG1hbmFnaW5n
IA0KZGVwZW5kZW5jaWVzIG1hbnVhbGx5LCBJIHByZWZlciBub3QgdG8gaGF2ZSBhIHZlcnNpb24g
aW4gdGhlIG5hbWUgZXhjZXB0IA0Kd2hlbiBpdCBpcyBzb21ldGhpbmcgbGlrZSBhIG1ham9yIHZl
cnNpb24gbnVtYmVyIHdoaWNoIGluZGljYXRlcyBhIA0KZGlmZmVyZW50IGFwaTsgdGhlbiBJIGNh
biBzbGlwIGEgbmV3IHZlcnNpb24gaW4gYXMgbmVlZGVkIHdpdGhvdXQgDQpjaGFuZ2luZyBhbGwg
cmVmZXJlbmNlcy4NCg0KasO8cmdlbiBow7ZsbGVyIFt3ZXJrM0FUXSB3cm90ZToNCg0KPiBIbW1t
LCBub3QgbXVjaCByZXNwb25zZSB5ZXQuLi4gSSBzdGlsbCB0ZW5kIHRvIHByZWZlciANCj4gInNw
cmluZy1mdWxsLTEuMC5qYXIiLCBmb3IgZWFzeSBkcm9wLWluLiBJTU8sIGEgamFyIGZpbGUgZG9l
cyBub3QgbmVlZCANCj4gdG8gcmVmbGVjdCB0aGUgZXhhY3QgZGV0YWlsIHZlcnNpb24uIEkgY29u
c2lkZXIgaXQgZmluZSBlbm91Z2ggaWYgaXQgDQo+IGluZGljYXRlcyB0aGUgbWFqb3IgdmVyc2lv
bi4gU2VlIHNlcnZsZXQuamFyLCBoaWJlcm5hdGUyLmphci4gQ2FuIHdlIA0KPiBwbGVhc2UgZGVj
aWRlIG9uIHRoaXMgdW50aWwgKnRvbW9ycm93Kj8gOi0pDQo+ICANCj4gSnVlcmdlbg0KPiAgDQo+
ICANCj4NCj4gICAgIC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ICAgICAqRnJvbToqIGrD
vHJnZW4gaMO2bGxlciBbd2VyazNBVF0NCj4gICAgICpTZW50OiogTW9uZGF5LCBBdWd1c3QgMjUs
IDIwMDMgMTE6NTAgUE0NCj4gICAgICpUbzoqIExhcnMgRmlzY2hlcjsgc3ByaW5nZnJhbWV3b3Jr
LWRldmVsb3BlckBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCj4gICAgICpDYzoqIHRyaXNiZXJnQHRy
aWRiLmNvbQ0KPiAgICAgKlN1YmplY3Q6KiBSZTogW1NwcmluZ2ZyYW1ld29yay1kZXZlbG9wZXJd
IEV4YW1wbGUgY2xhc3NlcyBuZWVkZWQNCj4NCj4gICAgIExldCdzIHZvdGUgb24gdGhpcy4gSSBk
b24ndCBtaW5kIGVpdGhlciBuYW1pbmcgc3RyYXRlZ3kgZm9yIGphcg0KPiAgICAgZmlsZXMuIEFu
eWJvZHkgZWxzZSBwcmVmZXJpbmcgdGhlIHNwcmluZy1mdWxsLTEuMG0xIHN0eWxlPw0KPiAgICAg
IA0KPiAgICAgQlRXLCBIaWJlcm5hdGUgdXNlcyBoaWJlcm5hdGUyLmphciBmb3IgaXRzIHdob2xl
IDIueCB0cmVlLiBMb2c0Sg0KPiAgICAgdXNlcyBsb2c0ai0xLjIuOC5qYXIgZm9yIHRoZSBzcGVj
aWZpYyB2ZXJzaW9uLiAyIGV4YW1wbGVzIGZvcg0KPiAgICAgb3Bwb3NpdGUgZW5kcywgSSBndWVz
cy4NCj4gICAgICANCj4gICAgIEp1ZXJnZW4NCj4gICAgICANCj4gICAgICANCj4NCj4gICAgICAg
ICAtLS0tLVVyc3Byw7xuZ2xpY2hlIE5hY2hyaWNodC0tLS0tDQo+ICAgICAgICAgKlZvbjoqIExh
cnMgRmlzY2hlciBbbWFpbHRvOmxhcnMuZmlzY2hlckBnbXhwcm8ubmV0XQ0KPiAgICAgICAgICpH
ZXNlbmRldDoqIE1vIDI1LjA4LjIwMDMgMjM6MTgNCj4gICAgICAgICAqQW46KiBzcHJpbmdmcmFt
ZXdvcmstZGV2ZWxvcGVyQGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KPiAgICAgICAgICpDYzoqIGrD
vHJnZW4gaMO2bGxlciBbd2VyazNBVF07IHRyaXNiZXJnQHRyaWRiLmNvbQ0KPiAgICAgICAgICpC
ZXRyZWZmOiogUmU6IFtTcHJpbmdmcmFtZXdvcmstZGV2ZWxvcGVyXSBFeGFtcGxlIGNsYXNzZXMg
bmVlZGVkDQo+DQo+ICAgICAgICAgSSBhZ3JlZSB3aXRoIFRob21hcywgSSBvbmNlIG1hZGUgYSBt
aXN0YWtlIGJlY2F1c2UgSSBkaWRuJ3QNCj4gICAgICAgICByZWFsaXplDQo+ICAgICAgICAgdGhh
dCBJIHdhcyB1c2luZyBhbiBvbGRlciB2ZXJzaW9uLiBUaGUgamFyLWZpbGVzIHNob3VsZCBiZQ0K
PiAgICAgICAgIG5hbWVkIGFmdGVyDQo+ICAgICAgICAgdGhlIHZlcnNpb24uDQo+DQo+ICAgICAg
ICAgPiBKdWVyZ2VuLA0KPiAgICAgICAgID4NCj4gICAgICAgICA+IFRoZSBkcmF3YmFjayB0aGVu
IGlzIHRoYXQgeW91IGNhbid0IHRlbGwgZnJvbSB0aGUgamFyIGZpbGUNCj4gICAgICAgICBpZiBp
dCBpcyBNMSwgTTINCj4gICAgICAgICA+IG9yDQo+ICAgICAgICAgPiB0aGUgcmVsZWFzZSBqYXIu
DQo+ICAgICAgICAgPg0KPiAgICAgICAgID4gVGhvbWFzDQo+ICAgICAgICAgPg0KPiAgICAgICAg
ID4gPiBJdCdzIGdvbm5hIGJlICJzcHJpbmctZnJhbWV3b3JrLTEuMG0xIiBhbmQNCj4gICAgICAg
ICAic3ByaW5nLWZ1bGwtMS4wLmphciIsIGlmIHdlDQo+ICAgICAgICAgPiBzdGljaw0KPiAgICAg
ICAgID4gPiB0byB0aGUgY3VycmVudCBwbGFuLiBXZSd2ZSB1c2VkIHRoZSBzYW1lIG5hbWluZyBz
dHJhdGVneQ0KPiAgICAgICAgIGZvciAwLjkueCwgZS5nLg0KPiAgICAgICAgID4gPiAic3ByaW5n
LWZyYW1ld29yay0wLjkuMSIgYnV0IHN0aWxsICJzcHJpbmctZnVsbC0wLjkuamFyIi4NCj4gICAg
ICAgICBJIHByZWZlciB0aGF0DQo+ICAgICAgICAgPiB3YXkNCj4gICAgICAgICA+ID4gdG8gZWFz
ZSBkcm9wLWluIHJlcGxhY2VtZW50IGluIHRoZSBsaXRlcmFsIHNlbnNlIDotKSBUaGUgYnVpbGQN
Cj4gICAgICAgICA+IHByb3BlcnRpZXMNCj4gICAgICAgICA+ID4gcmVmbGVjdCB0aGlzIGluICJz
cHJpbmctdmVyc2lvbj0xLjAiIGFuZA0KPiAgICAgICAgICJzcHJpbmctdmVyc2lvbi1kZXRhaWw9
MS4wbTEiLg0KPiAgICAgICAgID4gPiANCj4gICAgICAgICA+ID4gSnVlcmdlbg0KPiAgICAgICAg
ID4gPiANCj4gICAgICAgICA+ID4gDQo+ICAgICAgICAgPiA+DQo+ICAgICAgICAgPiA+ICAgICAt
LS0tLVVyc3Byw4PCvG5nbGljaGUgTmFjaHJpY2h0LS0tLS0NCj4gICAgICAgICA+ID4gICAgIFZv
bjogdHJpc2JlcmdAdHJpZGIuY29tIFttYWlsdG86dHJpc2JlcmdAdHJpZGIuY29tXQ0KPiAgICAg
ICAgID4gPiAgICAgR2VzZW5kZXQ6IE1vIDI1LjA4LjIwMDMgMTk6MjENCj4gICAgICAgICA+ID4g
ICAgIEFuOiBqw4PCvHJnZW4gaMODwrZsbGVyIFt3ZXJrM0FUXQ0KPiAgICAgICAgID4gPiAgICAg
Q2M6IExhcnMgRmlzY2hlcjsNCj4gICAgICAgICBzcHJpbmdmcmFtZXdvcmstZGV2ZWxvcGVyQGxp
c3RzLnNvdXJjZWZvcmdlLm5ldA0KPiAgICAgICAgID4gPiAgICAgQmV0cmVmZjogUkU6IFtTcHJp
bmdmcmFtZXdvcmstZGV2ZWxvcGVyXSBFeGFtcGxlDQo+ICAgICAgICAgY2xhc3NlcyBuZWVkZWQN
Cj4gICAgICAgICA+ID4gICAgDQo+ICAgICAgICAgPiA+ICAgIA0KPiAgICAgICAgID4gPg0KPiAg
ICAgICAgID4gPiAgICAgSnVlcmdlbiwNCj4gICAgICAgICA+ID4gICAgDQo+ICAgICAgICAgPiA+
ICAgICA+IEFueXdheSwgQ29udGV4dExvYWRlclNlcnZsZXQgKndpbGwqIGJlIGluIDEuMCBNMSwg
dG8NCj4gICAgICAgICBiZSByZWxlYXNlZCBhdA0KPiAgICAgICAgID4gdGhlDQo+ICAgICAgICAg
PiA+IGVuZA0KPiAgICAgICAgID4gPiAgICAgPiBvZiB0aGlzIHdlZWsgaWYgdGhlcmUgYXJlbid0
IGFueSBtYWpvciBvYnN0YWNsZXMuDQo+ICAgICAgICAgQlRXLCBjYW4gZXZlcnlib2R5DQo+ICAg
ICAgICAgPiA+IHBsZWFzZQ0KPiAgICAgICAgID4gPiAgICAgPiB0ZXN0IHRoZSBjdXJyZW50IENW
UyBjb250ZW50cyBhZ2FpbnN0IG93biBhcHBsaWNhdGlvbnM/DQo+ICAgICAgICAgPiA+ICAgICA+
DQo+ICAgICAgICAgPiA+ICAgIA0KPiAgICAgICAgID4gPiAgICAgSSBhbSB1cGRhdGluZyB0aGUg
U3RlcC1ieS1zdGVwLU1WQyBkb2N1bWVudCAtIHdoYXQNCj4gICAgICAgICB3aWxsIHRoZSBleGFj
dCBuYW1lDQo+ICAgICAgICAgPiBvZg0KPiAgICAgICAgID4gPiB0aGUNCj4gICAgICAgICA+ID4g
ICAgIGRpcmVjdG9yeSBhbmQgdGhlIGphciBmaWxlIGJlPyAgSSdtIGFzc3VtaW5nDQo+ICAgICAg
ICAgJ3NwcmluZy1mcmFtZXdvcmstMS4wTTEnDQo+ICAgICAgICAgPiBhbmQNCj4gICAgICAgICA+
ID4gICAgICdzcHJpbmctZnVsbC0xLjBNMS5qYXInLg0KPiAgICAgICAgID4gPiAgICANCj4gICAg
ICAgICA+ID4gICAgIFRob21hcw0KPiAgICAgICAgID4gPiAgICANCj4gICAgICAgICA+ID4NCj4g
ICAgICAgICA+ID4NCj4gICAgICAgICA+DQo+ICAgICAgICAgPg0KPiAgICAgICAgID4NCj4NCg0K
DQo=

Re: [Springframework-developer] Example classes needed

[Colin S. <col...@ex...>]

To throw some water into the fire, :-), I prefer the exact name when 
using Maven, since I can enforce what I am getting, but when managing 
dependencies manually, I prefer not to have a version in the name except 
when it is something like a major version number which indicates a 
different api; then I can slip a new version in as needed without 
changing all references.

jürgen höller [werk3AT] wrote:

> Hmmm, not much response yet... I still tend to prefer 
> "spring-full-1.0.jar", for easy drop-in. IMO, a jar file does not need 
> to reflect the exact detail version. I consider it fine enough if it 
> indicates the major version. See servlet.jar, hibernate2.jar. Can we 
> please decide on this until *tomorrow*? :-)
>  
> Juergen
>  
>  
>
>     -----Original Message-----
>     *From:* jürgen höller [werk3AT]
>     *Sent:* Monday, August 25, 2003 11:50 PM
>     *To:* Lars Fischer; spr...@li...
>     *Cc:* tri...@tr...
>     *Subject:* Re: [Springframework-developer] Example classes needed
>
>     Let's vote on this. I don't mind either naming strategy for jar
>     files. Anybody else prefering the spring-full-1.0m1 style?
>      
>     BTW, Hibernate uses hibernate2.jar for its whole 2.x tree. Log4J
>     uses log4j-1.2.8.jar for the specific version. 2 examples for
>     opposite ends, I guess.
>      
>     Juergen
>      
>      
>
>         -----Ursprüngliche Nachricht-----
>         *Von:* Lars Fischer [mailto:lar...@gm...]
>         *Gesendet:* Mo 25.08.2003 23:18
>         *An:* spr...@li...
>         *Cc:* jürgen höller [werk3AT]; tri...@tr...
>         *Betreff:* Re: [Springframework-developer] Example classes needed
>
>         I agree with Thomas, I once made a mistake because I didn't
>         realize
>         that I was using an older version. The jar-files should be
>         named after
>         the version.
>
>         > Juergen,
>         >
>         > The drawback then is that you can't tell from the jar file
>         if it is M1, M2
>         > or
>         > the release jar.
>         >
>         > Thomas
>         >
>         > > It's gonna be "spring-framework-1.0m1" and
>         "spring-full-1.0.jar", if we
>         > stick
>         > > to the current plan. We've used the same naming strategy
>         for 0.9.x, e.g.
>         > > "spring-framework-0.9.1" but still "spring-full-0.9.jar".
>         I prefer that
>         > way
>         > > to ease drop-in replacement in the literal sense :-) The build
>         > properties
>         > > reflect this in "spring-version=1.0" and
>         "spring-version-detail=1.0m1".
>         > > 
>         > > Juergen
>         > > 
>         > > 
>         > >
>         > >     -----Ursprüngliche Nachricht-----
>         > >     Von: tri...@tr... [mailto:tri...@tr...]
>         > >     Gesendet: Mo 25.08.2003 19:21
>         > >     An: jürgen höller [werk3AT]
>         > >     Cc: Lars Fischer;
>         spr...@li...
>         > >     Betreff: RE: [Springframework-developer] Example
>         classes needed
>         > >    
>         > >    
>         > >
>         > >     Juergen,
>         > >    
>         > >     > Anyway, ContextLoaderServlet *will* be in 1.0 M1, to
>         be released at
>         > the
>         > > end
>         > >     > of this week if there aren't any major obstacles.
>         BTW, can everybody
>         > > please
>         > >     > test the current CVS contents against own applications?
>         > >     >
>         > >    
>         > >     I am updating the Step-by-step-MVC document - what
>         will the exact name
>         > of
>         > > the
>         > >     directory and the jar file be?  I'm assuming
>         'spring-framework-1.0M1'
>         > and
>         > >     'spring-full-1.0M1.jar'.
>         > >    
>         > >     Thomas
>         > >    
>         > >
>         > >
>         >
>         >
>         >
>