Java

1363 readers

1 users here now

For discussing Java, the JVM, languages that run on the JVM, and other related technologies.

founded 1 year ago

MODERATORS

Ategon@programming.dev

JackbyDev@programming.dev

thtroyer@programming.dev

Jakarta EE Platform 10 was released one year ago today (jakarta.ee)

submitted 1 year ago by lysdexic@programming.dev to c/java@programming.dev

3 comments fedilink hide all child comments

Here's a link to the release plan https://projects.eclipse.org/projects/ee4j.jakartaee-platform/releases/10/plan

top 3 comments

sorted by: hot top controversial new old

[–] aev@lemmy.sdf.org 3 points 1 year ago (1 children)

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.

[–] lysdexic@programming.dev 2 points 1 year ago (1 children)

Did not expect that 2 decades of developer experience in Java EE would amount to nothing, for the people who implemented Jakarta.

I'd love to hear more about specifics.

[–] aev@lemmy.sdf.org 1 points 1 year ago

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.