All the good things Records bring are stifled by JPA and DAO conventions and requirements. I really hate JPA for that reason, and have avoided Hibernate in favor of my own DAO implementations.
Records will slash thousands of lines of code from my implementation and will make it infinitely easier to maintain, and trust down-stream.
With some of my smaller clients, the CIO is the same as the CTO and the same as the IT Director. There, IT is developers, too.
Enterprise will cause a boom in hiring VBA devs to migrate legacy apps to other programming languages, then hear Microsoft will extend support for a few more years, then fire all those VBA devs again. If Microsoft had some wits, they'd create easy tools to migrate VBA to C#.
Wouldn't it face the exact same security issues as VBA, with drive-by installs of obfuscated malware and executions of arbitrary code?
Sure! I wrote all about it over on Medium: https://medium.com/@aev_software/java-jakarta-soap-wsdl-client-fails-to-read-soap-message-for-logging-38087a63ea6d
To summarize: custom logging handlers failed after upgrading to version 3, because the underlying implementation that exports a message as a SOAP message is broken.
That indeed is annoying.
Oh dear. That would work. But I'd lose the paper!
Except that b comes before c, so it'll always recommend the .blog bookmark before the .com bookmark. This post is more about clarifying a stupefying situation. Solutions are a bonus.
Dinosaur here. I started building web sites when JavaScript had yet to be invented. If articles like this exist for new features introduced since EcmaScript 5, I'm all ears.
Cool. Just what I need: yet another version of a JDK/JRE to test. I feel like I spend more time testing these for regressions than I spend developing functionality for my clients. Anyway. Good for Adoptium and those who found and solved this bug.
I started using Jakarta half a year ago, as it was promised to be the de-facto way to build a SOAP client that speaks to a WSDL server. Oh boy: growing pains. Did not expect that 2 decades of developer experience in Java EE would amount to nothing, for the people who implemented Jakarta. As impressive as the effort may be, the inexplicable regressions we faced when we got forced to upgrade to version 3 proved quite cumbersome.
The Post? Really? Half of that article is an ad for the Post itself!