This has come up before but I've never been able to see it happen myself so am still in the dark as to the cause.
Does anything happen in your app just before this error shows up? Has jetty re-deployed your context? Are you running with caching enabled or disabled? Are you running with something else that might use javassist, like jboss or similar? Any additional information you can provide would be greatly appreciated. I'd really like to find and fix whatever the problem is so it'll be given top priority if any additional info can be had. On Wed, Jan 30, 2008 at 1:47 PM, Marcel Schepers <[EMAIL PROTECTED]> wrote: > Hello, > > Tapestry (or more likely Javassist) generated scary error messages, such as > 'compile error: no such class: $StampCatalogue_23'. StampCatalogue is an > abstract Tapestry page. In case these messages show up, Jetty has to be > restarted in order to restore from this chaos. > > I am using Tapestry version 4.1.3 (from the Maven repository). > > Any ideas what might cause this? > > Marcel > -- Jesse Kuhnert Tapestry / OGNL / Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
