On Sep 21, 2010, at 7:37 PM, Q wrote: > > On 22/09/2010, at 9:02 AM, David Avendasora wrote: > >>> On Sep 21, 2010, at 6:24 PM, Mike Schrag wrote: >>> >>>> i would maybe run with verbose classloading on, and you might be able to >>>> see what class was attempting to load when this failed ... i would also >>>> print out your classpath. obviously' you're mixing and matching frameworks >>>> along the line ... like maybe your app is linked against old wonder but >>>> you link to a framework that is linked against new wonder? >> >> I have custom install location for WO just for this project. It contains >> only WO (Installed with the WOInstaller.jar) and some pre-compiled >> WOFrameworks listed below. There are no Wonder (or other) framework projects >> in my workspace at all. Just this one app. > > One of your precompiled frameworks is almost certainly the cause. Unzip them > and grep for the offending ERXValidationException class.
I decompiled them and found nothing. Of course that's not what you said, you said to GREP them. I did that and sure enough, one is referencing the new package structure, so these are not the versions of the binary frameworks I thought they were. $ grep er.extensions.validation.ERXValidationException ERJavaMail.class Binary file ERJavaMail.class matches So, in the end Chuck was right. I AM an idiot. :-) Dave _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
