Run/Debug Configuration: Tomcat Server
Use the Tomcat Server run/debug configuration to deploy and debug your applications on Tomcat. For more information, see Application server run configurations.
Use a Local configuration to run a local instance of the application server and deploy the artifacts to it.
Use a Remote configuration to deploy artifacts to a running application server instance.
Even if you are connecting to a remote application server, you still need a local installation of this server configured under Build, Execution, Deployment | Application Servers as described in Integration with application servers.
Enable the Tomcat and TomEE plugin
This functionality relies on the Tomcat and TomEE plugin, which is bundled and enabled in IntelliJ IDEA by default. If the relevant features aren’t available, make sure that you didn’t disable the plugin.
Press Control+Alt+S to open the IDE settings and then select Plugins .
Open the Installed tab, find the Tomcat and TomEE plugin, and select the checkbox next to the plugin name.
Server tab for a local configuration
Select the server configuration to be used.
Click Configure to create a new server configuration or edit an existing one. (The Application Servers dialog will open.)
Select this checkbox to start a web browser after starting the server and deploying the artifacts.
Select the browser from the list. Click Shift+Enter to configure your web browsers.
With JavaScript debugger
If this checkbox is selected, the web browser is started with the JavaScript debugger enabled.
Note that JavaScript debugging is available only for Firefox and Google Chrome. When you debug your JavaScript in Firefox for the first time, the JetBrains Firefox extension is installed.
The field underneath After launch
Specify the URL the browser should go to when started. In most typical cases, this URL corresponds to the root of your Web application or its starting page.
Specify the options to be passed to the Java virtual machine when launching the application, for example, -mx , -verbose , and so on.
When specifying JVM options, follow these rules:
Use spaces to separate individual options.
If the value of an option includes spaces, enclose either the value or the actual spaces with double quotes.
If an option includes double quotes as part of the value, escape the double quotes using backslashes.
You can pass environment variable values to custom Java properties.
Use code completion in this field: start typing the name of a flag, and the IDE suggests a list of available command line options. This works for -XX: and -X options and some standard options that are not configured by IntelliJ IDEA automatically, like -ea , but not for -cp or –release .
The -classpath option specified in this field overrides the classpath of the module.
On ‘Update’ action
Select the necessary option for the Update application function ( or Control+F10 in the Run or Debug tool window).
The update options are different for exploded and packed artifacts.
For exploded artifacts, the available options are:
Update resources. All changed resources are updated (HTML, JSP, JavaScript, CSS and image files).
Update classes and resources. Changed resources are updated; changed Java classes (EJBs, servlets, etc.) are recompiled.
In the debug mode, the updated classes are hot-swapped. In the run mode, IntelliJ IDEA just updates the changed classes in the output folder. Whether such classes are actually reloaded in the running application, depends on the capabilities of the runtime being used.
Redeploy. The application artifact is rebuilt and redeployed.
Restart server. The server is restarted. The application artifact is rebuilt and redeployed.
For packed artifacts, the available options are:
Hot swap classes. Changed classes are recompiled and reloaded at runtime. This option works only in the debug mode.
Redeploy. The application artifact is rebuilt and redeployed.
Restart server. The server is restarted. The application artifact is rebuilt and redeployed.
Select this checkbox if you want to see the Update dialog every time you use the Update application function.
The Update dialog is used to select the Update option prior to actually updating the application.
On frame deactivation
Specify what IntelliJ IDEA should do when you switch from the IDE to a different application (for example, a web browser). (Frame deactivation means switching to a different application.)
The options other than Do nothing have the same meanings as in the case of the Update action.
By default, the project JDK is used to run the application. If you want to specify an alternative JDK or JRE here, select it from the drop-down list.
The server HTTP port.
The server HTTPS port.
The server JMX port.
The server AJP port.
Deploy applications configured in Tomcat instance
The Tomcat configuration files, among other things, may list the applications that should be deployed at the server start. If this checkbox is selected, all the applications so listed will be deployed on the server in addition to the artifacts specified on the Deployment tab.
If the checkbox is not selected, only the artifacts and the external resources specified on the Deployment tab will be deployed.
Preserve sessions across restarts
Select this checkbox to preserve active HTTP sessions when restarting the server.
Server tab for a remote configuration
Select the server configuration to be used. Note that this is a local server configuration. (When working with a remote server, the same server version must be available locally.)
Click Configure to create a new server configuration or edit an existing one. (The Application Servers dialog will open.)
Select this checkbox to start a web browser after connecting to the server and deploying the artifacts.
Select the browser from the list. Click Shift+Enter to configure your web browsers.
With JavaScript debugger
If this checkbox is selected, the web browser is started with the JavaScript debugger enabled.
Note that JavaScript debugging is available only for Firefox and Google Chrome. When you debug your JavaScript in Firefox for the first time, the JetBrains Firefox extension is installed.
The field underneath After launch
Specify the URL the browser should go to when started. In most typical cases, this URL corresponds to the root of your Web application or its starting page.
On ‘Update’ action
Select the necessary option for the Update application function ( or Control+F10 in the Run or Debug tool window).
The options are:
Hot swap classes. Changed classes are recompiled and reloaded at runtime. This option works only in the debug mode.
Redeploy. The application artifact is rebuilt and redeployed.
Select this checkbox if you want to see the Update dialog every time you use the Update application function.
The Update dialog is used to select the Update option prior to actually updating the application.
On frame deactivation
Specify what IntelliJ IDEA should do when you switch from the IDE to a different application (for example, a web browser). (Frame deactivation means switching to a different application.)
The options other than Do nothing have the same meanings as in the case of the Update action.
The server JMX port.
If you are not deploying anything with this run configuration, you don’t need to specify this port.
This section contains the settings related to staging.
Select the way the staging environment or host is accessed for transferring the application artifact or artifacts from your local computer. (In the user interface of IntelliJ IDEA this setting is also referred to as the connection type .)
The available options are:
Same file system. Select this option if the target server is installed on your local computer. The artifacts in this case are deployed locally and, thus, don’t need to be transferred to a remote host.
Local or mounted folder. The staging environment is a local folder or is accessed as a mounted folder.
If the list is empty, you have to enable the FTP/SFTP Connectivity plugin which supports the corresponding functionality.
If Same file system is selected for Type , the only available option for Host is also Same file system .
In all other cases, the list contains the existing configurations of the selected type. So each configuration corresponds to an individual (S)FTP connection, or a local or mounted folder.
Select an existing configuration or create a new one.
Click to the right of the list.
In the Add Server dialog, specify the configuration name, select the type, and click OK .
On the Connection tab, specify the settings in the Upload/download project files section.
The rest of the settings don’t matter.
Click OK in the Deployment dialog.
When deploying to the remote host, the application artifact or artifacts are placed into a staging folder which should be accessible to Tomcat. The settings in this section define the location of this staging folder.
Note that if Same file system is selected for Type and Host , no settings in this section need to be specified.
The path to the staging folder relative to the local or mounted folder, or the root of the (S)FTP host.
You can use to select the folder in the Choose target path dialog.
The absolute path to the staging folder in the local file system of the remote host.
Remote connection settings
The settings for accessing deployed applications.
The fully qualified domain name or the IP address of the Tomcat host.
The server HTTP port.
Example: remote staging for a mounted folder
C:\shared is a shared folder on the remote host, which is mounted to the local computer as the drive X: .
The folder that you are going to use for staging is C:\shared\staging .
Here are the corresponding remote staging settings:
Type: Local or mounted folder.
Host: The configuration should be selected in which the value in the Folder field is X:\ (the Upload/download project files section on the Connection tab of the Deployment dialog).
Staging/Path from root: staging
Staging/Mapped as: C:\shared\staging
Deployment tab
Specify which artifacts or external resources to deploy. An external resource is a deployable web component, such as a .war file, which is not represented by a project artifact. Usually, such components are stored outside of the project scope.
To deploy artifacts to a remote application server, you need Tomcat version 5 or later. Make sure that you pass the following VM options to enable JMX support on the server:
Specify the port and hostname or IP address of your application server.
If you use catalina.bat or catalina.sh to start the server, pass the options via the CATALINA_OPTS environment variable.
Add an artifact or an external resource to the list.
Remove the selected artifacts and external resources from the list.
Configure the selected artifact. The Artifacts page of the Project Structure dialog will open.
Specify the context root for an artifact or external resource: select the artifact or the resource and type or select the context root.
Logs tab
Use this tab to specify which log files generated while running or debugging should be displayed in the console, that is, on the dedicated tabs of the Run or Debug tool window.
Select checkboxes in this column to have the log entries displayed in the corresponding tabs in the Run tool window or Debug tool window.
The read-only fields in this column list the log files to show. The list can contain:
Full paths to specific files.
Ant patterns that define the range of files to be displayed.
Aliases to substitute for full paths or patterns. These aliases are also displayed in the headers of the tabs where the corresponding log files are shown.
If a log entry pattern defines more than one file, the tab header shows the name of the file instead of the log entry alias.
Select this checkbox to have the previous content of the selected log skipped.
Save console output to file
Select this checkbox to save the console output to the specified location. Type the path manually, or click the browse button and point to the desired location in the dialog that opens .
Show console when a message is printed to standard output stream
Select this checkbox to activate the output console and bring it forward if an associated process writes to Standard.out.
Show console when a message is printed to standard error stream
Select this checkbox to activate the output console and bring it forward if an associated process writes to Standard.err.
Click this button to open the Edit Log Files Aliases dialog where you can select a new log entry and specify an alias for it.
Click this button to edit the properties of the selected log file entry in the Edit Log Files Aliases dialog .
Click this button to remove the selected log entry from the list.
Code Coverage tab
Use this tab to configure code coverage monitoring options.
Note that this tab is not available for remote servers.
Choose code coverage runner
Select the desired code coverage runner.
Select this option to measure code coverage with minimal slow-down.
Select this option to collect accurate branch coverage. This mode is available for the IntelliJ IDEA code coverage runner only.
Track per test coverage
Select this checkbox to detect lines covered by one test and all tests covering line.
Packages and classes to record code coverage data
If necessary, specify the classes and packages to be measured.
Use or to add classes or packages to the list.
To remove the classes or packages from the list, select the corresponding list items and click .
Enable coverage in test folders.
Select this checkbox to include the test source folders in code coverage analysis.
Startup/Connection tab for a local configuration
Use to switch between the settings for the run, debug and code coverage modes.
Specify the script to be used to start the server.
If this checkbox is selected, the default script is used.
in this case opens the Default Startup Script dialog which shows the contents of the Startup script field (readonly).
Clear this checkbox to change the parameters passed to the script or to specify a different script:
To specify the script, click and select the desired script in the dialog that opens .
To specify the parameters, click and specify the script parameters and VM options in the Configure VM and Program Parameters dialog.
When specifying the parameters and options, follow these rules:
Use spaces to separate individual parameters and options, for example, -client -ea -Xmx1024m .
If a parameter or an option includes spaces, enclose the spaces or the argument that contains the spaces in double quotes, for example, some" "arg or "some arg" .
If a parameter or an option includes double quotes (e.g. as part of the argument), escape the double quotes by means of the backslashes, for example, -Dmy.prop=\"quoted_value\" .
Specify the script to be used to stop the server.
If this checkbox is selected, the default script is used.
in this case opens the Default Shutdown Script dialog which shows the contents of the Shutdown script field (readonly).
Clear this checkbox to change the parameters passed to the script or to specify a different script:
To specify the script, click and select the desired script in the dialog that opens .
To specify the parameters, click and specify the script parameters and VM options in the Configure VM and Program Parameters dialog.
When specifying the parameters and options, follow these rules:
Use spaces to separate individual parameters and options, for example, -client -ea -Xmx1024m .
If a parameter or an option includes spaces, enclose the spaces or the argument that contains the spaces in double quotes, for example, some" "arg or "some arg" .
If a parameter or an option includes double quotes (e.g. as part of the argument), escape the double quotes by means of the backslashes, for example, -Dmy.prop=\"quoted_value\" .
Pass environment variables
To pass specific variables to the server environment, select this checkbox and specify the variables:
To add a variable, click and specify the variable name and value in the Name and Value fields respectively.
To remove a variable from the list, select the variable and click .
Use this field to change the debugger port.
Click this button to edit the debugger options on the Debugger page of the Settings dialog.
Startup/Connection tab for a remote configuration
This tab shows command-line options for starting the server JVM in the run and debug modes.
Use to switch between the settings for the run and debug modes. The settings are shown in the area under To run/debug.
To run/debug remote server JVM.
The command-line options for starting the server JVM. These are shown just for copying elsewhere.
Transport (and all that follows)
The GUI for generating the remote debug command-line options shown in the area under To run/debug.
Common settings
When you edit a run configuration (but not a run configuration template), you can specify the following options:
Specify a name for the run configuration to quickly identify it among others when editing or running.
Allow multiple instances
Allow running multiple instances of this run configuration in parallel.
By default, it is disabled, and when you start this configuration while another instance is still running, IntelliJ IDEA suggests stopping the running instance and starting another one. This is helpful when a run configuration consumes a lot of resources and there is no good reason to run multiple instances.
Store as project file
Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations . However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project.
By default, it is disabled, and IntelliJ IDEA stores run configuration settings in .idea/workspace.xml .
Toolbar
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.
Create a run/debug configuration.
Delete the selected run/debug configuration. Note that you cannot delete default configurations.
Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.
The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.
Move into new folder / Create new folder. You can group run/debug configurations by placing them into folders.
To create a folder, select the configurations within a category, click , and specify the folder name. If only a category is in focus, an empty folder is created.
Then, to move a configuration into a folder, between the folders or out of a folder, use drag or and buttons.
To remove grouping, select a folder and click .
Click this button to sort configurations in the alphabetical order.
Before launch
In this area, you can specify tasks to be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
Click this icon to add one of the following available tasks:
Run External tool : select to run an external application. In the dialog that opens, select one or multiple applications you want to run. If it is not defined in IntelliJ IDEA yet, add its definition. For more information, see External tools and External tools settings.
Run Another Configuration : select to execute another run/debug configuration and wait until it finishes before starting the current configuration. If you want to run several configurations in parallel, use a compound run/debug configuration.
Build : select to compile the specified module. The Build Module command will be executed.
If an error occurs during compilation, IntelliJ IDEA won’t attempt to start the run/debug configuration.
Build Project : select to compile the entire project. The Build Project command will be executed.
If an error occurs during compilation, IntelliJ IDEA won’t attempt to start the run/debug configuration.
Build, no error check : the same as the Build option, but IntelliJ IDEA will try to start the run/debug configuration irrespective of the compilation results.
Build Artifacts : select this option to build an artifact or artifacts. In the dialog that opens, select the artifact or artifacts that should be built.
Launch Web Browser : select this option to have a browser started. In the dialog that opens, select the type of the browser and provide the start URL. Also, specify if you want the browser be launched with JavaScript debugger.
Run Ant target : select this option to run an Ant target. In the dialog that opens, select the target to be run.
Run Grunt task : select this option to run a Grunt task.
In the Grunt task dialog that opens, specify the Gruntfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Grunt tool.
Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the grunt-cli package.
Run gulp task : select this option to run a Gulp task.
In the Gulp task dialog that opens, specify the Gulpfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Gulp tool.
Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the gulp package.
Run Maven Goal : select this option to run a Maven goal. In the dialog that opens, select the goal to be run.
Run npm script : select this option to execute an npm script.
In the NPM Script dialog that opens, specify the npm run/debug configuration settings.
If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start.
If the Check errors checkbox is cleared, the compiler will show all the detected errors but the run configuration still will be launched.
Run Remote External Tool : adds a remote SSH external tool.
Disconnect Data Source : select this option if you want to disrupt the connection to a data source before the run/debug configuration is run.
Click this icon to remove the selected task from the list.
Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
Click these icons to move the selected task one line up or down in the list. The tasks are performed in the order that they appear in the list.
Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.
Activate tool window
By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration.
Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5 .
How to run/debug your web application with IntelliJ IDEA and Tomcat
This is a very short article on how to run and debug your web application using IntelliJ IDEA.
In order to learn how to run/debug a web application, you need to have a web application. Obvious! 😀 If you are interested in learning how to create a simple Java RESTful Web Service refer here. For this article, I have created a very simple JAX-RS/Jersey web application. You can find the source code here on GitHub. Fork the repository and clone it and modify it as you want. Otherwise, simply download the .zip file and extract and open it on IntelliJ IDEA.
Prerequisites
- IntelliJ IDEA: A Java IDE by JetBrains
- Apache Tomcat Web Server version 7: Open source servlet container
- Download the sample web application source code from here.
Setting up Tomcat and adding artefacts
If you are using macOS then you can use Homebrew to install the tomcat server. Also, you can visit http://tomcat.apache.org/ and download the zip file and extract it to a location based on your preference.
Now open IntelliJ IDEA. Open the downloaded project jaxrs-sample-webapp.
Then go to the 'Run' menu and 'Edit Configurations'. Refer to Figure 1 below.
In the popup window, click on the ‘+’ button on the top left corner. Refer to Figure 2 below.
In the drop-down select Tomcat Server >> Local as shown in the Figure 3 below.
You will be directed to the following window as in Figure 4. Please note that you can always use the 'Configure' button and provide the path to the bin folder of your apache tomcat installation and change the servers as needed. If you have multiple servers, name them properly to avoid confusions.
In the above window, you will see a warning message saying "No artefacts marked for deployment". Scroll down further or click and expand on "Before launch: Build. Activate tool window". Refer to Figure 5 below.
Click on the "+" button on the bottom of the window, below “Build” and select "Build Artifacts". Refer to Figure 6 below.
On the popup window select the 'simple_webapp:war' checkbox as shown in Figure 7 below. Click OK.
Then go to the 'Deployment' tab as shown in Figure 8 below and then click on the "+" button, which is on top of the Application Context. Then select "Artifact…" from the drop-down.
On the popup window select the ‘simple_webapp:war’ as shown in Figure 79 below and click OK.
N.B. Make sure to change the "Application Context" to /simple_webapp. This will be by default /simple_webapp_war. Refer to Figure 10 below.
Click OK, then Apply and then OK again. Now you should see similar IDE interface as below in Figure 11 and 12.
If you are all set up to this point and everything happens smoothly, you are ready to run your web application. Before running the web application lets put a HelloService.java line 18 a debug point. Just click on where you can see a red ball in Figure 12 below.
All set to run. Get set, ready and Run… Refer to Figure 13 below. Click on the "Run" menu and then click "Run…".
Since we click on "Run", you do not need to worry about the debug point. The Tomcat server will be started in normal mode. Now the Tomcat server will be started and your web application will be deployed. Now it is time to test your REST API. You can use any REST client like Postman, CURL etc. Here, I'm going to use a web browser because it is the easiest. Open the browser and copy and paste the following endpoint.
You should get the output as shown in Figure 14 (Make sure you run Tomcat on the port 8080).
To debug, you need to start the Tomcat server in debug mode. Since we are handling everything inside IntelliJ IDEA, you can go to the "Run" menu and then click on "Debug…". Refer the Figure 15 below. Now the Tomcat server will be started in debug mode and your web application will be deployed.
This time you will be directed back to the IDE. Now your program is paused in the debug point that you have added before. That is on line 18 in HelloService.java file. Refer the Figure 16 below.
You can debug your code line by line if you want by using the different arrow icons you can see in Figure 17.
At any time you can resume program or execute line by line or whatever you like to do. Here you can see (Figure 17) the values that your variables hold, object references etc. If you want, you can add different values to these variables manually and test. That will be a separate topic like what you can do while debugging. So I'm not going to describe what you can do here. Once you executed all the lines or if you resume the programme you should get the final outcome on the browser as in Figure 14.
Well, that's a very short and quick explanation of how you can run/debug your web application with IntelliJ IDEA and Tomcat.
If you like this article and the content that I create, you can buy me a virtual coffee ️��;
How To: Use Tomcat in Intellij IDEA Community
Recently I started working on a project that required me to have the backend part installed locally, instead of using a remote backend. The project uses Maven as a build tool and it deploys the code to a Tomcat server.
I got cracking and started configuring the project on my local machine. The first thing I noticed is that Intellij IDEA Community does not have a Tomcat plugin, unlike the Ultimate edition, that has one out of the box.
Many Google searches later I found a few plugins that might do the trick but when I tried using them, the famous NullPointerException happened and I started looking for an alternative. I found some inspiration on Github, but not in the form I wanted, but it was good enough to get me started.
Bellow is a short tutorial on how to setup Tomcat in Intellij IDEA Community to run/debug, and how to use Maven to build your project and then deploy it to Tomcat.
Prerequisites
- Install Intellij IDEA Community.
- Install Tomcat — For my project I’ve used Tomcat 8. You can get it from here.
- Install Maven.
Tomcat Configuration
Make sure you install Tomcat in a place that doesn’t require admin access, for example next to your project.
After that, open File -> Settings and expand Tools and select External Tools .
You can add a new tool with whatever name you want. I named mine, Tomcat. For tool settings, select the catalina.bat file, usually located in the bin folder of your Tomcat installation. For example mine is C:\apache-tomcat-8.5.34\bin\catalina.bat . And last but not least set an argument with the command jpda run . The working directory should be set automatically.
Tomcat External Tool
Start Tomcat
If you go to Tools -> External Tools and click on Tomcat, it should start the Tomcat server.
Maven build and deploy to Tomcat
Now that you’re done with the Tomcat configuration you want the ability to build using Maven and deploy to the now working Tomcat server.
To achieve this you’ll need to head over to Run -> Edit Configurations , click the «+» and select Maven . Don’t forget to name your new configuration. Select your project location and add the following command line.
Exit fullscreen mode
What this line does is that it builds the project, using Maven, and then gets the file from the specified path (that’s usually configured in your project) and copies it to the webapps folder in Tomcat. Tomcat then knows it has a new version of the file and redeploys it.
Build and deploy to Tomcat
Tomcat Remote Debug
Like all applications you want the ability to debug your backend. To achieve this you’ll need to add a new configuration like the previous step. The only difference this time is that when you click «+» you’ll need to select Remote .
Give your configuration a name. You’ll need to set the Debugger mode to Attach to remote JVM , the Transport to Socket , the Host to localhost and lastly the Port to 8000 . That way when you start the configuration, Intellij will connect via Socket to the Tomcat server that emits via port 8000 . You can change the port for Tomcat, to something else, in the Tomcat server.xml file, in the config folder.
Tomcat Remote Debug
Once the Tomcat server is started you can run this configuration. Just click on Run -> Debug and then select the newly created configuration.
If you want to keep a record of all the logs when debugging, you can achieve this by going to the Logs tabs in the newly created Remote configuration and set the Save console output to file to the logs folder of your Tomcat installation. In my case it was C:\apache-tomcat-8.5.34\logs*.* .
Tomcat Remote Debug Logs
That is it. @ me on Twitter if you think I’ve missed something or if there is another way of doing this without installing Eclipse or purchasing the Ultimate edition of Intellij IDEA.
Добавление Tomcat в IDEA
Шаг второй. Затем выбираем локальный Tomcat.
Шаг третий. Конфигурируем Tomcat. Нажав на strong>configure добавляем путь к папке Tomcat
Тут ты можешь указать:
- HTTP port — порт, на котором будет работать Tomcat
- JRE — можно выбрать JRE, на которой будет работать Tomcat
- VM options — параметры виртуальной машины для Tomcat
- URL — эту ссылку будет открывать IDEA после запуска сервера с ее помощью
Шаг четвертый. Добавляем наш проект как артефакт к Tomcat.
Для этого переходим на вкладку Deployment и нажимаем справа кнопку +.
5.2 Создаем первое веб-приложение
Если у тебя еще нет никакого веб-приложения, то можно создать его в IDEA двумя способами. Проект на основе Maven и просто родной JavaEE-проект.
Если ты хочешь создать родной web-проект от IDEA, то следуй этой простой инструкции:
Шаг 1. Создаем новый проект ( menu File -> New Project ), затем выбираем:
- Тип проекта — Java Enterprise
- Шаблон (template) приложения — Web Application
- Application Server — текущий сконфигурированный Tomcat Server. Если он еще не добавлен, то справа есть кнопка New .
- JDK — твою текущую Java JDK
Шаг 2. Дальше IDEA попросит указать различные зависимости, ничего не добавляй.
Шаг 3. Если Tomcat был настроен правильно, то ты увидишь свое приложение:
Шаг 4. Твой проект готов, можешь запускать его кнопкой Run или Debug.
5.3 Создаем первое веб-приложение на основе Maven
Если ты хочешь создать web-приложение на основе проекта Maven, то инструкция будет еще проще.
Шаг 1. Создаем новый проект ( menu File -> New Project ), затем выбираем:
- Тип проекта — Maven Archetype
- JDK — задаем JDK проекта
- Archetype (шаблон проекта) — задаем maven-archetype-webapp
Шаг 2. Получим проект типа такого:
Проект сгенерирован, но Tomcat еще не настроен. Чтобы иметь возможность запускать или дебажить проект, тебе нужно настроить Tomcat и добавить свой проект в него как артефакт. Как именно это делать, мы уже рассматривали раньше.
Шаг 3. Если Tomcat настроен правильно, то твоя страница настроек должна выглядеть примерно так:
Шаг 4. Твой проект готов, можешь запускать его кнопкой Run или Debug.