Per chi fosse interessato a #java :
#redhat regala l'ottava edizione di Java in a Nutshell.
Ed un paio di ebook su #jboss e #javabeans

https://developers.redhat.com/e-books/java-nutshell-guide

Eres old pero tan old como para haber ejecutado ahora mismo

#jboss restart

Question for #java folks.

Is there any #jboss modules expert that could tell me if there is a way to figure out the exact list of modules that are loaded when deploying and application on JBoss ?

I am fighting a linkage error that is caused by two versions of #hibernate being pulled on the classpath, and I have no clue where they are coming from.

@carlwgeorge @mattdm @mairin @nirik @adamw @major @hughsie @vrothberg Now to try to find some of those #JBoss/#Wildfly developers. I know, the #JavaEE/#JakartaEE guys are probably in a separate building 🤓

Damnation ! #JBoss #Weld est passé en version 5 (avec un renommage de javax.inject vers jakarta.inject), mais pour l'instant #Deltaspike n'a pas encore fait la migration. Est-ce qu'ils comptent faire cette migration ? Ou est-ce que c'est encore une librairie qui mourra à cause de la migration ?

Red Hat has released WildFly 27, featuring support for JDK 11, JDK 17, Jakarta EE 10, and MicroProfile 5.0. There are also dependency upgrades to Hibernate ORM 6.1, Hibernate Search 6.1, Infinispan 14, JGroups 5.2, RESTEasy 6.2, and Weld 5. WildFly 27 is a compatible implementation for Jakarta EE 10, having passed the TCKs in the Platform, Web, and Core profiles.

https://www.infoq.com/news/2022/12/wildfly-delivers-support-jdk-17/

#wildfly
#jboss
#jakartaee
#java
#java17
#javaee
#radhat

I migrated my camel integration to #quarkus running with #podman on #fedora Just a little route that lets me integrate some disparate systems for my #homeautomation. I'll miss you #wildfly but it was time. 15 years of #jboss ! This is going to make my life so much easier. #containersarelinux

Activate #infinispan second level cache with #jboss and #hibernate https://blog.voina.org/activate-infinispan-second-level-cache-with-jboss-and-hibernate/

So things are getting bad, and #cloud is being considered more complex to manage and more costly.
I have to admit that while I really believed in the cloud, the problems that my customers were facing started to break my beliefs.
Ops costs increased, because they still hired the IT guy, but now a #SiteReliabilityEngineer costs way more than a traditional #SystemAdministrator, and often he has an #infra knowledge way inferior, since everything is not in house anymore. Everything is hosted and you don't access to the technology internals anymore.
Also, they are dealing with a level of complexity unheard of.
Before the cloud there were only physical and virtualized layers of complexity.
Now we also have then #containerorchestration and #servicemesh layers.
We moved from putting a stupid #Java class in classpath to run #JBoss with the #APM profiling to running #Prometheus, #Grafana, #Jaeger and #Kiali to obtain the same level of informations.

The only good thing is that now in Linux engineers are using #eBPF to profiling network and software execution.
But this is NOT innovation at all. You could do that already with #DTrace in #Solaris and #FreeBSD with way less complexity, and the same level of profiling since #Java, #Ruby and lot of frameworks included its probes to support advanced tracing.
Apple's #macOS used to provide a good #DTrace frontend called #Instruments that was really cool to work with.

https://world.hey.com/dhh/why-we-re-leaving-the-cloud-654b47e0

Erstmal das automatische scrollen auf der Webseite deaktiviert, in der #federation rattert das ja schlimmer runter als mein #jboss im Hochbetrieb 😂

So, #IBM are buying #RedHat. Seems obvious this is about #OpenShift and #Kubernetes, and not #RHEL. If RHEL dies an IBM death it's a big opportunity for #Ubuntu and #SUSE, of course.

#k8s has enough other support to stand on its own, regardless. And there's a competitive market for OpenShift. But I'm concerned for #GlusterFS, #Ansible, and #JBoss.

#holyhashtag