The Jakarta EE 2019 Developer Survey is available!
Take the survey today and help the community gain a better understanding of what’s in store for Java innovation. This is your chance to share your thoughts and experiences and help shape the future for Jakarta EE!
Responses will be collected until March 25, 2019, at 11:59 PM Pacific Time
The Apache NetBeans project is really shaping up. Version 10.0 was released on the 27th of December 2018. The main features added since version 9.0 are listed on the download page. For me personally, the most important feature is the JDK 11 Support.
So, what about Java EE then?
Until all the NetBeans sources have been transferred from Oracle to Apache and incorporated into the Apache NetBeans build, an additional step is required in order to get Netbeans set up for Java EE development.
The first thing you need to do is to add the NetBeans 8.2 Distribution Update Center. Select Tools->Plugins in Apache NetBeans 10.0. Then click on the Settings tab and choose Add. Paste in the URL:
http://updates.netbeans.org/netbeans/updates/8.2/uc/final/distribution/catalog.xml.gz
After saving the configuration, the next step is to select the Available Plugins tab and type java ee in the search field.
As a minimum, check the plugin called Java EE Base and click the Install button. Follow the instructions and accept the licenses. NetBeans will need to restart before continuing after the installation.
After this, you are able to set up a Java EE server as shown with GlassFish 5.0 below. Choose Tools->Servers and then click Add Server.
Happy Coding!
Java EE developers using NetBeans are used to be able to run and debug their thin-war applications in their application server of choice directly from NetBeans. When developing microservices packaged as über-or hollow-jars, you expect the same effortless way of running and debugging. The good news is that you can. In this post, I show step-by-step how to run and debug the WildFly Swarm version of CloudEE Duke in NetBeans.
The easiest way of running CloudEE Duke in NetBeans is to edit the Run project action for the project. Right click on CloudEE Duke, select properties and Actions as shown below.
Configure the Execute Goals to package wildfly-swarm:run, remove all the default properties and your’re all set. Run Project (F6 ) will start the application using the WildFly Swarm Maven Plugin.
To enable debugging, you follow the same steps as described above, but in this case it is the Debug Project action you select.
Execute Goals is configured the same way as for Run, but in the Set Properties, you need to configure a debug port for WildFly Swarm. This is done by setting the swarm.debug.port property, e.g. to 9000.
Debug Project Ctrl-F5 will start the application in debug mode. Note that the execution will halt while waiting for the debugger to attach. See the screenshot below for how it will look in the log.
Select Debug->Attach Debugger from the menu in NetBeans. Change the value for Port to 9000 (or the value you chose in the previous step) and click OK.
To verify the setup, set a breakpoint at line 16 in the class HelloWorldEndpoint.
Then navigate to http://localhost:8080/hello. The execution will stop at the breakpoint at line 16 in HelloWorldEndpoint.
2016 was a pretty eventful and great year for me personally. I had the opportunity to speak at a number of conferences including Jfokus, JavaLand, GIDS, CybercomDev, jPrime, Devoxx UK, JavaDay Minsk, JavaOne, JavaDay Kiev, Devoxx MA, Øredev. Links to talks and videos for most of these talks can be found on my Speaker Bio page.
I will continue speaking at conferences and events throughout 2017 as well. First up are Snowcamp.io, Devnexus, jDays, JavaLand, Riga Dev Days, DevDays Vilnius. And I still have some CFPs to submit talks to…
I also took over as JUG leader of Javaforum, the Java User Group in Malmö, and we had four meetings during 2016. The goal for 2017 is to continue with one meeting each quarter.
At the end of the year I won one of the associate seats in the Executive Committee of the Java Community Process. I am really looking forward to starting this work (I am actually going to London for our first face-to-face meeting tomorrow…).
If I should pick one single thing as the highlight of 2016, it would be the accepted to join the Java Champions. It was a surprise and an honor to be handed the Java Champions jacket from Arun Gupta at the closing Keynote of Devoxx UK.
The JPA Modeler plugin for NetBeans provides visual support for creating, designing and editing entity relationship models. It also provides Java code generation and new for version 1.5.5 is that it provides support for generating MVC 1.0 applications.
Check out MVC 1.0 Generator Tutorial to see how it works.
Kudos to Gaurav Gupta (@jGauravGupta) for this awesome tool! Another proof that NetBeans is the IDE for developing Java EE applications!
Follow @jpamodeler on Twitter!
It is great to start 2016 with the announcement that I have been included in the NetBeans Dream Team!
I always try to be as objective and unbiased as possible when writing and talking about tools and technologies, but I guess it has been pretty obvious that NetBeans is my favorite IDE and in my opinion the best IDE for Java EE development. Being a member of the Dream Team will enable me to contribute even more to make this great tool even greater.
More information about the NetBeans Dream Team can be found on the wiki.
Five days packed with technical sessions, discussions, community building…It is such a blast!
I have heard more than once that this conference is more about the people than the technology. And I totally agree with that.
Since I am pretty heavy involved in the Java Community Process (JCP), many of my activities this year (as last year) was connected to this. I was interviewed on NightHacking about the JCP in general as well as the JSRs I am on the expert group of (368, 371 and 375). I also managed to get in a word or two about Snoop with input from Arun Gupta.
In addition to my planned sessions, CON1615: Meet Snoop – a Discovery Service for Java EE and BOF3666: How would you like to improve the Java EE Security API, I was also on stage at the CON4176: Introduction to MVC 1.0 (JSR 371).
Thursday morning we had a very productive Face-to-Face meeting in the JMS 2.1 Expert Group (JSR 368). The minutes from this meeting can be found here.
Last, but not least, thanks to Tomitribe for gathering together the #usualsuspects and making sure everyone is having a good time.
JavaOne in San Francisco is less than a month away. If you have not registered yet, do so now!
So far so good! Then you will need to add sessions you want to attend to to your personal schedule. Make sure you don’t wait until the last moment. The most popular sessions tend to fill up pretty fast.
My presentation Meet Snoop – a Discovery Service for Java EE may be can be found in the Schedule Builder by searching for CON1615. Add it to your schedule so that you are sure to get a seat. It may fill up…
Here is an article about my favorite NetBeans features published on DZone.
http://netbeans.dzone.com/5-favorite-netbeans-features-ivargrimstad
If you have tried adding a recent nightly build of GlassFish 4.1 to the server configurations in NetBeans, you may have come across the following problem:
The solution is as follows:
cd glassfish4/glassfish/lib/install/applications/__admingui/WEB-INF/lib/ mv console-core-4.2-SNAPSHOT.jar console-4.1.jar
This deficiency of the NetBeans server plugin is covered by Bug #250165
