Re: Regarding the "localhostips" property in deployment

2025-05-05 Thread Maik Musall via Webobjects-dev
Hi, I can see this being set in an older installation here, but in many cases I don’t even have an /etc/WebObjects directory, and I don’t recall ever setting this property by hand. We do have complex setups with apache on different hosts than wotaskd, but it is sufficient to set the IP address

JavaXML.framework and Java 21 (and Eclipse)

2025-05-05 Thread Paul Hoadley via Webobjects-dev
Hello, I'm porting a project to Java 21. It makes some use of packages in the java.xml module, e.g. org.w3c.dom. When I switch java.version to 21, Eclipse complains:  [In case the image is dropped: The package org.w3c.dom is accessible from more than one module: , java.xml] That's fair enoug

Re: Regarding the "localhostips" property in deployment

2025-05-05 Thread Paul Hoadley via Webobjects-dev
On 5 May 2025, at 16:38, Hugi Thordarson via Webobjects-dev wrote: > quick question: When setting up a deployment environment you usually have to > set the property er.extensions.WOHostUtilities.localhostips (usually in > /etc/WebObjects/Properties) to ensure your applications accept incoming

Regarding the "localhostips" property in deployment

2025-05-05 Thread Hugi Thordarson via Webobjects-dev
Hi all, quick question: When setting up a deployment environment you usually have to set the property er.extensions.WOHostUtilities.localhostips (usually in /etc/WebObjects/Properties) to ensure your applications accept incoming admin requests from wotaskd. This feels a little redundant, so I'v