Yes, we're now running our Black Friday Sale. All Access and Pro are 33% off until 2nd December, 2025:
Modern software architecture is often broken. Slow delivery leads to missed opportunities, innovation is stalled due to architectural complexities, and engineering resources are exceedingly expensive.
Orkes is the leading workflow orchestration platform built to enable teams to transform the way they develop, connect, and deploy applications, microservices, AI agents, and more.
With Orkes Conductor managed through Orkes Cloud, developers can focus on building mission critical applications without worrying about infrastructure maintenance to meet goals and, simply put, taking new products live faster and reducing total cost of ownership.
Try a 14-Day Free Trial of Orkes Conductor today.
Modern software architecture is often broken. Slow delivery leads to missed opportunities, innovation is stalled due to architectural complexities, and engineering resources are exceedingly expensive.
Orkes is the leading workflow orchestration platform built to enable teams to transform the way they develop, connect, and deploy applications, microservices, AI agents, and more.
With Orkes Conductor managed through Orkes Cloud, developers can focus on building mission critical applications without worrying about infrastructure maintenance to meet goals and, simply put, taking new products live faster and reducing total cost of ownership.
Try a 14-Day Free Trial of Orkes Conductor today.
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:
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:
Modern software architecture is often broken. Slow delivery leads to missed opportunities, innovation is stalled due to architectural complexities, and engineering resources are exceedingly expensive.
Orkes is the leading workflow orchestration platform built to enable teams to transform the way they develop, connect, and deploy applications, microservices, AI agents, and more.
With Orkes Conductor managed through Orkes Cloud, developers can focus on building mission critical applications without worrying about infrastructure maintenance to meet goals and, simply put, taking new products live faster and reducing total cost of ownership.
Try a 14-Day Free Trial of Orkes Conductor today.
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.
Yes, we're now running our Black Friday Sale. All Access and Pro are 33% off until 2nd December, 2025:
1. Introduction
In this tutorial, we’re going to have a look at how to deploy a war file on the JBoss server.
We can deploy the war file either by placing the file in the suitable directory manually or directly from Eclipse.
2. Deploying the WAR File by Hand
If we already have the war file and we want to deploy it on JBoss, we can go to the JBoss installation directory at standalone/deployments and paste the file there.
There are two modes in which the deployment works:
- manual: the deployment scanner will not attempt to directly monitor the deployment folder. Instead, the scanner relies on marker files. The user’s addition of a marker file serves as a sort of command telling the scanner to deploy content.
- auto: the scanner will directly monitor the deployment folder, automatically deploying new content and redeploying content whose timestamp has changed.
We can specify the mode in the configuration file standalone.xml by setting the value of the auto-deploy-zipped attribute to either true or false:
<deployment-scanner
name="default"
path="deployments"
scan-enabled="true"
scan-interval="5000"
relative-to="jboss.server.base.dir"
auto-deploy-zipped="true"
deployment-timeout="60"/>By default, the value is true. So whenever we place a war file in the deployment folder, it’s deployed automatically. JBoss creates the .deployed marker file automatically which indicates that the content has been deployed.
However, if we remove the previous deployment before copying a new war file to the deployment folder, JBoss will create an .undeployed marker file suggesting that the deployment has been removed. In that case, we would need to delete the marker file manually for the deployment to begin.
If the value of auto-deploy-zipped is set to false, we’ll need to create the .deployed marker file manually for the deployment to start.
3. Using Eclipse to Deploy
We can create a dynamic web project in Eclipse, add a JBoss server and then configure the application to run on the server. Internally, Eclipse will create the war file of the application and place it in the JBoss directory. We can create an index.html file and set the welcome-file in web.xml to point to it.
To test if the application is deployed successfully we can fire up the web browser and try to access the URL in this format: http://localhost:<portnumber>/<projectname>
If we see the index page, the application is deployed successfully.
4. Conclusion
In this article, we looked at how to deploy a war file on a JBoss server by working with the deployment folder and using Eclipse.
We also discussed the auto and manual deployment modes and how they work with JBoss’ marker files.
