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 ) which I
suspect are bugs in either WildFly itself or one of our libraries.
Related to those, I believe, the fix in this PR
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.
On 27/02/18 9:02 AM, Jason Greene wrote:
In preparation for WildFly 12 Final, CR1 is now available for build testing:
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”.
wildfly-dev mailing list