I saw the following notification in my tomcat log after a tomcat:redeploy SEVERE: The web application [/instihire] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. Oct 14, 2011 12:02:30 PM org.apache.catalina.startup.HostConfig checkResources INFO: Undeploying context [/instihire]
To be sure it was beta-21, I completely removed the app from webapps, did a tomcat:deploy followed by a tomcat:redeploy. The same error was logged. Hope this helps. Tony On Oct 14, 2011, at 10:35 AM, Wechsung, Wulf wrote: > Awesome, thanks! Learning something new every day :) > > > -----Original Message----- > From: Steve Eynon [mailto:steve.ey...@alienfactory.co.uk] > Sent: Freitag, 14. Oktober 2011 14:18 > To: Tapestry users > Subject: Re: An Appeal To Use the Latest Betas > > For point 3, try viewing the new PageCatalog page. > > e.g. http://localhost:8080/PageCatalog > > There's a button there to load all pages. > > Steve. > > On 14 October 2011 19:47, Wechsung, Wulf <wulf.wechs...@sap.com> wrote: >> I've taken 5 minutes to try out the beta with my integration test project >> and besides noticing that chenillekit doesn't declare its dependency on >> tapestry as "provided" which leads to an IncompatibleClassChangeError I >> found the beta-21 to be much stricter about the location of non-managed >> classes. In 5.2.6 you could still have an interface in the components >> package (now yields plastics error java.lang.ClassFormatError: Illegal field >> modifiers in class 0x12) or an enum in the mixin package ( gave an error >> stating that is should be moved to the base package). I also noticed the new >> event handler verification. All in all, I think these are acceptable changes >> if they find their way in the user docs. >> >> I also think it would be great if tapestry came repacked with a web-app >> validation suite that >> >> 1) attempts to realize all registered services >> 2) checks all classes in the "managed" package for the class format and >> tapestry-required visibility >> 3) checks templates of all pages and components known to tapestry >> >> Framework errors are a great way to let the developer know that he isn't >> making any sense or in the case of event handlers that he probably made an >> error in the functional implementation. However, webapps are usually >> user-facing and it's a little bit embarrassing to have the webapp barf all >> over the user just because an empty event handler isn't attached to a form >> or because an interface isn't in the "correct" package. Giving the developer >> a tool to avoid this before deployment would be a great way for the >> framework cto enhance productivity by essentially prepackaging a crash and >> burn test. >> >> >> -----Original Message----- >> From: Howard Lewis Ship [mailto:hls...@gmail.com] >> Sent: Freitag, 14. Oktober 2011 01:16 >> To: Tapestry users >> Subject: An Appeal To Use the Latest Betas >> >> If you've been following the discussions here and elsewhere, you may >> be aware that Tapestry 5.3 is nearly done, with big improvements to >> every aspect of Tapestry, including speed and memory utilization. Our >> goal is to deliver an upgrade that is as seamless as possible. >> >> The PMC would dearly like to get a final release out and available >> before December (that is, within one year of the release 5.2). >> >> However, we can't do it without YOU: We need people actively using >> Tapestry to upgrade to the latest betas (5.3-beta-20 is the latest, >> but we're releasing new updates almost every day). We are looking for >> broken features or problems upgrading ... all the things that will get >> in the way of a release candidate and then a final release. >> >> Your feedback is essential ... without are community, we don't know >> for sure that Tapestry is ready to go to the next stage. Please >> budget some time, as soon as possible, to run you application under >> 5.3 and report back here about any problems you find. Without accurate >> (and hopefully, positive) feedback, we will not be able to progress to >> a final release ... and that means we'll be delayed adding the next >> layer of amazing features in Tapestry 5.4! >> >> Please see these notes on how to make use of the latest beta preview >> releases: >> >> http://tapestry.apache.org/2011/08/27/tapestry-53-beta-preview.html >> >> http://tapestryjava.blogspot.com/2011/10/tapestry-53-maven-archetype.html >> >> I've been posing on twitter each time a new preview is made available: >> >> http://twitter.com/#!/search/%23tapestry5 >> >> ... and note that by the time you do you upgreade, the exact version >> number may have changed (don't worry, beta-20 will still be available >> when beta-21 is made available). >> >> Your support is deeply appreciated ... now get back to coding less and >> delivering more! >> >> -- >> Howard M. Lewis Ship >> >> Creator of Apache Tapestry >> >> The source for Tapestry training, mentoring and support. Contact me to >> learn how I can get you up and productive in Tapestry fast! >> >> (971) 678-5210 >> http://howardlewisship.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
