This problem has gone away. One of those mysterious problems that
just goes away after doing several things seemingly unrelated.
Things that I've done since my last try are restart eclipse (actually
the whole machine, a MacBook), changed from using Wonder Framework to
the checked out project and back to the framework.
My guess is that it was related to the 'known race condition on
project creation' and that if I had originally closed the project and
opened it it might have solved the problem.
-- Jonathan
On Mar 30, 2007, at 2:12 PM, Chuck Hill wrote:
>
> On Mar 30, 2007, at 11:01 AM, Jonathan Ricker wrote:
>
>>
>>>>
>>>> Yes. launching from Eclipse.
>>>>
>>>> Here is the stack trace of the exception:
>>>>
>>>> java.lang.IllegalStateException: Unable to find framework named
>>>> "NetSoftware".
>>>> at
>>>> com.webobjects.appserver._private.WOComponentDefinition.<init>
>>>> (WOComponentDefinition.java:179)
>>>> at
>>>> com.webobjects.appserver.WOApplication._componentDefinitionFromClas
>>>> sNamed(WOApplication.java:2353)
>>>> at com.webobjects.appserver.WOApplication._componentDefinition
>>>> (WOApplication.java:2448)
>>>> at com.webobjects.appserver.WOApplication.pageWithName
>>>> (WOApplication.java:1943)
>>>>
>>>
>>> That is an odd one, I don't think I have seen that before.
>>> NetSoftware is the app name? Look in the launcher under the
>>> Arguments tab, what is the working directory set to? It should
>>> be something like ${workspace_loc: NetSoftware/build/
>>> NetSoftware.woa}
>>
>>
>> Yes, NetSoftware is the app name. Working directory as pictured
>> below.
>>
>> <workingDirectory.jpg>
>>
>> I tried the default as well (which is the same as the one on the
>> older development machine that works just fine) but it doesn't
>> makes a difference.
>>
>> When I build the app with the build.xml file I can run it from the
>> command line ( with wocaching )and it works fine.
>
> Which means that your Launcher config in Eclipse is wrong. That
> working directory looks really weird. Is that a WOApplication
> launcher or a Java Application Launcher? The latter, as Mike said,
> will not work.
>
> Chuck
>
>
>>
>> I'm going to try one of our other applications to see if I get the
>> same problem.
>>
>>
>>
>>>
>>>> at
>>>> com.webobjects.appserver._private.WOComponentRequestHandler._dispat
>>>> chWithPreparedSession(WOComponentRequestHandler.java:273)
>>>> at
>>>> com.webobjects.appserver._private.WOComponentRequestHandler._dispat
>>>> chWithPreparedApplication(WOComponentRequestHandler.java:322)
>>>> at
>>>> com.webobjects.appserver._private.WOComponentRequestHandler._handle
>>>> Request(WOComponentRequestHandler.java:358)
>>>> at
>>>> com.webobjects.appserver._private.WOComponentRequestHandler.handleR
>>>> equest(WOComponentRequestHandler.java:435)
>>>> at com.webobjects.appserver.WOApplication.dispatchRequest
>>>> (WOApplication.java:1306)
>>>> at er.extensions.ERXApplication.dispatchRequest
>>>> (ERXApplication.java:1105)
>>>> at ita.wo.ITAERXApplication.dispatchRequest
>>>> (ITAERXApplication.java:425)
>>>> at Application.dispatchRequest(Application.java:204)
>>>> at com.webobjects.appserver._private.WOWorkerThread.runOnce
>>>> (WOWorkerThread.java:173)
>>>> at com.webobjects.appserver._private.WOWorkerThread.run
>>>> (WOWorkerThread.java:254)
>>>> at java.lang.Thread.run(Thread.java:613)
>>
>
> --
>
> 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
>
>
>
>
>
This archive was generated by hypermail 2.0.0 : Mon Apr 02 2007 - 10:52:54 EDT