Hi Mike. Thanks. Next time happens, will post to bug report. The more datapoints available, the better the chance of finding and fixing this.
Currently, everything is rolling smoothly, thanks. Regards, Steve -- Java/J2EE Developer/Integrator Currently "On the Road" 214-724-7741 Platform Independance Rules. Give me a stable platform, and I will give you stable code. ----- Original Message ----- From: Michael Nash JGlobal.com Sent: 10/6/2003 7:08:03 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Keelgroup] Keel mysteriously stopped working... > Steve: > > Update on this issue: After much hair-pulling, Shash and I have figured out partly > why this happens. It has to do with the new Fortress configuration meta-data that's > done automagically by Xdoclet, as we suspected. Due to strangeness with > classloaders, that information is sometimes not digested correctly. As a partial > fix, I've added *very* detailed dump information to KeelContainer in the event the > problem occurs. So, if it happens to you again, have a look in catalina.out (or > wherever your container dumps stderr) and you'll see a full trace of whatever the > container got as far as meta information. Look for WARN or FATAL in there (as I'm > doing a certain amount of validation as part of the dump) and make sure the names > line up the way you think they should for the model that the stacktrace is > complaining about. If it is a legit config error, this makes it easy to find at > least. It's helped me catch a few subtle mistakes I made already. > > Research continues, but this should help get you rolling again. > > Regards, > > Mike > http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
