Posts Tagged ‘Java EE’
IntelliJ IDEA 10 includes an option to setup an application server right in the New Project Wizard. You only need to specify a directory where the server is installed:
IntelliJ IDEA will create a sample application, setup it accordingly for the selected server and will add a corresponding Run Configuration. Once project is created you can just click Run button to start the server.
Next Maia EAP build includes new action that lets you quickly update a running JavaEE application after you changed its code. To invoke it, either press Ctrl+F10, or click this button on the Run tool window bar:
IntelliJ IDEA will allow you to select what to update in application:
Settings are saved in a current Run Configuration, so you can change them later even if you select Don’t ask again option.
Now, configure your servlets and filters with @WebServlet and @WebFilter annotations:
Everything is recognized by IntelliJ IDEA, as well as Web fragment descriptors and static resources packaged in libraries.
You can also use built-in Glassfish v3.0 integration to deploy your applications. Good luck!
Output layout of an artifact is displayed in a tree. You can edit it with Alt+Ins and Delete shortcuts, and by using drag-and-drop.
You can build artifact at any time from the main menu (Build | Build Artifact | <artifact name>), or you can automate it with the use of Build on make option in artifact settings, and Build Artifacts option in run configuration settings:
These features will be available in the next Maia EAP (around next Monday). Packaging configurations of existing JavaEE facets are migrated to artifacts automatically.
JRebel (formerly JavaRebel) is a small application that allows you to see changes you make to your code without redeploying it by mapping your project workspace directly to a running application. So, when you make a change to any class or resource in your IDE the change is immediately reflected in the application, skipping build and redeploy phases.
They’ve posted a survey (700+ respondents) that says the redeploy & restart phase wastes 2-8 weeks of your development time annually, depending on the container you use.
The plugin itself lets you configure JRebel for projects and containers directly within IntelliJ IDEA, using a neat GUI, instead of going to the command line. Basically, if you’re interested in JRebel, then it’s easier than ever to work with it directly from IntelliJ IDEA.
If you’re interested in writing your own plugins for IntelliJ IDEA, check out our repository of 550+ extensions, and information on how you can get started, here: http://plugins.intellij.net/
First Maia EAP brings you the following JavaEE support improvements:
- EJB 3.1 @Singleton Session Bean
- JPA 2.0 @ElementCollection attribute type, plus freshly allowed attribute types in embeddable objects (@OneToOne, @Embedded, etc.)
- JPA 1.0/2.0 with Hibernate provider will not throw false-positive warnings about certain JPA specification violations that occur because of differences in JPA and Hibernate.
IntelliJ IDEA provides excellent facilities for Java EE and Web development that let you easily create wide variety of applications.
To get you started with Java EE and Web development in IntelliJ IDEA, we’ve created a short and simple tutorial, showing how to create a basic Java EE application with servlets.
You can download the tutorial in PDF format and get IntelliJ IDEA a try right away. You are welcome to leave any comments, questions and suggestions in this post for discussion.
IntelliJ IDEA has the full-blown support for Enterprise Java Beans (EJB). Supporting EJB specifications from 1.x to 3.0 and leveraging it through all of its productivity-boosting features, from coding assistance to refactoring, IntelliJ IDEA stands for the weapon of choice for developing EJB applications.
Today we’re going to see how easy it is to migrate from earlier EJB versions to the latest 3.0. For the purposes of this demonstration we have a sample project, containing a 2.1 CMP Entity Bean and a Session Bean used to access CMP bean fields.
To migrate these beans to EJB 3.0:
- Switch Project View to
Java EE: Structure
- Expand the EJB Facets node
- Right-click EJB (in MigrationTest) and select
Apply EJB 3.0 Stylefrom the shortcut menu.
First we’re going to change the environment access settings for the beans and resort from using the
IntelliJ IDEA automatically upgrades the code. Have a look at the screenshot below and see the difference. Note that code before migration is displayed on the left side.
IntelliJ IDEA also automatically removes descriptors that were replaced with annotations from
Now, replace the CMP Entity Bean with JPA Persistence unit. For that:
- Invoke the migration dialog as described above
- Select the Replace Entity Beans with CMP to Persistence Unit
- Click Refactor
IntelliJ IDEA automatically creates the required JPA code and converts the existing Entity Bean. Notice that it has been removed from the project and matching JPA Persistence Unit has been created.
After that we have to manually rewrite the session bean code according to JPA specification so that it would use the Persistence Unit instead of the Entity Bean to complete migration.
Since version 7.0 IntelliJ IDEA provides the complete support for creating Web Service applications, providing the full range of productivity-boosting features:
- Smart code completion
- Syntax and error highlighting
- Code analysis, inspections, quick-fixes and refactoring
- Automatic code generation, including WSDL/WADL from Java and vice versa
- Dedicated run configurations for debugging and automated deployment
- and more
To help you get started with developing Web Service applications using IntelliJ IDEA, I’ve created a small tutorial, demonstrating how to create a simple Web Service and client application in literally few clicks. The tutorial shows how to create, deploy and use Web Service based on Apache Axis and JaxWS frameworks, with appropriate server and run configurations.
You can get it in PDF format here.