Skip to content

The Eclipse MicroProfile version 1.1 has been released and builds upon the version 1.0 release by adding support for the Configuration API.

With the inclusion of the new Configuration API, Eclipse Microprofile, whose tag line is "Optimizing Enterprise Java for a microservices architecture", now supports the following APIs

  1. Configuration 1.0
  2. CDI 1.2
  3. JSON-P 1.0
  4. JAX-RS 2.0.1

The full specification for this release can be downloaded from here.

There is a vast amount of Developer Resources available around Eclipse MicroProfile including sample code and online resources available on the project's site. This is worth reading for those new to MicroProfile, as is the MicroProfile site at

The WildFly team have announced that WildFly 11 Beta 1 is now available. This release is now feature complete.

The key highlights of WildFly 11 Beta 1 are:

  • New Security Infrastructure - Elytron
  • Simplification of JNDI and EJB invocation
  • HTTP/2 support
  • Out of the box load balancer configuration

Of these changes, the most significant is the Elytron security system.

Elytron offers a centralised security framework that can be used both by applications deployed to the application server and by the application server itself, thus providing a consistent approach to security for WildFly 11 users. Elytron covers both authentication and authorization.

WildFly 11 Beta 1 can be downloaded directly from

What are your thoughts on this new Beta? How does it compare to previous version of WildFly that you've used? Get involved in the community and leave your thoughts below.

I’ve just taken my first steps in EJB3 and started writing some small sample applications so that I can get up to speed on it.

I’ve been doing J2EE for some time now so I thought I’d have a look at the new EJB 3 stuff and see how it differs. I’m a fan of JBoss, which provides a version of EJB3 on JBoss 4.0.3RC1. The EJB3 support can also be ported to run on JBoss 4.0.2.

Installing JBoss with EJB3 support is a doddle. I used the webstart installer on the JBoss website and installation proceeded smoothly without any problems. During the installation, you are asked which configuration of JBoss you want (all, default, ejb3 etc.). Both the all and ejb3 configurations provide EJB3 support.

So far, I’ve primarily been looking at Session beans. I’m impressed at the lack of verbose XML that needs to be written to deploy the beans (i.e. there was none!). The lack of boilerplate code required to develop these beens is very impressive, in fact my ant script was by far the most complex thing in my sample project.

I’ll post some more comments as I delve deeper, but so far I’m impressed and I think EJB3 is a large leap forwards in J2EE.

NetBeans 4.1 has built in support for Sun App Server and Tomcat 5.5. There is also a Server Plugins project for NB that adds support for JBoss 4, WebLogic 9 and WebSphere 6. The server plugins project is currently classified as experimental.

Currently the only way to try these plugins is to build NB and the required plugins – you can only download the source for them at the moment. Downloading and building is a easy process, albeit rather lengthy. Full details are given on the server plugins home page, but basically to download from CVS and build on Windows you need to do the following.

rem Create a directory to store and build NB in.
mkdir netbeans
cd netbeans

rem Setup CVS

rem login to CVS - no password required.
cvs login

rem download NB relase 4.1 source
cvs -z 6 co -r release41 -P stable

rem download server plugins source
cvs -z 6 co -P serverplugins

rem build NB
cd nbbuild

rem build JBoss plugin
rem change into the weblogic9 or websphere6 directories
rem and run ant to build these plugins.
cd ../serverplugins/jboss4

Once this is all done, there should be a netbeans/bin directory from which you can run the freshly build NB with the new server modules.

Starting up NB and selecting Tools – Server Manager allows you to now add a server instance for JBoss, WebLogic or WebSphere.

I tried building the JBoss 4 plugin and it integrated correctly with my JBoss 4.0.2 installation. I was able to create an enterprise app from within NB and deploy and run it successfully to JBoss 4 – all from within NB.