Ah, I'd totally forgotten about that one. Yeah, overall the WOApplication launcher just feels like "one more thing that can break".
> On 8 Nov 2025, at 17:53, Ricardo Parada <[email protected]> wrote: > > The reason I started using the Java application launcher is that Eclipse > seemed to misbehave when I used the WOApplication launcher. For example when > I clicked on a frame in the stack trace when debugging it would display tha > source code in a read only java viewer that would not let me set breakpoints > nor edit the code. So something was off. > > I will try that patch too. > > Thank you Hugi > > > >> >> On Nov 8, 2025, at 12:18 PM, Hugi Thordarson <[email protected]> wrote: >> >> Glad to be of help Ricardo :). >> >> I always run my applications as plain Java applications, not using the >> WOApplication launcher, since the WOApplication launcher can generate a >> broken classpath when using maven, which can cause some really fun problems: >> >> https://github.com/wocommunity/wolips/issues/153 >> >> I mentioned the old nature just for completeness — it shouldn't matter in >> your case, but only when doing bundleless development (which you can't do >> anyway with maven in the current Project Wonder). >> >> https://github.com/wocommunity/wonder/issues/1029 >> >> The exception you're seeing is just a pretty general indicator that for some >> reason, ERXApplication$Loader can't locate or construct a main bundle. The >> reasons for that can be various (one of which is trying to run a Wonder >> application in bundleless mode). >> >> Cheers, >> - hugi >> >> >>> On 8 Nov 2025, at 16:57, Ricardo Parada <[email protected]> wrote: >>> >>> Thanks a million, Hugi, you just saved me many hours of debugging in >>> NSBundle and ERXApplication which is a bit awkward in NSBundle because the >>> decompiled line numbers and the line numbers on the left side do not match. >>> >>> I had a chance to try the Java application launch with your suggestions: >>> >>> 1. Set the working directory for the Debug/Run configuration to >>> ${working_dir_loc_WOLips:MyApp} and >>> 2. Pass in the VM argument -DNSProjectBundleEnabled=true >>> >>> And it worked!!!! >>> >>> >>> Also the exception you mention in >>> https://github.com/wocommunity/wonder/issues/1025 >>> >>> is the same exact exception I was getting. Is this fix for the bundle less >>> that you were referring to? >>> >>> As for the nature “ <nature>org.maven.ide.eclipse.maven2Nature</nature>” I >>> removed it because I thought that was the old one and that I only needed >>> the new one, e.g <nature>org.eclipse.m2e.core.maven2Nature</nature> >>> >>> I have to go now but I will check everything else you mention and give your >>> fix a try. >>> >>> Thank you very very much, >>> Ricardo Parada >>> >>> >>> >>> >>> >>>> >>>> On Nov 8, 2025, at 3:03 AM, Hugi Thordarson <[email protected]> wrote: >>>> - Does your ".project" file contain >>>> <nature>org.maven.ide.eclipse.maven2Nature</nature> — and a WOLips builder? >>>> - Does your application project contain a "build" folder on disk? (should >>>> be getting generated by WOLips). And does it look pretty much like an >>>> application bundle or do you see something missing? >>>> - Does woproject/resources.include.patternset properly define your >>>> resources? (kind of pointless to ask since your build works with maven so >>>> it should be fine — but can't hurt to ask) >>>> >>>> Launching as a WOApplication should work if you have "generate bundles" >>>> enabled. But if you launch as a "java application" (not a WOApplication), >>>> you will see the error you described unless you: >>>> 1. Set the working directory for the Debug/Run configuration to >>>> ${working_dir_loc_WOLips:SW} and >>>> 2. Pass in the VM argument -DNSProjectBundleEnabled=true >>>> >>>> -- >>>> >>>> "Generate bundles" does pretty much what it says on the tin. It activates >>>> the WOLips builder, which generates that "build" folder in the root of >>>> your project, containing a bundle that WOLips will constantly keep "built" >>>> as you make changes. Your WO application will then locate everything from >>>> there. >>>> >>>> The nicer alternative is bundleless development, meaning no generated >>>> build-folder/bundles and resources get located directly in the project >>>> rather than from the fake bundle in the "build" folder. >>>> >>>> Bundleles is faster, simpler and better. But there's a bug in project >>>> Wonder which prevents you from using bundleless with it when using maven ( >>>> https://github.com/wocommunity/wonder/issues/1025 ). >>>> It's fixed by one of the patches I submitted yesterday, those patches >>>> exactly being meant to ease life for those migrating to maven (everyone >>>> hits these problems in the first steps, and I think we should really fix >>>> those). >>>> >>>> Cheers, >>>> - hugi >>>> >>>> >>>> >>>> >>>>> On 8 Nov 2025, at 04:27, Ricardo Parada <[email protected]> wrote: >>>>> Hi Hugi, >>>>> Yes that checkbox is selected. >>>>> Do you know what the checkbox is supposed to do exactly? I just want to >>>>> check the right things are happening. >>>>> By the way, the flattening of Resources you suggested fixed the other >>>>> problem I was having. >>>>> Thanks >>>>> Ricardo Parada >>>>>> On Nov 7, 2025, at 6:50 PM, Hugi Thordarson <[email protected]> wrote: >>>>>> Have you activated "Generate bundles" in Eclipse Preferences -> WOLips >>>>>> -> Build? >>>>>> - hugi >>>>>>> On 7 Nov 2025, at 23:45, Ricardo Parada via Webobjects-dev >>>>>>> <[email protected]> wrote: >>>>>>> Hello everyone >>>>>>> I got all my frameworks and one of my apps building correctly with >>>>>>> maven. They have a fluffy bunny layout but everything’s is being built >>>>>>> correctly and the application runs fine from the command line. >>>>>>> However, when I run it with Debug as WOApplication or as Java >>>>>>> application it gets a NullPointerException and it seems like it does >>>>>>> not know what the main bundle is. >>>>>>> If it rings a bell please let me know. >>>>>>> The funny thing is that I had it running a couple of days ago and today >>>>>>> I decided to setup everything from scratch to document what other >>>>>>> developers will have to do to setup their development environment for >>>>>>> maven and now I can’t get it to launch from Eclipse. >>>>>>> Let me know if you have any ideas. >>>>>>> Thank you >>>>>>> Ricardo Parada >>
