{"id":41745,"date":"2015-07-20T10:00:07","date_gmt":"2015-07-20T07:00:07","guid":{"rendered":"http:\/\/www.javacodegeeks.com\/?p=41745"},"modified":"2015-07-19T18:30:24","modified_gmt":"2015-07-19T15:30:24","slug":"truly-unleashing-the-power-of-maven-and-java-ee","status":"publish","type":"post","link":"https:\/\/www.javacodegeeks.com\/2015\/07\/truly-unleashing-the-power-of-maven-and-java-ee.html","title":{"rendered":"Truly Unleashing the Power of Maven and Java EE"},"content":{"rendered":"

Ambition and vision can be the undoing of great solutions, if they are too complex to use. While Maven<\/a> and Java EE<\/a> are technologies that are well established throughout the Java industry, it can be extremely tricky to get\u00a0started with them and to architect\u00a0projects using all the techniques and patterns that\u00a0their authors intended you to use.<\/p>\n

How often do applications, midway in the development process, not need to be set up afresh again because of a flaw that crept into their\u00a0architecture right at the beginning? How much time is spent in drawing out and mapping the relationships between artifacts in an application, right at the beginning, only for all those plans and designs to gradually be forgotten and an unresolvable mess of spaghetti code to gradually arise instead?<\/p>\n

Here is where the right tools are essential and, when looking at all the available tools that relate to Maven and Java EE, it\u00a0can be seen that NetBeans IDE<\/a>, in particular, has been created to be both “Maven centric” and “Java EE centric”. What that means is that NetBeans IDE does not simply “support Maven” and “support Java EE”. No, NetBeans IDE has been developed over many years around the ideas and architectures that the authors of Maven and Java EE have always had in mind for you to use.<\/p>\n

Maven<\/h2>\n

The key to unlocking Maven is to realize that NetBeans IDE natively (i.e., “out of the box”)\u00a0understands the POM file that defines the project structure common to all\u00a0Maven projects. What makes Maven unique is that it standardizes project structures, enabling NetBeans IDE to natively provide standardized tools to support those project structures.<\/p>\n

Imagine a tool were to natively understand a Maven POM file.\u00a0What assumptions should you be able to make of such a tool?<\/p>\n

You should be able to assume one or more of the following:<\/p>\n

    \n
  1. No import process should be needed to convert a Maven project to some kind of internal structure inherent to the tool in question.<\/li>\n
  2. An “Open Project” command applicable to any other kind of application should work in exactly the same way for Maven, i.e., you’d assume you’d be able to browse to a folder containing the POM and then the tool should simply be able to open the Maven project and visualize it in some way in the tool. The visualization of the Maven project should be helpful and logical and, for example, enable you to see all the entry points easily.<\/li>\n
  3. The tool should be able to integrate its project-level commands with the goals defined in the POM, so that when you invoke a “Build Project” command, that you’d be able to map that command to Maven goals specific to the project, such as “mvn install”, for example.<\/li>\n
  4. Maven commands run in the tool should run and behave in the same way as on the command line, while producing the same kind of output as provided by a continuous build server, such as Jenkins.<\/li>\n
  5. The Maven dependencies should be visualized in some way, such that their interrelated connections can be viewed in some kind of reconfigurable and customizable set of diagrams.<\/li>\n<\/ol>\n

    Each of the assumptions above are realized in NetBeans IDE.<\/p>\n

    No importation process of any kind is needed to get a Maven project into NetBeans IDE. No plugin needs to be installed. Nothing needs to be configured. Simply go to File | Open Project (Ctrl-Shift-O) and browse to any folder containing a POM, such as the open source\u00a0multi-module JAnnocessor framework<\/a>. As you can see here, the IDE recognizes the project, while you’ve had to do nothing at all to “convince” the IDE that the project should somehow be openable, i.e., the IDE recognizes the project automatically, since the folder you’ve browsed to has a POM file. Click “Open Project” below and the IDE opens and visualizes the project in the Projects window.<\/p>\n

    \"unlock-11\"<\/a>

    <\/div> <\/div><\/p>\n

    Similarly, you can use the IDE’s Git tools, which are also baked into the IDE, no plugins or configuration needed:<\/p>\n

    \"unlock-7\"<\/a><\/p>\n

    For example, simply point to Arquillian lead Aslak Knutsen’s new Simple Arquillian HelloWorld Example project<\/a>, as shown below…<\/p>\n

    \"unlock-8\"<\/a><\/p>\n

    …and, at the end of the Git process, you’ll automatically have the Maven project open in the IDE, without having needed to do anything at all, since the IDE understands the POM file and organizes the Maven project coherently in the IDE based on the parsing of the POM file:<\/p>\n

    \"unlock-9\"<\/a><\/p>\n

    If the Maven project incorporates Java EE RESTful Web Services, the IDE visualizes the services as entry points into the application, as shown below:<\/p>\n

    \"unlock-10\"<\/a><\/p>\n

    As with other IDEs and tools, the IDE lets you run project-level commands, such as “Build” and “Run”, as shown below…<\/p>\n

    \"unlock-6\"<\/a><\/p>\n

    …however, what\u00a0happens<\/em> when those commands are invoked is completely up to you, i.e., use the Project Properties dialog of the Maven project to map Maven goals to project commands, as shown below:<\/p>\n

    \"unlock-5\"<\/a><\/p>\n

    A final point is that the dependencies in the POM are visualized and their relationships rendered in a customizable diagram, as shown here:<\/p>\n

    \"unlock-4\"<\/a><\/p>\n

    Moreover, as shown above by the fact that there’s an “Effective” tab, you can see where each entry in a multi-module project’s POM file comes from, as can be seen here, too:<\/p>\n

    \"unlock-12\"<\/a><\/p>\n

    Now that we have explored the deep integration of Maven with the IDE, let’s turn to Java EE, which is, of course, often used in combination with Maven.<\/p>\n

    Java EE<\/h2>\n

    The key to unlocking Java EE is to realize that the engineers who lead the Java EE specifications work for the same organization as the engineers who develop NetBeans IDE. Originally, the main driving force behind the Java EE platform was Sun Microsystems, while that has, of course, become Oracle, over the past few years. All along, NetBeans IDE is the development tool that has been positioned, by Sun Microsystems\u00a0as well as Oracle, as the official IDE for the Java platform.<\/p>\n

    Imagine a tool were to be developed by engineers at the same organization as where the Java EE platform itself is driven and developed. What assumptions should you be able to make of such a tool?<\/p>\n

    You should be able to assume one or more of the following:<\/p>\n

      \n
    1. When new specifications of the Java EE platform are released, a new version of the tool should be released, too. Generally, the current release of the tool should be synchronized with the current release of the Java EE platform.<\/li>\n
    2. The official documentation and tutorials of the Java EE platform should, from beginning to end, use the tool as the entry point to understanding the Java EE platform.<\/li>\n
    3. The tool should provide, out of the box, a lot more than a simple “hello world” example for getting started with the Java EE platform. More specifically, the tool should provide a very wide range of samples that help to understand far more than the simple basic components of the Java EE platform, in fact, the tool should provide, out of the box, complete scenarios that encapsulate best practices and enable newbies to the Java EE platform to be confident in building their applications based on the recommendations made available by the built-in examples.<\/li>\n
    4. The key components of the Java EE platform should be easy to set up in the tool. The tool should be the central mechanism for getting to grips with the Java EE platform and should be structured in such a way that each new release of the Java EE platform should be easy to understand via templates, code generators, and keyboard shortcuts that the tool should make available specifically for the Java EE platform.<\/li>\n
    5. Key members of the community around the Java EE platform should recognize and promote the tool as being the ideal way to come to grips with the Java EE platform.<\/li>\n<\/ol>\n

      The assumptions above are all, without exception, realized\u00a0in\u00a0NetBeans IDE. The IDE is always the first to provide tools and a variety of related features applicable to the latest release of the Java EE platform.<\/p>\n

      At the same time, out of the box, the\u00a0IDE comes with a wide range of simple as well as complex examples relevant to understanding each of the key components that make up the Java EE platform. Go to File | New Project (Ctrl-Shift-N) and you should see the immense range of Java EE examples for yourself, available and working out of the box, with the aim to help you get up and running with the key components of the Java EE platform:<\/p>\n

      \"unlock-1\"<\/a><\/p>\n

      Getting started with the Java EE platform is helped considerably via comprehensive templates, which generate large segments of a Java EE application, such as all the JPA entity classes from a database, or all JAX-RS RESTful Web Services from JPA entity classes or a database, as shown here:<\/p>\n

      \"unlock-2\"<\/a><\/p>\n

      Related to the above, the official Java EE tutorial uses NetBeans IDE throughout from beginning to end as the tool most well suited for creating applications that comply with the specifications conforming to the Java EE platform:<\/p>\n

      \"unlock-3\"<\/a><\/p>\n