Re: java.lang.NoClassDeffoundError: Application
Re: java.lang.NoClassDeffoundError: Application
- Subject: Re: java.lang.NoClassDeffoundError: Application
- From: Mike Schrag <email@hidden>
- Date: Wed, 25 Apr 2007 22:36:16 -0400
Sorry, i mean the project metadata files, not the workspace metadata
files. In your project are .classpath, .project, etc. Check those
to make sure they are unchanged.
On Apr 25, 2007, at 10:34 PM, Jeff Schmitz wrote:
Well, something is hosed. I just created a brand new
WonderApplication project and tried to run it as is, and I get the
same error. I looked in the workspace .metadata directory, but I
don't see any editable files in there except version.ini. I looked
at previous versions and they are like that too. Just .lock, .log
files and a .plugins directories. I guess I'll try to update
Eclipse and see what happens. Any other ideas?
Jeff
On Apr 25, 2007, at 7:01 AM, Mike Schrag wrote:
Not sure if this is your problem or not, but if you open an
Eclipse 3.2 workspace with Eclipse 3.3, it can mangle workspace
metadata. I don't think it would cause this NoClassDefFoundError,
but you never know. Another symptom is that cmd-shift-t view
doesn't work anymore.
All wolips/eclipse project files are just text files ... I would
just recommend comparing the project against your revision control
and see if any of the metadata files are different
(specifically .classpath or .project).
ms
On Apr 25, 2007, at 7:43 AM, Jeff Schmitz wrote:
That doesn't work either. I deleted all the launchers and
created a new one (under WOApplication). No parameters, main
class Application. I get the same error. My Application extends
ERXApplication if that gives any clues.
Thanks,
Jeff
On Apr 25, 2007, at 12:21 AM, Chuck Hill wrote:
While Gavin is correct for command line / JavaMonitor launches,
Eclipse does not use this file. I'd try deleting the launcher
config you are using and creating a new one.
Chuck
On Apr 24, 2007, at 9:40 PM, Gavin Eadie wrote:
At 10:59 PM -0500 4/24/07, Jeff Schmitz wrote:
No, it's just in the default package/folder, and there's no
package statement in the file. That's how it's always been
and it always worked fine before.
... next to check would be the 'classpath.txt' file at:
*.woa/Contents/MacOS/MacOSClassPath.txt
or which path is right for your platform, and be sure it
contains lines like:
# ApplicationClass == Application
APPROOT/Resources/Java/*.jar
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40global-village.net
This email sent to email@hidden
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve
specific problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mdimension.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@mac.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden