I’ll do more testing and then comment on the pull request. :-)
Thank you > > On Nov 8, 2025, at 5:58 PM, Hugi Thordarson <[email protected]> wrote: > > The project layout looks fine at first sight, so I can't think of what's > causing your application to fail in WOApplication launch/bundle-mode. > > But glad to hear that you're up and running! And that the fixes to bundleless > development work. I might just count that as a review and merge into main :). > > - hugi > > > >> On 8 Nov 2025, at 22:07, Ricardo Parada <[email protected]> wrote: >> >> I’m gonna summarize here. >> >> >>> >>>> 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? >> >> Yes, it has a build folder as shown below: >> >> % ls build >> Phynance.woa >> % ls build/Phynance.woa >> Contents >> % ls build/Phynance.woa/Contents >> Info.plist Resources WebServerResources >> >>> - 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) >> >> It is as follows: >> >> % cat woproject/resources.include.patternset >> Components/**/*.wo/**/* >> Components/**/*.api >> Resources/**/*% >> >> also In my build.properties I have classes.dir=target/classes. It used to be >> set to “bin”. Do you think it hay has any effect on this? >> >> >>> >>> 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 >>> >> >> This worked for my java launch configuration. And I think that is what I had >> when things used to work. When I started from scratch I recreated the launch >> configurations from zero and forgot I was using this. >> >> In my case I set working directory to: >> >> ${working_dir_loc_WOLips:MyApp >> >> This works!!! >> >> >>> -- >>> >>> "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). >> >> I incorporated those two commits into our fork of Wonder. >> >> We are using Wonder 7.3 which we converted a while ago to use slf4j >> throughout. That was a significant effort. >> >> And we also upgraded jar files in it that had been flagged by the security >> scanning software as having vulnerabilities. >> >> Anyways, I just added your two commits to that version and it fixes the >> problem. >> >> >>> Cheers, >>> - hugi >
