ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Java 17 sealed classes let you lock down inheritance hierarchies and get compile‑time exhaustive pattern matching. This post shows how to declare a sealed interface, use it in a switch expression, and what to watch out for with proxies and modules.
Java 17 sealed classes let you restrict subclassing to a finite set. This guide shows how to declare a sealed hierarchy, use exhaustive pattern matching, and avoid common pitfalls. Compile with <code>javac --release 17</code> and keep the <code>permits</code> list in sync for reliable type safety.
NetBeans 12.4+ makes Java 17 records safe to adopt with component‑aware editing, Introduce Record refactoring, and debugger inspection that shows components directly.
Integration Overview Developers often embed the Sema Policy Engine into Spring‑based microservices by registering a SemaPolicyResolver bean and wiring a custom PolicyFilter into the SecurityFilterChain . The filter intercepts each request and delegates authorization decisions to Sema’s PolicyResolver . Version Compatibility Constraints Sema 1.2 officially su
Groovy 4 vs Java 17 sealed classes: can Groovy extend a sealed Java class? The goal is to determine whether Groovy 4 can legally extend a sealed Java 17 class or interface, and if so, how the compiler and runtime enforce the sealed hierarchy. Current observations indicate that Groovy 4’s compiler accepts subclasses of sealed Java types that are not listed in
Spark 4.0 changes the Scala binary compatibility boundary compared with Spark 3.5. Spark 3.5 ships Scala 2.12 and 2.13 builds, while Spark 4.0 is documented as Scala 2.13 only and requires Java 17 at runtime. The goal is to determine the impact on existing codebases compiled against Spark 3.5 with Scala 2.12 and Java 8/11 toolchains. The constraints include
The goal is to understand whether a Maven 4.0.0 build can continue to compile source code with Java 8 while the Maven process itself runs on Java 17, using the toolchains mechanism to decouple the compilation JDK from the runtime JDK. Maven 4.0.0 enforces a hard runtime baseline of Java 17, but the toolchains.xml configuration can still declare a Java 8 tool
java
sema
maven