It looks and works way better than LibreOffice Base (sorry) and it's real client-server architecture. Yes, it isn't #FLOSS, which would be too awesome.
It's still from Apple, you know. (They probably still regret they wrote this in #Java in their early naive childhood days, not doing peek capitalism.)

It's just so awesome. You lay out a database schema, import it to EOModeler, fix a few data types, set some rules (GUI! no freaking XML writing, simple syntax if you want to write) and the GUI looks exactly like you want a database app to look like.

In later times #Apple probably didn't want to accept they really reimplemented the whole (?, at least a lot of) Foundation in pure portable Java (this is not the Cocoa-Java bridge!). But they did. This is the removed doc: "The Foundation Framework". 378 pages.

https://leopard-adc.pepas.com/documentation/LegacyTechnologies/WebObjects/WebObjects_5/FoundationRef/Java/JavaFoundation.pdf

Looks like I got it running without errors from #Eclipse now. Two example frameworks, included into two example apps and clients. Server and client classes and resources both distributed correctly.
Still impressed by its beauty. Both optical as well as conceptual.

Those guys called Apple's #JavaClient their "best kept secret" in 2009. Quite understandable why.

https://www.mail-archive.com/webobjects-dev@lists.apple.com/msg28020.html

#Swing #Cocoa: It isn't suprising when you look into it. For #WebObjects #Apple not only reimplemented #Foundation in #Java (com.webobjects.foundation), they also made a #Cocoa abstraction layer that mimics layout and behaviour in #Swing (com.webobjects.eointerface.swing).

That one still works (https://fosstodon.org/@lazarus/114252747377471833), while the bridge to Cocoa has been deprecated with WebObjects 5.4 (and thus is not part of its docs anymore).

Compare https://leopard-adc.pepas.com/documentation/InternetWeb/Reference/WO542Reference/index.html to https://leopard-adc.pepas.com/documentation/WebObjects/Reference/WO53_Reference/.

I mean, it doesn't look as gorgeous on #elementaryOS, but still, it works.

Ok, it even works using JDK 17 when you add `--add-exports java.base/sun.security.action=ALL-UNNAMED` as JVM option.

It‘s just lovely how they made these #Swing apps look like #Cocoa .

Think I got it running. It is aged. But aged very well. The client of this almost 30 years old example runs quite nicely, errors only point to SQL/model setup.

Think I‘ll reread that #WebObjects Desktop Application docs. They are just delicious.

@fbartho Yes, I wrote SwiftWebUI in the week when #SwiftUI got released. Do not use it for something real, it is essentially #WebObjects converted to the SwiftUI API. I.e. it holds all state server side and each click means a new page gets generated (with URLs holding the identity of the activated element).
It really isn't suitable for real world apps. I have some ideas how one might make it more useful, but no time for that

@chris Maybe it would be OK to say that body returns a list, but even that is not really true, it might return a container.
BTW: As usual it is the same in #WebObjects, it also has the „content“ thing not as an array, but as a single type that can be a container of some form.