X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.25a (ClamAV 1.4.3/27950) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=simple/simple; d=wocommunity.org; s=mail; bh=pjRov4vGE0MSKbGUMGuR6BpLs71SZtfvvwVB/3RmfXk=; h=From:Subject:Message-ID:Date:Content-Type:MIME-Version:To:Sender:Reply-To: List-Archive:List-Unsubscribe:List-Id; b=ACzRSEZft2QWoiO1st+EUXPQLDTYmNtocRNB nHHBtGZ9KSCTp59TFNWBixKjZxEzaWC8/fb3CAWNqsTIk/zPuzoI4c/RmtqVuGZHbpRqp0N+sUmuA ZkxLuvUU8xw6vafDOfyyQILKW5Qr0AJ/afe4TWf9bD3AH5egddsMG1YqgK5K12vVLdMq71SWoGfGG oMbcIHKgyjhUVXor3D/Wvtcr1qYD48/neHir9ZHYrcuQB0fWTYMbBT22NeRklaZjeOC7EwH2y/o9v T9VugoAQ/q0xlCmjAEJ28xJ1U4Bxky0bGaHg+HGl53JBQwyls7vUXyvFJSrZwlNFHwnLTMgixUg== Return-Path: X-ListServer: CommuniGate Pro LIST 6.3.18 List-Id: List-Unsubscribe: List-Archive: Reply-To: "WebObjects & WOnder Development" Sender: "WebObjects & WOnder Development" To: "WebObjects & WOnder Development" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------NpcyveI2gXj1ynA80R2zcqAg" X-Original-Message-ID: Date: Wed, 25 Mar 2026 07:40:05 +0900 Message-ID: Subject: [WO-DEV] Re: Apache in development From: "Ramsey Gurley" This is a multi-part message in MIME format. --------------NpcyveI2gXj1ynA80R2zcqAg Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit If you're not running in direct connect, you'll need to set up Apache locally. After years of using it, I despise Apache however :) Mostly due to its weird config format.  I like to run in direct connect. I've added a vert.x woadaptor to Wonder8 to make direct connect a lot better. I still haven't worked out my strategy to fully replace apache/monitor/wotaskd in production, but it will probably be a docker container and standard kubernetes stuff. If there are any bugs with jar resource loading, I think I've fixed them in the new NSBundle. I've recently gotten an all in one WOApp to run with jlink. That is: D2W, persistent session storage, h2 embedded database, vert.x webserver, java 25, all embedded in one app. I plan to turn that into a maven archetype when I get Wonder8 released onto maven central. On 3/25/26 6:51 AM, Paul Hoadley wrote: > Hi Ted, > > On 25 Mar 2026, at 05:44, Theodore Petrosky > wrote: > >> HOWEVER, I have a D2W app that was started with the Ant paradigm. >> After learning maven and switching my app over (it is much cleaner) >> many of the images from ERModernDefaultSkin do not display in >> development. > > There is an annoying edge case with Maven frameworks and resource > loading in Eclipse. I've never investigated it too deeply, as the > workaround is simple: in your case, you need > ERModernDefaultSkin.framework as an open project in your Eclipse > workspace, and the Maven version needs to match exactly to what your > app depends on. When there's a version mismatch, it doesn't seem to be > able to load resources out of the JAR in your ~/.m2/repository. > > > -- > Paul Hoadley > https://logicsquad.net/ > https://www.linkedin.com/company/logic-squad/ > --------------NpcyveI2gXj1ynA80R2zcqAg Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

If you're not running in direct connect, you'll need to set up Apache locally. After years of using it, I despise Apache however :) Mostly due to its weird config format.  I like to run in direct connect. I've added a vert.x woadaptor to Wonder8 to make direct connect a lot better. I still haven't worked out my strategy to fully replace apache/monitor/wotaskd in production, but it will probably be a docker container and standard kubernetes stuff.

If there are any bugs with jar resource loading, I think I've fixed them in the new NSBundle. I've recently gotten an all in one WOApp to run with jlink. That is: D2W, persistent session storage, h2 embedded database, vert.x webserver, java 25, all embedded in one app. I plan to turn that into a maven archetype when I get Wonder8 released onto maven central.


On 3/25/26 6:51 AM, Paul Hoadley wrote:
Hi Ted,

On 25 Mar 2026, at 05:44, Theodore Petrosky <webobjects-dev@wocommunity.org> wrote:

HOWEVER, I have a D2W app that was started with the Ant paradigm. After learning maven and switching my app over (it is much cleaner) many of the images from ERModernDefaultSkin do not display in development.

There is an annoying edge case with Maven frameworks and resource loading in Eclipse. I've never investigated it too deeply, as the workaround is simple: in your case, you need ERModernDefaultSkin.framework as an open project in your Eclipse workspace, and the Maven version needs to match exactly to what your app depends on. When there's a version mismatch, it doesn't seem to be able to load resources out of the JAR in your ~/.m2/repository.


--------------NpcyveI2gXj1ynA80R2zcqAg--