This article will examine some dos and don'ts for Gradle plugin developers. These include common implementation issues that complicate the usage of third-party plugins and some principles for an ideal plugin API.
JavaScript singe-page application can mimic sub pages via an internal routing mechanism. For this feature to still work on a page reload, a filter must be implemeneted in a Quarkus backend which redirects certain 404 errors to the index page.
An analysis of class names from the most popular Java repositories on GitHub. In particular, we will try to give a statistical answer for naming controversies, such as the case sensitivity of abbreviations.
The best way to become familiar with Quarkus as a Spring developer is to look at what is required to migrate a Spring application to a Quarkus application. This way, we can build a deep understanding of the concepts and components of Quarkus.
We are looking at a project architecture that combines the maven and npm toolchains to bundle a web framework frontend and a Quarkus backend into one distributable JAR.
This article presents an implementation strategy to create a custom JSON, HTML, or text error page, via a centralized error response handling in an exception mapper or a response filter.
In this article we look at the primitive equivalents to object-based functional interfaces, streams and optionals, which are available in the Java standard library.
Implementation strategies for the "synchronizer token", "cookie-to-header token" and "double submit cookie" pattern to prevent CSRF attacks in Quarkus.