Re: die terrible error message (Unable to find framework named "YourApplicationName")
Re: die terrible error message (Unable to find framework named "YourApplicationName")
- Subject: Re: die terrible error message (Unable to find framework named "YourApplicationName")
- From: David Avendasora <email@hidden>
- Date: Tue, 15 Jan 2008 09:52:56 -0500
SOLVED.
I'm posting this here for the Future Me (as is the tradition of this
thread) that is dumb enough to cause this like Present Me.
Okay, my resources.exlude.patternset and resources.include.patternset
had gotten completely hosed. I'm not sure if I caused it with all my
"Include this, exclude that" that I was doing, or if I just simply
went in and messed around where I shouldn't have. I grabbed new
patternset files from another project that was working and now
everything is working again and no more Unable to find framework
named "YourApplicationName" error!
All the previous suggestions didn't help because even though the
project was structured properly, the patternsets were missing entries
or in direct conflict with each other, so things were missing from
the Resources directory (like my components, duh!).
What is important is the contents of the "Resources" and
"WebResources" directories in the build folder, not what there
contents are in the project. They _should_ match up, but in my case
they didn't, and simply selecting "Include as Resource" didn't put
the little "R" on the file, because it was already in both the
include and exclude patternsets.
Dave
On Jan 14, 2008, at 3:35 PM, David Avendasora wrote:
Okay, So I rolled the new Ant Builder back in, and I'm now getting
the error again. Grrrr..
I've rolled it back, and killed the build directory, emptied the
trash, deleted the project (without deleting the files) and
reimported it, restarted Eclipse and danced a spirit dance to the
WO gods, and nothing. I'm still getting this error.
More suggestions?
Dave
On Jan 14, 2008, at 2:56 PM, David Avendasora wrote:
You know, with Xcode that would have been the first thing I would
have done...
I did clean a bunch of times, but it took actually deleting the
build file through Eclipse to fix it.
Thanks!
Dave
On Jan 14, 2008, at 2:39 PM, Mike Schrag wrote:
when in doubt, delete the "build" folder in your projects and
force a clean build ...
On Jan 14, 2008, at 2:33 PM, David Avendasora wrote:
Oh, and I'm running Eclipse Version: 3.2.2, WOLips 2.0.0.4118
Dave
On Jan 14, 2008, at 1:48 PM, David Avendasora wrote:
Okay all you "Future Yous" out there, I'm getting this error
and I can't seem to get it to go away.
I have not modified the components at all since they were
automatically generated way-back-when by Xcode during the
project setup. This has been working fine for days, and all I
did was try to add a new builder to the project for some client-
side class shuffling around which worked just fine, then the
error started. I've since backed that change out, but no luck,
still failing with this "terrible error".
Suggestions?
Dave
On Nov 9, 2007, at 8:04 AM, Kieran Kelleher wrote:
Had this same nasty error last night on an app that had
WOComponents in the java source dir. Funny thing it has been
that way for years and suddenly after a project delete and
clean svn checkout, that error showed up. Basically looking in
the build folder shows that no components are being included
in there by the automatic builder even though the resource
include/exclude patternset clearly had the same **/*.wo that
it always had!
Moving the WOComponents our to a dir in project root showed
the automatic builder to immediately include then in the build
and problem gone.
Anyway, just writing this so Future Me never forgets this
either .... and for some reason I could not find this message
by Mike in the dev archives but fortunately it was in my local
"lists" Mailbox.
It is indeed a useless exception.
Kieran
(WO 5.3.3/Tiger)
On Sep 27, 2007, at 8:44 PM, Mike Schrag wrote:
I'm preserving this here for all time so Future Me doesn't
get as annoyed as Present Me.
If you ever get:
java.lang.IllegalStateException: Unable to find framework
named "<TheNameOfYourApp>".
at
com.webobjects.appserver._private.WOComponentDefinition.<init>
(WOComponentDefinition.java:179)
at
com.webobjects.appserver.WOApplication._componentDefinitionFromC
lassNamed(WOApplication.java:2353)
at
com.webobjects.appserver.WOApplication._componentDefinition
(WOApplication.java:2448)
at com.webobjects.appserver.WOComponent._componentDefinition
(WOComponent.java:475)
at com.webobjects.appserver.WOComponent.<init>
(WOComponent.java:233)
You have done one of the following:
1) return new NextPage(context) instead of pageWithName
("NextPage") (or pageWithName(NextPage.class.getName()) )
or 2) you have put your .wo folder in a naughty place -- the
case we ran into was accidentally creating a component INSIDE
another component (note to self -- make wolips consider this
an error). I think this can also happen if you put a
component in a java source package by accident.
This goes on my list of top useless exceptions in WO :)
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-
email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
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:
email@hidden
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:
@avendasora.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:
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:
40avendasora.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:
40avendasora.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