Awesome :), so let's release now we support java 16 OOTB :)

about the config: the reason it is there is not only jakarta - even if it
triggers it - but all cases where the original jar package is forbidden,
can be endorsed lib on java 8, some validated package (with some 3rd party
lib), some particular native libs (now we can run libs as .so) and so on.
So think it makes sense to keep it, in particular because its cost is not
very high and even from a strict jvm point of view we are incomplete (don't
forget now the jdk uses jdk.xxx to dev early features user can rely on and
we totally don't cover this case OOTB). So overall: this flag is intended
to be used ;). Longer term we can desire to make it a real SPI - the flag
moving to the default impl - to control the proxy package+name and ease the
"defineclass" but right  now it is a bit overkill, let's wait java XX which
locks even more the JVM ;).

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>


Le mer. 17 mars 2021 à 01:01, David Blevins <david.blev...@gmail.com> a
écrit :

> > On Mar 16, 2021, at 4:56 PM, David Blevins <david.blev...@gmail.com>
> wrote:
> >
> > The results after the OWB upgrade and prior to this weekend's changes
> were less than 10k passing.
>
> For clarity, the reason things worked before the OWB upgrade is we had
> AbstractProxyFactory patched.  I deleted that after Mark upgraded us to the
> main branch:
>
>  -
> https://github.com/apache/tomee-jakarta/commit/8883f220104c45be102f4dc339956a09a3ff6e72
>
> Now it appears we don't need a patch or a flag which is very very awesome!
>
>
> -David
>
>

Reply via email to