Re: [wildfly-dev] 8.0.0.Beta1 released

From: "Jason Greene" <jason.greene(a)redhat.com&gt; To: wildfly-dev(a)lists.jboss.org Sent: Monday, October 7, 2013 12:20:03 PM Subject: [wildfly-dev] 8.0.0.Beta1 released Hello Everyone, As many of you have already noticed, on Friday we released our first Beta of WildFly 8. This is a significant release because all major features on the 8 plan have been implemented; most notably all user facing Java EE7 APIs. As always you can download the latest release here: http://wildfly.org/download Our overall status of the primary features follows. You can find this information, along with additional details in the official release notes: https://community.jboss.org/wiki/WildFly800Beta1ReleaseNotes Java EE7 ======== Java EE7 offers applications several productivity improving capabilities including support for the modern web, batch processing, simplified concurrent task processing, and improvements in dependency injection. At this point all user facing EE7 APIs have been implemented! Aside from achieving compliance certification, the only remaining work is to implement a few updates in the security integration SPIs, JASPIC and JACC. High Performance Web Server (Undertow.io) ========================================= Undertow, the new cutting-edge web server in WildFly 8 is designed for maximum throughput and scalability, including environments with over a million connections. It supports non-blocking and blocking handlers, traditional and asynchronous servlets, and JSR-356 web socket handlers. It is highly customizable, with the ability for applications to implement nearly anything from dynamic request routing to custom protocols. It can also function as a very efficient, pure non-blocking reverse proxy, allowing WildFly to delegate to other web servers with minimal impact to running applications. Undertow has been fully integrated for several releases now. This release finalizes the key features of this integration with the addition of reverse proxy support. Port Reduction ============== An important goal of WildFly 8 was to greatly reduce the number of ports used by multiplexing protocols over HTTP using HTTP Upgrade. This is a big benefit to cloud providers (such as OpenShift) who run hundreds to thousands of instances on a single server. Our default configuration now only has three ports, and will become two ports by final. We decided to preserve the original native management port for this Beta release to give those using legacy clients time to update before the final release.The native management port, 9999, is deprecated and will be removed by final. Port Bound Interface Protocols ---- --------------- --------- 9990 management HTTP/JSON Management HTTP Upgraded Remoting - (Native Management & JMX) Web Administration Console 8080 application HTTP (Servlet, JAX-RPC) Web Sockets HTTP Upgraded Remoting (EJB Invocation, Remote JNDI) 9999 (deprecated) management Remoting - Native Management Management Role Based Access Control (RBAC) & Auditing ====================================================== WildFly can now support organizations with separated management responsibilities and restrictions. Roles represent different sets of permissions such as runtime operation execution, configuration areas that can read or written, and the ability to audit changes and manage users. In addition a new restricted audit log can be enabled including the ability to offload to a secure syslog server. Patching ======== The 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. -- Jason T. Greene WildFly Lead / JBoss EAP Platform Architect JBoss, a division of Red Hat _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev