Hi Everyone, In preparation for WildFly 12 Final, CR1 is now available for build testing: http://wildfly.org/downloads/ Provided no blocking issues are discovered we will be releasing Final shortly. WildFly 12 is the first release in our new quarterly delivery model. The most significant feature is delivery of new EE8 capabilities. As mentioned during the original 12 announcement, we are delivering EE8 functionality incrementally, as opposed to waiting for a big bang. WildFly 12 includes Servlet 4, JAX-RS 2.1, CDI 2.0, Bean Validation 2.0, JSF 2.3, JSON-B, JSON-P 1.1, and Javamail 1.6. By default WildFly 12 runs in EE7 mode, but you can enable EE8 variants of the standard by starting the server with the special parameter “-Dee8.preview.mode=true”. Thanks! -Jason _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

Hi Jaikiran, Thanks for the feedback! In our new release model, we are trying to be as close to timeboxed as we can, so the only thing that holds back a Final is a blocker level issue. Since the issues you reference occur in specific circumstances and have workarounds, they did not appear to meet that level of severity. Unfortunately this means that some issues like this will miss the train, but luckily the wait with our timeboxed model isn’t too long, and if something heavily affects the community in a way that really can’t wait we could always do an interim release. Thanks, -Jason > On Feb 28, 2018, at 10:52 PM, Jaikiran Pai <jai.forums2013(a)gmail.com&gt; wrote: > > Hi Jason, > > The past few weeks, there have been multiple reports in the forums and in the JIRA related to remote EJB invocations (especially over HTTP) that seems to be failing due to some of the bugs in our remote EJB libraries. From what I see, most of them should be resolved in 12.0.0.CR1 that's released. However, I think there's at least one or two issues (still being discussed in the forums and JIRA[1] [2]) which I suspect are bugs in either WildFly itself or one of our libraries. > > Related to those, I believe, the fix in this PR https://github.com/wildfly/wildfly/pull/10929 which is currently open, is an important one in context of 12.0 Final release. I haven't had the chance to check if this PR would solve the rest of the issues, but at least from the looks of it, it's an important fix in itself. > > I think we should include that fix in 12.0.0.Final. > > [1] https://issues.jboss.org/browse/WFLY-9896 > > [2] https://developer.jboss.org/message/980718#980718 > > -Jaikiran > > On 27/02/18 9:02 AM, Jason Greene wrote: >> Hi Everyone, >> >> In preparation for WildFly 12 Final, CR1 is now available for build testing: >> http://wildfly.org/downloads/ >> >> Provided no blocking issues are discovered we will be releasing Final shortly. >> >> WildFly 12 is the first release in our new quarterly delivery model. The most significant feature is delivery of new EE8 capabilities. As mentioned during the original 12 announcement, we are delivering EE8 functionality incrementally, as opposed to waiting for a big bang. WildFly 12 includes Servlet 4, JAX-RS 2.1, CDI 2.0, Bean Validation 2.0, JSF 2.3, JSON-B, JSON-P 1.1, and Javamail 1.6. >> >> By default WildFly 12 runs in EE7 mode, but you can enable EE8 variants of the standard by starting the server with the special parameter “-Dee8.preview.mode=true”. >> >> Thanks! >> >> -Jason >> >> >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev