Okay, I seem to be going round and round here, and I'm left a bit
confused, perhaps I can get some help clarifying this in my head.
I've been going around fixing library paths and getting everything
working, and now that all my build problems have gone away... I'm
back with the same error with the bundle that I had before.
[2007-07-18 11:31:12 PDT] <main> A fatal exception occurred: null
[2007-07-18 11:31:12 PDT] <main> java.lang.ExceptionInInitializerError
at
com.webobjects.appserver._private.WOProperties.initUserDefaultsKeys
(WOProperties.java:187)
at com.webobjects.appserver.WOApplication._initWOApp
(WOApplication.java:5081)
at com.webobjects.appserver.WOApplication.<init>(WOApplication.java:
551)
at org.nmc.pachyderm.authoring.Application.<init>(Application.java:76)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance
(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance
(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at com.webobjects.appserver.WOApplication.main(WOApplication.java:323)
at org.nmc.pachyderm.authoring.Application.main(Application.java:62)
Caused by: java.lang.IllegalStateException:
<com.webobjects.foundation.NSBundle> warning: There is already a
unique instance for Bundle named 'PXFoundation'. Use
NSBundle.bundleForName(PXFoundation) to access it:
<com.webobjects.foundation.NSBundle name:'PXFoundation' bundlePath:'/
Users/jarcher/Development/pachyderm/branches/2.1.x/Frameworks/
PXFoundation/build/PXFoundation.framework'
packages:'("org.nmc.pachyderm.foundation",
"org.nmc.pachyderm.document.file", "com.webobjects.foundation",
"org.nmc.pachyderm.foundation.metadata")' 102 classes >
at com.webobjects.foundation.NSBundle.CreateBundleWithPath
(NSBundle.java:825)
at
com.webobjects.foundation.NSBundle._bundleWithPathShouldCreateIsJar
(NSBundle.java:487)
at com.webobjects.foundation.NSBundle.LoadBundlesFromClassPath
(NSBundle.java:742)
at com.webobjects.foundation.NSBundle.<clinit>(NSBundle.java:365)
... 12 more
Exactly where should I include dependent frameworks in a project's
build path, and where should i not have them included?
(Sorry, I'm trying to get this, but as soon as I think I have it, I
don't)
Thanks, I'm trying. Seriously.
Joshua
On Jul 18, 2007, at 10:26 AM, Mike Schrag wrote:
> Doh .. Guilty as charged. I've been burned on the Wonder mailing
> list before also :)
>
> On Jul 18, 2007, at 12:07 PM, Ulrich Köster wrote:
>
>> Looks like someone has to read the docs ;-)
>>
>> uli
>>
>>
>> Am 18.07.2007 um 14:12 schrieb Mike Schrag:
>>
>>> Holy crap ... Denis and Lachlan, you have just rocked my world
>>> view. You're 100% correct, and I stand corrected :)
>>>
>>> Chuck -- They're totally right. In wolips.jdt plugin, there's an
>>> UpdateFrameworkIncludeFiles that runs any time .classpath
>>> changes. When this happens, the plugin goes through and looks
>>> for project dependencies that are WOLips projects and that are
>>> Frameworks, and automatically adds entries in
>>> ant.frameworks.wo.wolocalroot for Libraries/Frameworks/
>>> ThatOtherProject. 1) I have no idea how I never noticed this
>>> before, and 2) I want the years of my life back that were spent
>>> in the "WebObjects Frameworks" dialog. This code has existed
>>> since at least 2004.
>>>
>>> ms
>>>
>>> On Jul 17, 2007, at 7:38 PM, Chuck Hill wrote:
>>>
>>>>
>>>> On Jul 17, 2007, at 4:31 PM, Lachlan Deck wrote:
>>>>
>>>>> On 18/07/2007, at 9:25 AM, Lachlan Deck wrote:
>>>>>
>>>>>> On 18/07/2007, at 8:40 AM, Chuck Hill wrote:
>>>>>>
>>>>>>> On Jul 17, 2007, at 3:36 PM, Joshua Archer wrote:
>>>>>>>
>>>>>>>> I had added the jar to the build path in the 'Libraries'
>>>>>>>> tab, and the framework to the "required projects on the
>>>>>>>> build path" under Projects. I've removed them from the
>>>>>>>> latter, and things are moving along differently now...
>>>>>>>
>>>>>>> Um, no. You should check / select the framework in the
>>>>>>> WebObjects Frameworks library and add the project in Eclipse
>>>>>>> to Required Projects.
>>>>>>
>>>>>> Actually Chuck - you do one or the other; not both. They both
>>>>>> have the same effect (in terms of the classpath) at runtime.
>>>>>
>>>>> Sorry... I should clarify that by saying that it is not
>>>>> required to check/select the framework in the WebObjects
>>>>> Frameworks Library if you've added the framework as a project
>>>>> dependency. i.e., you can do both but checking it in the
>>>>> WebObjects Frameworks Library is optional.
>>>>
>>>> What happens when you deploy? How does the classpath to the
>>>> installed framework get generated?
>>>>
>>>>
>>>> Chuck
>>>>
>>>> --
>>>>
>>>> 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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
>
------------------------------------------------------------------------
-----
Joshua Archer
Software Engineer, CSU - Center for Distributed Learning
Phone: 707.664.2085, Fax: 707.664.4350
------------------------------------------------------------------------
-----
This archive was generated by hypermail 2.0.0 : Wed Jul 18 2007 - 14:44:06 EDT