Mailing List webobjects-dev@wocommunity.org Message #772
From: Theodore Petrosky <webobjects-dev@wocommunity.org>
Subject: Re: [WO-DEV] Archetypes
Date: Fri, 9 Oct 2026 17:26:00 +0000
To: WebObjects & WOnder Development <webobjects-dev@wocommunity.org>
Right, Normally, you would right click on application and choose debug. Now you simply right click on the .launch file so app.launch and select debug…  app.launch shows up in the debug and you select that.

That's where it runs it as a Java app, not as a woapplication.


Theodore Petrosky | IT/Finance Director
917 371-6080
AgencySacks
-
 

From: Ricardo Parada <webobjects-dev@wocommunity.org>
Date: Friday, October 9, 2026 at 11:36 AM
To: WebObjects & WOnder Development <webobjects-dev@wocommunity.org>
Subject: Re: [WO-DEV] Archetypes

Got it, I was just looking at that .launch file.  The project I created is called “App” and the .launch file generated is “App.launch”.  I noticed this is the one that Eclipse uses when I "Debug As Java Application”.  For example, I had to remove the compact header option and I did that in Eclipse launch configuration and when I clicked Apply it saved it back to App.launch.

I am new to modules and so I am learning it as it comes. 

I think Ramsey has done a great job in advancing development towards standard maven and JARs. Notice there is no .woa for the app and no .framework for the framework.  The app is a module (I think), it has a module-info.java and same for framework.  And the build produces a .jar for both.

Thanks
Ricardo Parada


On Oct 9, 2026, at 11:00 AM, Theodore Petrosky <webobjects-dev@wocommunity.org> wrote:

Ricardo,

The port 8080 issue is only an issue during development. I have a backup service that's running on Port 8080 so of course, if my development app started on the same port, it would conflict.

But with the dot launch file, I was able to tell the app the IP number of my workstation and change the port number so that any computer in my office could access this running app on my development machine. 

My development box has a static DHCP IP number. My IP will never change so it's very handy to tell the wonder app to start with the IP number and a better port number.

This all has to do with development not deployment.

From .launch
    <stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-DWOPort=8080"/>

Changed to:
    <stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-DWOPort=9007 -DWOHost=192.168.36.141 -DWOAdaptorURL=https://192.168.36.141/cgi-bin/WebObjects -DWOSSLEnabled=true"/>

Maybe someone else can get some more mileage out of this.

Ted


Theodore Petrosky | IT/Finance Director
917 371-6080
AgencySacks
-
 

From: Ricardo Parada <webobjects-dev@wocommunity.org>
Date: Friday, October 9, 2026 at 8:53 AM
To: WebObjects & WOnder Development <webobjects-dev@wocommunity.org>
Subject: Re: [WO-DEV] Archetypes


Hi Theodore,

I have not tried the aio yet. We currently deploy to EKS pods on AWS. They all run on port 8080.  

We don’t use wotaksd, nor wo monitor, nor Apache. We do have some pods running nginx serving static resources from the split install.

But I’m still reviewing the archetypes and what they produce. 

I built a web app from the command line with maven using the archetype for web app and I just noticed that there is no .woa? 

Anyways, looking forward to what Ramsey has to say at WOWODC. 

Thanks




On Oct 9, 2026, at 8:44 AM, Theodore Petrosky <webobjects-dev@wocommunity.org> wrote:


Did you try the All In One archetype? It creates a wonder application complete with H2 database ready to go.

Also remember that a wonder application now is going to start on Port 8080. That was my comment I left about changing the line in the .launch file.

It's the archetype called AIO

Theodore Petrosky | IT/Finance Director
917 371-6080
AgencySacks
-
 

From: Ricardo Parada <webobjects-dev@wocommunity.org>
Date: Friday, October 9, 2026 at 8:12 AM
To: WebObjects & WOnder Development <webobjects-dev@wocommunity.org>
Subject: Re: [WO-DEV] Archetypes

This is all very interesting. In further reviewing I noticed that there is no build.properties anymore. 

It now uses the FilteredResources/Info.plist. The principal classes is specified there and it can use maven properties to automatically set it along with other things. 

Thanks 
Ricardo Parada


On Oct 9, 2026, at 7:10 AM, Ricardo Parada <webobjects-dev@wocommunity.org> wrote:

Thanks for sharing that. 

Those archetypes do not seem to use wopackaging from wolifecycle-maven-plugin. It looks to me like he has gone pure maven here. 

And this would explain the problems I’m seeing in wonder8 in my project where it doesn’t find Info.plist in target/classes/… when running from Eclipse and so bundles for frameworks don’t get loaded and principal classes are not called to initialize the framework. 

I’m gonna try to model after these archetypes and I think that will clear the problems I’m seeing. 


Sent from my iPhone

On Oct 9, 2026, at 1:24 AM, Theodore Petrosky <webobjects-dev@wocommunity.org> wrote:

Ramsey,

Thank you for fixing the wonder (WO8) archetypes.

I know I can clone and install from here: git clone https://github.com/nullterminated/woarchetypes.git

The ReadMe explains that I can create from the CLI but are they available from Maven Central?

BTW, if anyone else has used these, the AIO (All In One) is really fantastic

Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster