http://blogs.webtide.com:80/jesse/ http://blogs.webtide.com:80/jesse/2008/06/25/1214410080000.html Jan and I have run across some annoying problems with test cases and test scoping within jetty recently and it has lead to some discussion on an idea that I have been kicking around for a while.&nbsp; The problem was that we have some useful test cases which are in the form of jetty server configurations in the jetty module and maybe a couple of other module, but since they are test source they are not readily available for consumption in other modules.<p><a href="http://blogs.webtide.com:80/jesse/2008/06/25/1214410080000.html">Read more...</a></p> http://blogs.webtide.com:80/jesse/2008/04/22/1208890620000.html The trunk of jetty has undergone some substantial changes over the last couple of weeks.&nbsp; In addition to jetty 7 now requiring a minimum version of jdk 1.5 and the default inclusion of the early servlet 3.0 spec, there have been a number of structural changes a bit more near and dear to my heart.&nbsp; It leverages a bit more maven2!<p><a href="http://blogs.webtide.com:80/jesse/2008/04/22/1208890620000.html">Read more...</a></p> http://blogs.webtide.com:80/jesse/2008/03/28/1206725514147.html Jetty Continuations have been addressing the problem of blocking servlet threads for a while now and the concept is under review for inclusion into the servlet 3.0 spec (due out near the end of the year I believe). With jetty 7.0 under development now one of the big new additions will be the implementation of the servlet 3.0 spec, which is handily already sitting on the trunk of jetty.<p><a href="http://blogs.webtide.com:80/jesse/2008/03/28/1206725514147.html">Read more...</a></p>