Yes, we're now running our Black Friday Sale. All Access and Pro are 33% off until 2nd December, 2025:
Tomcat Configuration in Eclipse
Last updated: January 8, 2024
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. Overview
One of the key challenges of web development is being able to debug effectively when running on web servers. Since building, packaging, and deploying consumes a lot of time, this might be difficult to achieve.
Luckily, Eclipse allows us to start a server in the IDE itself, saving build and packaging time. Also, helping us to investigate issues by starting the server in debug mode.
In this quick tutorial, we’ll see how to configure a Tomcat server in Eclipse to achieve this.
2. Defining a Server in Eclipse
Before configuring Tomcat in Eclipse, we’ll have to install it first.
Now, let’s start by invoking the New Server wizard in Eclipse using File > New > Other:
Clicking on Next will take us to the window where we can select the version of Tomcat. Here, we have selected version 9.0:
The wizard will default the name of the server to localhost and the server name to Tomcat v9.0 Server at localhost.
We’ll see that the very first time we add a Tomcat server in Eclipse, the wizard will ask us to configure the server runtime environment:
Here, we’ll specify the location of the Tomcat installation directory. Also, we will specify the JRE for the Tomcat server.
If we click Next, Eclipse will allow us to add the web applications to be deployed on the server. But, let’s cover that in a later section and click on Finish instead.
Now we can see the new server in the Project Explorer and the Server views.
3. Configuring the Server
In the Project Explorer, we’ll see the usual tomcat server configuration files, e.g. server.xml, tomcat-users.xml etc.
Also, if we double-click on Tomcat v9.0 Server at localhost, we can configure the server using the provided UI:
On this screen, we can configure:
- server name – this is the name that will appear in the server view
- configuration path – this is where the files we see in the Project Explorer reside
- server location – this is where we configure the location of the server installation. Also, we can set the application deploy location here
- module publishing – this is where we configure how the web modules are published
- timeouts – these are timeouts for starting/stopping the server
- ports – here we can set the various server ports
- MIME mappings – these are the various MIME type mappings
- server launch configuration – here we can configure the VM arguments, classpath etc.
- server options – here we can enable/disable features like security, auto reload of modules by default etc.
4. Adding Applications to the Server
We can now deploy our web applications on this server. Consequently, we have to make sure that the Dynamic Web Module facet is enabled for the project before we can add them.
So let’s right-click on the tomcat server in the Servers view and choose the Add and Remove… menu item. Then, on the screen that follows, we’ll select the spring-rest web module:
Finally, if we now click on Finish, we’ll see spring-rest in the Servers view.
5. Running the Server
Now all that remains to do is start the tomcat server. Then we’ll see the server logs in the Console view, while the server is starting.
Keep in mind, if the server timeout is very low, the server might fail to start. Consequently, we can resolve this by increasing the server start timeout on the configuration screen we saw above.
It is important to note that eclipse will not publish the application to the server’s webapps folder. It will deploy this web application to a temporary folder. Therefore, leaving the Tomcat installation unmodified. If we do not change the configuration, Eclipse will publish the applications to the workspace folder:
<workspace>/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebappsNow, Eclipse will keep monitoring our source code and look for code changes. Then, we can sync these changes with the server so that the latest code is deployed on the server.
6. Conclusion
In this tutorial, we saw how we are able to deploy our web applications in the Eclipse IDE itself.
This helps us avoid having to explicitly build, package and deploy the applications, thus save us precious development time that can be used more effectively.
