WildFly brings you the latest innovations in application server technology, and
- is developer-friendly with fast start-up, extensive tooling, and quickstarts
- supports Java EE standards and beyond
- is ideal for running in cloud environments where every cycle matters
WildFly 8 brings:
- Java EE 7 support: This means all the latest and greatest technologies such as WebSocket/JSR 356, Batch Processing/JSR 352, JSON-P/JSR 353, Concurrency Utilities/JSR 236, JAX-RS 2.0/JSR 339, JMS 2.0/JSR 343, and all others from the platform are now available in WildFly.
- New high performance web server (Undertow): A flexible performant web server written in java, providing both true blocking and non-blocking API’s based on NIO. It has the ability to scale to a million connections and has impressive numbers on throughput. It also allows us to add support for modern security standards. And since web server is one of the most critical pieces of an application server, writing it a fresh allows us to provide the best possible performance and memory efficiency.
- Greatly reduced port usage: Nearly all protocols are multiplexed over two ports: 8080 for application and 9990 for management. This is a very useful feature in high-density environments such as OpenShift.
- Role based access control (RBAC) and Audit logging: RBAC is the ability to restrict access to system or certain portions of it to authorized users. Seven pre-defined roles can be used to map permissions to users and groups to different parts of management infrastructure. Audit logging allows logging for of operations affecting the management model. RBAC and Audit Logging certainly makes the server enterprise grade.
- Patching infrastructure: Infrastructure to support the application of patches to an existing install has been implemented. This capability allows for a remote client to install and rollback new static modules and binary files using the WildFly management protocol.
Read the official release announcement which provides a comprehensive list of features (lots of cool ones!) and check out the resources page (books, videos, tutorials, docs, etc).
How do you reach us ?
- wildfly.org
- WildFly Forums or Mailing List (archive)
- @WildFlyAS
- File bugs in issue tracker
- IRC
Download now (zip) and get started!
- Tweet
-
“RBAC, Audit Logging and Patching Infrastructure” are not innovative at all. WebLogic, and even WebSphere have these features for years.
But anyway, I am happy to see WildFly community and the Red Hat JBoss engineering team fulfilling these Operational Features gap. It clearly shows that Application Servers are far from being commodities, and there is a lot of space for improvements and competition.
For customers, this move is excellent. This shows that being developer-friendly is just one of the many requirements customers rely on to choose one product over another.
More features from WildFly for Production Environment operators will definitely help to drive forward the app server market.
Hi Arun,
I followed the steps in http://wildfly.org/news/2014/02/06/GlassFish-to-WildFly-migration/ to migrate my Java EE app from Glassfish to WildFly, I loaded the MySQL database driver, configured the data sources, changed my persistence.xml so it works with Hibernate instead of Eclipselink, installed and configured the WildFly plugin in my Netbeans 7.4, and it builds with no problems, but if instead I click on “run”, I get this:
Deployment error.
See the server log for details.
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:294)
at org.netbeans.modules.maven.j2ee.ExecutionChecker.performDeploy(ExecutionChecker.java:205)
at org.netbeans.modules.maven.j2ee.ExecutionChecker.executionResult(ExecutionChecker.java:123)
at org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:235)
at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:153)
Caused by: java.lang.NullPointerException
at org.netbeans.modules.javaee.wildfly.config.WildflyDatasourceManager.deployDatasources(WildflyDatasourceManager.java:139)
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.deployDatasources(ServerInstance.java:750)
at org.netbeans.modules.j2ee.deployment.impl.DeploymentHelper.deployDatasources(DeploymentHelper.java:115)
at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:239)
… 4 more
It mentions to check the server log, I went into standalone/log/server.log and nothing, I don’t know what to do and looked it up in Google and got nothing, any thoughts?
Raul,
NetBeans/WildFly plugin works with either NetBeans nightly (http://bits.netbeans.org/download/trunk/nightly/latest/) or just released RC (https://netbeans.org/community/releases/80/). Can you try that ?
Hi Arun,
Thanks for the quick reply, I installed the latest Netbeans, but when I open the plugins window, it tries to pull the list of plugins from deadlock.netbeans.org but it times out all the time, for the moment it’s not possible for me to install the WildFly plugin, as soon as I can I’ll let you know if it worked,
Thanks so much for the help, you’re awesome!
Raul,
Seems like the WildFly plugin is not available by default in NetBeans RC1.
http://blog.arungupta.me/2013/12/netbeans8-and-wildfly8-techtip-6/ (towards the end) gives a workaround on how to install on a non-nightly build. In the meanwhile, I’m also following up with NetBeans team on a proper fix.