Mocking is an essential part of unit testing, and the Mockito library makes it easy to write clean and intuitive unit tests for your Java code.
Get started with mocking and improve your application tests using our Mockito guide:
Handling concurrency in an application can be a tricky process with many potential pitfalls. A solid grasp of the fundamentals will go a long way to help minimize these issues.
Get started with understanding multi-threaded applications with our Java Concurrency guide:
Spring 5 added support for reactive programming with the Spring WebFlux module, which has been improved upon ever since. Get started with the Reactor project basics and reactive programming in Spring Boot:
Since its introduction in Java 8, the Stream API has become a staple of Java development. The basic operations like iterating, filtering, mapping sequences of elements are deceptively simple to use.
But these can also be overused and fall into some common pitfalls.
To get a better understanding on how Streams work and how to combine them with other language features, check out our guide to Java Streams:
Explore Spring Boot 3 and Spring 6 in-depth through building a full REST API with the framework:
Yes, Spring Security can be complex, from the more advanced functionality within the Core to the deep OAuth support in the framework.
I built the security material as two full courses - Core and OAuth, to get practical with these more complex scenarios. We explore when and how to use each feature and code through it on the backing project.
You can explore the course here:
Spring Data JPA is a great way to handle the complexity of JPA with the powerful simplicity of Spring Boot.
Get started with Spring Data JPA through the guided reference course:
Refactor Java code safely — and automatically — with OpenRewrite.
Refactoring big codebases by hand is slow, risky, and easy to put off. That’s where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.
Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions — one for newcomers and one for experienced users. You’ll see how recipes work, how to apply them across projects, and how to modernize code with confidence.
Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.
Distributed systems often come with complex challenges such as service-to-service communication, state management, asynchronous messaging, security, and more.
Dapr (Distributed Application Runtime) provides a set of APIs and building blocks to address these challenges, abstracting away infrastructure so we can focus on business logic.
In this tutorial, we'll focus on Dapr's pub/sub API for message brokering. Using its Spring Boot integration, we'll simplify the creation of a loosely coupled, portable, and easily testable pub/sub messaging system:
1. Overview
In this quick tutorial, we’ll have a look at how to change the default port in WildFly; generally, this port is 8080.
Of course, WildFly is a popular open source application server maintained by the JBoss community.
2. Using Configuration XML
In the standalone mode, we can update the configuration XML files to change the default port.
In the WildFly installation home directory, standalone.xml can be found in the standalone/configuration folder. We can open this file in any text editor and replace the default port 8080 with any port of our choice in the following line:
<socket-binding name="http" port="${jboss.http.port:8080}"/>There is another way to change the default port by tweaking the XML. In the same standalone.xml we can set an offset value for the port:
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">The default value is 0 that means the HTTP port will be 8080. If we change the offset value to 10 then the HTTP port will be 8090 (8080+10). We must keep in mind, though, that the offset affects other ports, too.
For example, the https port will be changed to 8453 (8443+10).
3. Using System Property
The default WildFly port can be changed by setting the system property jboss.http.port – while starting the server.
For Windows:
standalone.bat -Djboss.http.port=<Desired_Port_Number>For Unix/Linux:
standalone.sh -Djboss.http.port=<Desired_Port_Number>4. Conclusion
In this quick article, we found out how to change the default port in WildFly quite easily.
You can explore different popular servers available for Java development in our previous article.
