I've been in a big crunch mode here, including working most of the
weekend, so have not tested Spring functionality not related to my main
app. However, for my main app, the new code from Wed/Thurs has been
running with no problems (this includes multi-context use, AOP for
transaction and Hibernate session wrapping, Hibernate OR support code,
and small amounts of JDBC code, against Oracle).
Some time later tonight I'll pull down any changes, and give that ago,
also adding in the new Hibernate 2.12...
Darren Davison wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On Wednesday 04 February 2004 19:11, jürgen höller [werk3AT] wrote:
>
>
>
>>I'd like to encourage everybody to test the current CVS head thoroughly.
>>I will test our sample apps myself too, against HSQLDB and MySQL, but I'm
>>primarily talking of custom applications here. Please report any
>>remaining issues promptly; I intend to release RC1 this weekend.
>>
>>
>
>I've run a couple of apps this weekend without any issues on tomcat5 -
>they're lightweight web apps, one with JDBC access to MySQL and one with
>hibernate. Both seem fine through normal usage.
>
>Using the autobuilds' modified jpetstore app, I tested on resin2, resin3,
>tomcat4, tomcat5, jboss3/tomcat (all using hsqldb) with no problems. Jetty
>4.2.17 standalone failed as usual due to not reading the tld's in the jar
>files.
>
>Just for the hell of it, I ran all of the above tests on Sun JDK 1.4.1,
>Blackdown JDK 1.3.1 and Blackdown JDK 1.4.1.
>
>Fairly meaningless, but interesting nonetheless, the average time taken by
>each app server for the 'testPurchase' test case over 5 runs each on my
>machine (with the Sun JDK) is below.
>
>resin2: 10s
>resin3: 30s
>tomcat4: 25s
>tomcat5: 12s
>jboss3/tomcat: 36s (gotta love those JBoss guys)
>
>(testPurchase involves browsing the items, adding to cart, changing the
>order, logging in incorrectly, logging in correctly, changing user
>registration details, completing the purchase and checking the database
>tables for sane numbers)
>
>
|
