[wildfly-dev] Re: Changes coming to WildFly
Good question.
I'd like to be able to support core profile in some way, but I'm not sure
if something like a new standard config "standalone-core.xml" makes sense,
vs just having appropriate Galleon layers to make it easy to compose a
server with the profile.
Do you all foresee the proposed adaptor for portable extensions as being
something that could be integrated in WF? If not would supporting full CDI
prevent certification as a Core Profile compliant?
On Tue, Sep 28, 2021 at 11:09 AM Scott Stark <sstark(a)redhat.com> wrote:
Brian, do you envision that Wildfly would support a Core profile
configuration for EE10? Weld will support the CDI Lite specification, but
it will run with an adaptor for portable extensions that
downgrades/restricts the allowed behavior to Lite extension (Ladislav,
Matej, correct me if I'm wrong here) that may not be ideal.
On Mon, Sep 27, 2021 at 2:11 PM Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
> There are a lot of changes coming in WildFly as we move on from legacy
> security, pivot toward Jakarta EE 10 and the jakarta.* package namespace,
> and keep up with progress in Java SE. I've blogged about how I see things
> changing in WildFly over the next few releases. See
>
> https://www.wildfly.org/news/2021/09/27/WildFly-Changes/
>
> I'd love to hear your thoughts and questions about all of this!
>
> Best regards,
> Brian Stansberry
> Project lead -- WildFly
> He/Him/His
>
> _______________________________________________
> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His
Attachments:
- attachment.html (text/html — 3.9 KB)