Rewiring and improving the core of the application server, making it a lean mean machine of isolated modules, concurrent loading and all out greatness. On top of that they took in the best of breed components from JBoss.org and other Java middleware communities and created the best Java EE Web Profile compatible server I’ve used.
But the team did not stand still - since AS 7.0 they have been working on improving the server and just last week released AS 7.1.
Listening to all of the community feedback that have been given, fixing bugs and implementing features that just did not make it into AS 7.0.
The next three days I’ll post a blog a day about each of three features which I have had a personal interest in making it into AS 7.1 and the upcoming JBoss Enterprise Application Platform (EAP) 6: Deployable datasources, Developer Friendly Security & Quickstarts Frenzy!
AS 7.1 and JBoss Tools M5
But before I do then just let me say that if you are using JBoss Tools 3.3 M5 then it will work with AS 7.1 just fine except for one small caveat.
If you open the server editor for a server configured to work with AS 7.1 it will complain about a missing server port. This happens because AS 7.1 introduced using a system property default value instead of a concrete port number in its XML configuration which M5 does not parse correctly. It will thus show an empty field and mark it is an error.
The server will happily still start/stop etc. if you are using defaults, but if you don’t like to see the error in the server editor or are using non-default values then to fix this simply uncheck “Automatically Detect” and type in the port value manually (i.e. 9999).
This glitch is fixed in the nightly builds of JBoss Tools 3.3 Beta1 which we are working on making stable and available anytime soon.