BTW, Is everyone contributing some dollars (or yen, or even Zlotych) A few years ago I put in monies to Maik and I have tried to get him to send me an invoice so I can put more money there.
I am happy to do this again!!!!! Theodore Petrosky | IT/Finance Director 917 371-6080 AgencySacks On 2/4/26, 8:34 PM, "Hugi Thordarson" <[email protected] <mailto:[email protected]>> wrote: Heh, duh… Yeah, there's a whole slew of problems with WO on newer JDKs, I sometimes really do sound like I fell on my head or something. In my mind I was thinking if there were problems without pre-existing workarounds — but you're tackling these at the root level which is great. Cheers, - hugi > On 4 Feb 2026, at 22:54, Ramsey Gurley <[email protected] > <mailto:[email protected]>> wrote: > > You're so modest. You've enumerated many of them over the years. Like how we > can't even compile with Java 25 without re-implementing NSTimeZone because > Java finally dumped that sun.security.action thing. Or how JavaXML just needs > to die. > > The repackaging does this. It updates NSTimeZone. It entirely removes the > WOWebService stuff built on ancient Apache Axis 1.x. All the split package > patchwork found in Wonder gets rolled into the new modular jars directly. No > more dancing around classpath ordering with ERAttributeExtension. You'll just > get Wonder's EOAttribute directly in the modular EOAccess jar... and so on. > > On 2/5/26 12:17 AM, Hugi Thordarson wrote: >> Great work Ramsey, didn't know there were problems with Wonder on JDK 25.
