6 ms·
Probably true, but I can confirm that this relationship does not go both ways :). Absolutely hated going from WO to Java EE back in the day. But I understand it
by hugi 2y ago
Probably true, but I can confirm that this relationship does not go both ways :). Absolutely hated going from WO to Java EE back in the day. But I understand it's gotten better in recent years though.
- pjmlp 2y agoTrue enough that it has its own Wikipedia page, https://en.m.wikipedia.org/wiki/Distributed_Objects_Everywhere https://en.m.wikipedia.org/wiki/Distributed_Objects_Everywhe... The Java WO Java EE compatibility, https://en.m.wikipedia.org/wiki/WebObjects https://en.m.wikipedia.org/wiki/WebObjects And docs, https://developer.apple.com/library/archive/documentation/LegacyTechnologies/WebObjects/WebObjects_5/WebObjectsRef/Java/JavaWebObjects.pdf https://developer.apple.com/library/archive/documentation/Le...
- hugi 2y agoYeah, I've deployed a few WO apps in Java EE environments. How that works is WO will basically use a servlet (adaptor) for request handing, which will bridge calls and convert them from the Java EE APIs to the WO specific APIs. You don't actually interact with the Java EE APIs much (or at all). I just meant that going from WO to Java EE didn't feel very nice :).
- pjmlp 2y agoI see, thanks.