• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Bug with frameworks as jar and bundless build
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug with frameworks as jar and bundless build

  • Subject: Re: Bug with frameworks as jar and bundless build
  • From: Alexis Tual <email@hidden>
  • Date: Wed, 23 Jan 2013 17:25:58 +0100
Hi Mike and Henrique,

Henrique, by bundle less build I mean no creation of "build" folder by the incremental builder. NSProjectBundleEnabled false or true doesn't change the behavior in my case.
Mike, you mean it's fixed now on 6.0.0 and it hasn't been commited back to 5.x branche(s) ?

Thanks

Alex

2013/1/23 Mike Schrag <email@hidden>
Yeah, I'm pretty sure that wasn't fixed until later, and other dependent APIs diverged enough that it became difficult to continue pushing updates.

On Jan 23, 2013, at 9:29 AM, Henrique Prange <email@hidden> wrote:

Hi Alexis,

By bundleless build you mean running the application with the NSProjectBundleEnabled property active? I don't think Wonder is capable of handling jar frameworks in this mode yet.

Cheers,

Henrique

On 23/01/2013, at 11:47, Alexis Tual <email@hidden> wrote:

Hi list,

I try to develop with jar frameworks only (even system frameworks). That works fine when generate bundles but not at all with bundless build.
I get this error on startup : 

[2013-1-23 14:17:49 CET] <main> Initialized : er.extensions.ERXExtensions
[2013-1-23 14:17:50 CET] <main> A fatal exception occurred: null
[2013-1-23 14:17:50 CET] <main> java.lang.ExceptionInInitializerError
at com.webobjects.appserver.WOResourceManager.__getJavaWebObjectsResourceAsStream(WOResourceManager.java:116)
at com.webobjects.appserver._private.WOProperties.initUserDefaultsKeys(WOProperties.java:317)
at com.webobjects.appserver.WOApplication._initWOApp(WOApplication.java:5743)
at com.webobjects.appserver.WOApplication.<init>(WOApplication.java:779)
at er.extensions.appserver.ajax.ERXAjaxApplication.<init>(ERXAjaxApplication.java:24)
at er.extensions.appserver.ERXApplication.<init>(ERXApplication.java:1094)
at org.cocktail.fwkcktlwebapp.server.CktlWebApplication.<init>(CktlWebApplication.java:124)
at org.cocktail.fwkcktlajaxwebext.serveur.CocktailAjaxApplication.<init>(CocktailAjaxApplication.java:39)
at org.cocktail.coriandre.serveur.Application.<init>(Application.java:138)
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:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at com.webobjects.appserver.WOApplication.main(WOApplication.java:547)
at er.extensions.appserver.ERXApplication.main(ERXApplication.java:826)
at org.cocktail.coriandre.serveur.Application.main(Application.java:134)
Caused by: java.lang.IllegalStateException: Main bundle 'Properties' file can't be read.  Did you run as a Java Application instead of a WOApplication in WOLips?
Please post your deployment configuration in the Wonder mailing list.
at er.extensions.appserver.ERXApplication$Loader.collectMainProps(ERXApplication.java:745)
at er.extensions.appserver.ERXApplication$Loader.bundleDidLoad(ERXApplication.java:642)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.webobjects.foundation.NSSelector._safeInvokeMethod(NSSelector.java:122)
at com.webobjects.foundation.NSNotificationCenter$_Entry.invokeMethod(NSNotificationCenter.java:588)
at com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:532)
at com.webobjects.foundation.NSNotificationCenter.postNotification(NSNotificationCenter.java:562)
at com.webobjects.foundation.NSBundle.postNotification(NSBundle.java:2546)
at com.webobjects.foundation.NSBundle.LoadBundlesFromJars(NSBundle.java:735)
at com.webobjects.foundation.NSBundle.<clinit>(NSBundle.java:345)
... 18 more

Wonder version : 5.5.0 (same thing with 5.8.2)
I also put ERFoundation in the classpath before everything else. It looks like WO can't find the main bundle name with this setup...
Has anybody stumble across this one ? I've seen a similar message from Andrew a while ago…

Thanks for your help

-- 
Alexis Tual
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)

This email sent to email@hidden

_______________________________________________
Do not post admin requests to the list. They will be ignored.

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
  • Follow-Ups:
    • Re: Bug with frameworks as jar and bundless build
      • From: Mike Schrag <email@hidden>
References: 
 >Bug with frameworks as jar and bundless build (From: Alexis Tual <email@hidden>)
 >Re: Bug with frameworks as jar and bundless build (From: Henrique Prange <email@hidden>)
 >Re: Bug with frameworks as jar and bundless build (From: Mike Schrag <email@hidden>)

  • Prev by Date: Re: Kill User Session On Browser Closed
  • Next by Date: Re: Bug with frameworks as jar and bundless build
  • Previous by thread: Re: Bug with frameworks as jar and bundless build
  • Next by thread: Re: Bug with frameworks as jar and bundless build
  • Index(es):
    • Date
    • Thread