From emartins at redhat.com  Mon Jun  3 10:52:00 2019
From: emartins at redhat.com (Eduardo Martins)
Date: Mon, 3 Jun 2019 15:52:00 +0100
Subject: [wildfly-dev] Updating the WildFly archetypes
In-Reply-To: <5A38A072-F4DA-4646-9A9A-2CD3234C82B8@redhat.com>
References: <2c35697c-c08e-9fbc-d824-dd036ec51dce@gmx.de>
	<582dba4b-d3eb-6b69-d1ea-544043f38c05@gmx.de>
	<CAPhbRDYS84hisLYa3DC20BWjBg_v5iL=Fk4fWhGXd3foMugOSw@mail.gmail.com>
	<b213ce6a-7b08-7c2a-64dc-f3186def802f@gmx.de>
	<de7cd83d-9076-7af5-27df-5b468aac5f39@gmx.de>
	<e9897b9a-8aca-1534-4aa8-04eac62e501f@gmx.de>
	<CAPhbRDZZ6H3N=_=wxR0tmMo7uYhbwHFEarNZEHVpgg+_bq3G1Q@mail.gmail.com>
	<1456ba90-89d2-2a6c-21bd-de109033551e@gmx.de>
	<0DC3C23D-3681-4941-B355-E2C33F5B2026@redhat.com>
	<7035b0b9-07fe-c241-8186-24a541a3fae0@gmx.de>
	<05A98C47-1EAE-41C2-8835-CD975326A3D3@redhat.com>
	<928b27fe-eaaf-1b43-1b55-6635fccc4171@gmx.de>
	<28D77BA0-E00F-4144-BF31-62CF8385EA47@redhat.com>
	<96e133b0-bf15-3b3d-9975-02cf6e3dec1e@gmx.de>
	<CALX1fhcOp7eu0AAc5CYhSzr+_GFTVnu9-MVv2wB4TFt=Vagicg@mail.gmail.com>
	<5914b66f-e9d5-b703-3295-84012220d9e1@gmx.de>
	<42a971fe-fd23-df27-c31d-9fdc6148dca7@gmx.de>
	<3a70866d-4621-514e-b329-0fa117219c45@gmx.de>
	<EE0424D8-D48B-4000-AD26-FF3419A0DEF2@redhat.com>
	<736372a6-ead3-2d3b-d9bd-cd7bc346a8de@gmx.de>
	<625CA896-F39B-4270-9D71-0CA71A44C839@redhat.com>
	<88FA5E9A-43B0-4ED6-A18B-4A370CA6CF9C@redhat.com>
	<CAPhbRDZ5x4+5cs7gdXuiy6hs-7bCvhB7FF3p=U40ziCtKkrspQ@mail.gmail.com>
	<CALX1fhfRiyp9iZkn7Tf+s35GRzcv=r8PiLVu2Uj8O6xJzLNsfw@mail.gmail.com>
	<CAPhbRDYeg+vTGrhDOgsxH+CTbkJvt5he3MiW6QM1UYZj79jQpw@mail.gmail.com>
	<5A38A072-F4DA-4646-9A9A-2CD3234C82B8@redhat.com>
Message-ID: <2A45481D-E369-4E21-BA28-C06ED259C029@redhat.com>

Wolfgang: yours and mine PRs are merged, and when WFLY 17 Final is out I will also deploy the archetype, thanks a lot for your contribution! Yet now I have to ask, do you plan to submit similar for the other old javaee archetype? :-)

Brian: yep it was just the JDK, I will deploy these too (no planned updates in such code tho)

?E

> On 16 May 2019, at 10:09, Eduardo Martins <emartins at redhat.com> wrote:
> 
> Hmm ok, maybe it just failed build due to some specific like JDK 11, will recheck that.
> 
> ?E
> 
>> On 16 May 2019, at 02:25, Brian Stansberry <brian.stansberry at redhat.com <mailto:brian.stansberry at redhat.com>> wrote:
>> 
>> These build for me.
>> 
>> They're not as out of date as I'd thought either.
>> 
>> On Fri, May 10, 2019 at 6:34 PM Eduardo Martins <emartins at redhat.com <mailto:emartins at redhat.com>> wrote:
>> If you think it?s not a small effort task then certainly agree that?s not a blocker, I look at the archetypes same way as the quickstarts,  an aggregation project, so we may take outdated/faulty ones out of build and release the working+actual ones. We may give it a thought later if it makes sense effort wise to update or drop the subsystem ones, no worries.
>> 
>> ?E
>> 
>> On Fri, 10 May 2019 at 21:46, Brian Stansberry <brian.stansberry at redhat.com <mailto:brian.stansberry at redhat.com>> wrote:
>> Is that blocking this Eduardo?
>> 
>> If not, updating those is a pretty big task and right now I don't see it happening anytime soon.
>> 
>> On Fri, May 10, 2019 at 3:10 PM Eduardo Martins <emartins at redhat.com <mailto:emartins at redhat.com>> wrote:
>> Brian, any idea what to do wrt the subsystem archetypes? ATM even build fails and most likely there is someone else better than me to look into that?
>> 
>> ?E
>> 
>> > On 7 May 2019, at 09:18, Eduardo Martins <emartins at redhat.com <mailto:emartins at redhat.com>> wrote:
>> > 
>> > Hi Wolfgang, I actually did start reviewing it, but unfortunately had to put it on hold due to unexpected blocker kind of priority tasks/issues needed to be solved asap. If nothing urgent comes I should be able to finish the review the next couple of days.
>> > 
>> > ?E
>> > 
>> >> On 6 May 2019, at 20:50, Wolfgang Knauf <wolfgang.knauf at gmx.de <mailto:wolfgang.knauf at gmx.de>> wrote:
>> >> 
>> >> Hi,
>> >> 
>> >> just want to ask for an update ;-)
>> >> 
>> >> Best regards
>> >> 
>> >> Wolfgang
>> >> 
>> >> Am 31.03.19 um 21:34 schrieb Eduardo Martins:
>> >>> I will review it, soon hopefully.
>> >>> 
>> >>> ?E
>> >>> 
>> >>>> On 31 Mar 2019, at 19:40, Wolfgang Knauf <wolfgang.knauf at gmx.de <mailto:wolfgang.knauf at gmx.de>> wrote:
>> >>>> 
>> >>>> Hi,
>> >>>> 
>> >>>> just want to ask about the state of the pull request and further steps...
>> >>>> 
>> >>>> Best regards
>> >>>> 
>> >>>> Wolfgang
>> >>>> 
>> >>>> Am 21.03.19 um 12:47 schrieb Wolfgang Knauf:
>> >>>>> OK, I sent a pull request:
>> >>>>> https://github.com/wildfly/wildfly-archetypes/pull/3 <https://github.com/wildfly/wildfly-archetypes/pull/3>
>> >>>>> 
>> >>>>> There already exists a JIRA (created by myself):
>> >>>>> https://issues.jboss.org/browse/WFLY-9703 <https://issues.jboss.org/browse/WFLY-9703> - but I cannot assign it to
>> >>>>> myself, probably because I only have the role "jira user".
>> >>>>> 
>> >>>>> Next steps (if the pull request is accepted):
>> >>>>> -someone has to release if to maven central. See the release scripts in
>> >>>>> the wildfly-archetypes root. This is probably something that has to done
>> >>>>> by the JBoss team.
>> >>>>> -the old archetype can be removed.
>> >>>>> -I will create a similar archetype replacement for
>> >>>>> "wildfly-javaee7-webapp-archetype"
>> >>>>> 
>> >>>>> 
>> >>>>> Wolfgang
>> >>>>> 
>> >>>>> Am 19.03.19 um 12:09 schrieb Wolfgang Knauf:
>> >>>>>> 
>> >>>>>> Am 18.03.19 um 22:49 schrieb Eduardo Martins:
>> >>>>>>> Webapp-ear sounds a bit weird, perhaps app-ear and app-web instead? :-)
>> >>>>>> 
>> >>>>>> 
>> >>>>>> What do you think about "wildfly-javaee-ear-archetype" and
>> >>>>>> "wildfly-javaee-web-archetype"?
>> >>>>>> 
>> >>>>>> 
>> >>>>>> Attached is a suggested integration test prototype, which shows how to
>> >>>>>> create the EAR file using ShrinkWrap. The test code will be placed in
>> >>>>>> the web module. The kitchensink quickstart had the tests in the EJB jar,
>> >>>>>> but this is the wrong place if you also want to test the web layer.
>> >>>>>> 
>> >>>>>> If this is all sound OK, I will start committing it to my git repository
>> >>>>>> and sending the pull request.
>> >>>>>> 
>> >>>>>> Best regards
>> >>>>>> 
>> >>>>>> Wolfgang
>> >>>>>> 
>> >>>>>>> 
>> >>>>>>> On Mon, 18 Mar 2019 at 21:04, Wolfgang Knauf <wolfgang.knauf at gmx.de <mailto:wolfgang.knauf at gmx.de>
>> >>>>>>> <mailto:wolfgang.knauf at gmx.de <mailto:wolfgang.knauf at gmx.de>>> wrote:
>> >>>>>>> 
>> >>>>>>>     OK, so there are two votes (mine and Eduardo's) for "create a blank
>> >>>>>>>     archetype from scratch - no demo source included" and no vote for
>> >>>>>>>     "continue using the quickstart" approach.
>> >>>>>>> 
>> >>>>>>>     Currently, I struggle with the archetype and will send a pull
>> >>>>>>>     request in
>> >>>>>>>     the next few days.
>> >>>>>>> 
>> >>>>>>>     Any objections against the name
>> >>>>>>> "wildfly-javaee-webapp-ear-archetype"
>> >>>>>>>     (which means: a new subdirectory in git)?
>> >>>>>>> 
>> >>>>>>>     If this is done, the next step would be to create a
>> >>>>>>>     "wildfly-javaee-webapp-archetype". And then someone could clean
>> >>>>>>> up the
>> >>>>>>>     old archetypes.
>> >>>>>>> 
>> >>>>>>>     I think about adding a small integration test to the web project
>> >>>>>>> which
>> >>>>>>>     shows how to create the @Deployment using ShrinkWrap? The test
>> >>>>>>> itself
>> >>>>>>>     might have only dummy code, just the creation of the EAR file is
>> >>>>>>>     relevant. This might be helpful to users.
>> >>>>>>> 
>> >>>>>>>     Best regards
>> >>>>>>> 
>> >>>>>>>     Wolfgang
>> >>>>>>> 
>> >>>>>>>     Am 18.03.19 um 09:33 schrieb Eduardo Martins:
>> >>>>>>>> The archetype sources should actually be simpler to maintain, no
>> >>>>>>>     need to ?fix? the imported QS sources... I guess for most releases
>> >>>>>>>     it would be to simply the effort to sync some dependency management
>> >>>>>>>     versions for the generated parent pom, e.g. WildFly BOMs version.
>> >>>>>>>> 
>> >>>>>>>> Wrt the html5-mobile archetype, I believe it is similar to the
>> >>>>>>>     ones you were looking at, but pointing to an old QS that was
>> >>>>>>> removed
>> >>>>>>>     at some point.
>> >>>>>>>> 
>> >>>>>>>> ?E
>> >>>>>>>> 
>> >>>>>>>>> On 13 Mar 2019, at 19:14, Wolfgang Knauf <wolfgang.knauf at gmx.de <mailto:wolfgang.knauf at gmx.de>
>> >>>>>>>     <mailto:wolfgang.knauf at gmx.de <mailto:wolfgang.knauf at gmx.de>>> wrote:
>> >>>>>>>>> 
>> >>>>>>>>> 
>> >>>>>>>>> Am 13.03.19 um 18:25 schrieb Eduardo Martins:
>> >>>>>>>>>> 
>> >>>>>>>>>>> On 12 Mar 2019, at 19:12, Wolfgang Knauf
>> >>>>>>>     <wolfgang.knauf at gmx.de <mailto:wolfgang.knauf at gmx.de> <mailto:wolfgang.knauf at gmx.de <mailto:wolfgang.knauf at gmx.de>>> wrote:
>> >>>>>>>>>>> 
>> >>>>>>>>>>> Hi Eduardo,
>> >>>>>>>>>>> 
>> >>>>>>>>>>> Am 12.03.19 um 08:58 schrieb Eduardo Martins:
>> >>>>>>>>>>>> Hi Wolfgang, the kitchensink QS truly depends on the QS
>> >>>>>>>     parent pom (dependency management, plugins, etc.), which means that
>> >>>>>>>     if we replace it with a ?local? parent pom then, for each release,
>> >>>>>>>     we need to sync manually such parents poms content? I don?t see any
>> >>>>>>>     issue with using QS parent pom, it seems that those archetypes were
>> >>>>>>>     designed to generate clones of specific quickstarts with just
>> >>>>>>>     different Maven GAVs. Have you tried to install the SNAPSHOT
>> >>>>>>>     versioned QS parent first (mvn install -N at QS repo root), or
>> >>>>>>> use a
>> >>>>>>>     tag such as 16.0.0.Final, which parent was released to Maven,
>> >>>>>>>     instead of pointing to QS master branch ?
>> >>>>>>>>>>>> Honestly I?m not sure this kind of app archetype is of much
>> >>>>>>>     interest as it is, mostly due to the app's complexity, probably
>> >>>>>>>     would be more helpful almost ?empty? apps, but if the idea is to
>> >>>>>>>     have a QS clone tool then perhaps a single generic archetype for
>> >>>>>>>     that would make more sense. I?m open to QS source changes needed to
>> >>>>>>>     be friendly with such archetype :-)
>> >>>>>>>>>>>> ?E
>> >>>>>>>>>>> 
>> >>>>>>>>>>> 
>> >>>>>>>>>>> I agree that the "wildfly-javaee7-webapp-ear-archetype"
>> >>>>>>>     archetype is not really useful. But based on this archetype, an
>> >>>>>>>     empty archetype "wildfly-javaee7-webapp-ear-blank-archetype" is
>> >>>>>>>     generated, which consists of all necessary pom.xml files and some
>> >>>>>>>     deployment descriptor stubs. And *this* archetype is the reason why
>> >>>>>>>     I started working on it: it is a good starting point for a new
>> >>>>>>>     JavaEE application which already defines all necessary components.
>> >>>>>>>>>>> 
>> >>>>>>>>>>> I am willing to maintain this archetype for the next few
>> >>>>>>> years
>> >>>>>>>     and trying to release a version for each major WildFly version. As
>> >>>>>>>     suggested I would add a static root pom.xml to the archetype github
>> >>>>>>>     project which is independent of the quickstart files, as they are
>> >>>>>>>     not "standalone". This main pom.xml has to be updated for each
>> >>>>>>>     WildFly version, but all the other files still can be pulled from
>> >>>>>>>     the "KitchensinkEar" quickstart.
>> >>>>>>>>>>> 
>> >>>>>>>>>> 
>> >>>>>>>>>> Then why get any sources from QS repo, having a proper
>> >>>>>>>     do-nothing app project all locally sounds better to me, probably
>> >>>>>>>     less effort needed on every release too.
>> >>>>>>>>>> 
>> >>>>>>>>>> ?E
>> >>>>>>>>>> 
>> >>>>>>>>> 
>> >>>>>>>>> So you prefer to create a blank archetype which has no build
>> >>>>>>>>> dependencies, just containing the relevant pom.xml files and
>> >>>>>>>     maybe some
>> >>>>>>>>> required files (don't know if there are any)? And this
>> >>>>>>> archetype is
>> >>>>>>>>> updated by someone (e.g. me) each time a new major release
>> >>>>>>> is done?
>> >>>>>>>>> 
>> >>>>>>>>> Same applies to the other archetype,
>> >>>>>>>     "wildfly-javaee7-webapp-archetype?.
>> >>>>>>>>> The wildfly-archetypes project contains two more archetypes
>> >>>>>>>>> ("wildfly-html5-mobile-archetype",
>> >>>>>>>     "wildfly-subsystem-archetype"), but I
>> >>>>>>>>> did not even take a look at those.
>> >>>>>>>>> 
>> >>>>>>>>> Personally, I prefer the standalone approach, too. It means
>> >>>>>>> more
>> >>>>>>>     work to
>> >>>>>>>>> maintain it, but it is simpler ;-)
>> >>>>>>>>> 
>> >>>>>>>>> Please vote for any of those solutions ;-):
>> >>>>>>>>> a) continue pulling from KitchensinkEAR quickstart ("blank"
>> >>>>>>>     archetype
>> >>>>>>>>> and archetype with a basic project)...
>> >>>>>>>>> b) create standalone archetype (only "blank" archetype).
>> >>>>>>>>> 
>> >>>>>>>>> 
>> >>>>>>>>> Best regards
>> >>>>>>>>> 
>> >>>>>>>>> Wolfgang
>> >>>>>> 
>> >>>>>> _______________________________________________
>> >>>>>> wildfly-dev mailing list
>> >>>>>> wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
>> >>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev <https://lists.jboss.org/mailman/listinfo/wildfly-dev>
>> >>>>>> 
>> >>>> 
>> >>>> _______________________________________________
>> >>>> wildfly-dev mailing list
>> >>>> wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
>> >>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev <https://lists.jboss.org/mailman/listinfo/wildfly-dev>
>> >>> 
>> >>> 
>> >> 
>> >> _______________________________________________
>> >> wildfly-dev mailing list
>> >> wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
>> >> https://lists.jboss.org/mailman/listinfo/wildfly-dev <https://lists.jboss.org/mailman/listinfo/wildfly-dev>
>> > 
>> 
>> 
>> 
>> -- 
>> Brian Stansberry
>> Manager, Senior Principal Software Engineer
>> Red Hat
>> 
>> 
>> -- 
>> Brian Stansberry
>> Manager, Senior Principal Software Engineer
>> Red Hat
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190603/967cdd0e/attachment-0001.html 

From brian.stansberry at redhat.com  Mon Jun  3 11:05:25 2019
From: brian.stansberry at redhat.com (Brian Stansberry)
Date: Mon, 3 Jun 2019 10:05:25 -0500
Subject: [wildfly-dev] Updating the WildFly archetypes
In-Reply-To: <2A45481D-E369-4E21-BA28-C06ED259C029@redhat.com>
References: <2c35697c-c08e-9fbc-d824-dd036ec51dce@gmx.de>
	<582dba4b-d3eb-6b69-d1ea-544043f38c05@gmx.de>
	<CAPhbRDYS84hisLYa3DC20BWjBg_v5iL=Fk4fWhGXd3foMugOSw@mail.gmail.com>
	<b213ce6a-7b08-7c2a-64dc-f3186def802f@gmx.de>
	<de7cd83d-9076-7af5-27df-5b468aac5f39@gmx.de>
	<e9897b9a-8aca-1534-4aa8-04eac62e501f@gmx.de>
	<CAPhbRDZZ6H3N=_=wxR0tmMo7uYhbwHFEarNZEHVpgg+_bq3G1Q@mail.gmail.com>
	<1456ba90-89d2-2a6c-21bd-de109033551e@gmx.de>
	<0DC3C23D-3681-4941-B355-E2C33F5B2026@redhat.com>
	<7035b0b9-07fe-c241-8186-24a541a3fae0@gmx.de>
	<05A98C47-1EAE-41C2-8835-CD975326A3D3@redhat.com>
	<928b27fe-eaaf-1b43-1b55-6635fccc4171@gmx.de>
	<28D77BA0-E00F-4144-BF31-62CF8385EA47@redhat.com>
	<96e133b0-bf15-3b3d-9975-02cf6e3dec1e@gmx.de>
	<CALX1fhcOp7eu0AAc5CYhSzr+_GFTVnu9-MVv2wB4TFt=Vagicg@mail.gmail.com>
	<5914b66f-e9d5-b703-3295-84012220d9e1@gmx.de>
	<42a971fe-fd23-df27-c31d-9fdc6148dca7@gmx.de>
	<3a70866d-4621-514e-b329-0fa117219c45@gmx.de>
	<EE0424D8-D48B-4000-AD26-FF3419A0DEF2@redhat.com>
	<736372a6-ead3-2d3b-d9bd-cd7bc346a8de@gmx.de>
	<625CA896-F39B-4270-9D71-0CA71A44C839@redhat.com>
	<88FA5E9A-43B0-4ED6-A18B-4A370CA6CF9C@redhat.com>
	<CAPhbRDZ5x4+5cs7gdXuiy6hs-7bCvhB7FF3p=U40ziCtKkrspQ@mail.gmail.com>
	<CALX1fhfRiyp9iZkn7Tf+s35GRzcv=r8PiLVu2Uj8O6xJzLNsfw@mail.gmail.com>
	<CAPhbRDYeg+vTGrhDOgsxH+CTbkJvt5he3MiW6QM1UYZj79jQpw@mail.gmail.com>
	<5A38A072-F4DA-4646-9A9A-2CD3234C82B8@redhat.com>
	<2A45481D-E369-4E21-BA28-C06ED259C029@redhat.com>
Message-ID: <CAPhbRDajKjMvZSZHsQYb6_zTiN+U6uxiydA-Z18cxY4=YwGZ+A@mail.gmail.com>

Excellent!  Thank you so much Wolfgang!

On Mon, Jun 3, 2019 at 9:52 AM Eduardo Martins <emartins at redhat.com> wrote:

> Wolfgang: yours and mine PRs are merged, and when WFLY 17 Final is out I
> will also deploy the archetype, thanks a lot for your contribution! Yet now
> I have to ask, do you plan to submit similar for the other old javaee
> archetype? :-)
>
> Brian: yep it was just the JDK, I will deploy these too (no planned
> updates in such code tho)
>
> ?E
>
> On 16 May 2019, at 10:09, Eduardo Martins <emartins at redhat.com> wrote:
>
> Hmm ok, maybe it just failed build due to some specific like JDK 11, will
> recheck that.
>
> ?E
>
> On 16 May 2019, at 02:25, Brian Stansberry <brian.stansberry at redhat.com>
> wrote:
>
> These build for me.
>
> They're not as out of date as I'd thought either.
>
> On Fri, May 10, 2019 at 6:34 PM Eduardo Martins <emartins at redhat.com>
> wrote:
>
>> If you think it?s not a small effort task then certainly agree that?s not
>> a blocker, I look at the archetypes same way as the quickstarts,  an
>> aggregation project, so we may take outdated/faulty ones out of build and
>> release the working+actual ones. We may give it a thought later if it makes
>> sense effort wise to update or drop the subsystem ones, no worries.
>>
>> ?E
>>
>> On Fri, 10 May 2019 at 21:46, Brian Stansberry <
>> brian.stansberry at redhat.com> wrote:
>>
>>> Is that blocking this Eduardo?
>>>
>>> If not, updating those is a pretty big task and right now I don't see it
>>> happening anytime soon.
>>>
>>> On Fri, May 10, 2019 at 3:10 PM Eduardo Martins <emartins at redhat.com>
>>> wrote:
>>>
>>>> Brian, any idea what to do wrt the subsystem archetypes? ATM even build
>>>> fails and most likely there is someone else better than me to look into
>>>> that?
>>>>
>>>> ?E
>>>>
>>>> > On 7 May 2019, at 09:18, Eduardo Martins <emartins at redhat.com> wrote:
>>>> >
>>>> > Hi Wolfgang, I actually did start reviewing it, but unfortunately had
>>>> to put it on hold due to unexpected blocker kind of priority tasks/issues
>>>> needed to be solved asap. If nothing urgent comes I should be able to
>>>> finish the review the next couple of days.
>>>> >
>>>> > ?E
>>>> >
>>>> >> On 6 May 2019, at 20:50, Wolfgang Knauf <wolfgang.knauf at gmx.de>
>>>> wrote:
>>>> >>
>>>> >> Hi,
>>>> >>
>>>> >> just want to ask for an update ;-)
>>>> >>
>>>> >> Best regards
>>>> >>
>>>> >> Wolfgang
>>>> >>
>>>> >> Am 31.03.19 um 21:34 schrieb Eduardo Martins:
>>>> >>> I will review it, soon hopefully.
>>>> >>>
>>>> >>> ?E
>>>> >>>
>>>> >>>> On 31 Mar 2019, at 19:40, Wolfgang Knauf <wolfgang.knauf at gmx.de>
>>>> wrote:
>>>> >>>>
>>>> >>>> Hi,
>>>> >>>>
>>>> >>>> just want to ask about the state of the pull request and further
>>>> steps...
>>>> >>>>
>>>> >>>> Best regards
>>>> >>>>
>>>> >>>> Wolfgang
>>>> >>>>
>>>> >>>> Am 21.03.19 um 12:47 schrieb Wolfgang Knauf:
>>>> >>>>> OK, I sent a pull request:
>>>> >>>>> https://github.com/wildfly/wildfly-archetypes/pull/3
>>>> >>>>>
>>>> >>>>> There already exists a JIRA (created by myself):
>>>> >>>>> https://issues.jboss.org/browse/WFLY-9703 - but I cannot assign
>>>> it to
>>>> >>>>> myself, probably because I only have the role "jira user".
>>>> >>>>>
>>>> >>>>> Next steps (if the pull request is accepted):
>>>> >>>>> -someone has to release if to maven central. See the release
>>>> scripts in
>>>> >>>>> the wildfly-archetypes root. This is probably something that has
>>>> to done
>>>> >>>>> by the JBoss team.
>>>> >>>>> -the old archetype can be removed.
>>>> >>>>> -I will create a similar archetype replacement for
>>>> >>>>> "wildfly-javaee7-webapp-archetype"
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> Wolfgang
>>>> >>>>>
>>>> >>>>> Am 19.03.19 um 12:09 schrieb Wolfgang Knauf:
>>>> >>>>>>
>>>> >>>>>> Am 18.03.19 um 22:49 schrieb Eduardo Martins:
>>>> >>>>>>> Webapp-ear sounds a bit weird, perhaps app-ear and app-web
>>>> instead? :-)
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> What do you think about "wildfly-javaee-ear-archetype" and
>>>> >>>>>> "wildfly-javaee-web-archetype"?
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> Attached is a suggested integration test prototype, which shows
>>>> how to
>>>> >>>>>> create the EAR file using ShrinkWrap. The test code will be
>>>> placed in
>>>> >>>>>> the web module. The kitchensink quickstart had the tests in the
>>>> EJB jar,
>>>> >>>>>> but this is the wrong place if you also want to test the web
>>>> layer.
>>>> >>>>>>
>>>> >>>>>> If this is all sound OK, I will start committing it to my git
>>>> repository
>>>> >>>>>> and sending the pull request.
>>>> >>>>>>
>>>> >>>>>> Best regards
>>>> >>>>>>
>>>> >>>>>> Wolfgang
>>>> >>>>>>
>>>> >>>>>>>
>>>> >>>>>>> On Mon, 18 Mar 2019 at 21:04, Wolfgang Knauf <
>>>> wolfgang.knauf at gmx.de
>>>> >>>>>>> <mailto:wolfgang.knauf at gmx.de>> wrote:
>>>> >>>>>>>
>>>> >>>>>>>     OK, so there are two votes (mine and Eduardo's) for "create
>>>> a blank
>>>> >>>>>>>     archetype from scratch - no demo source included" and no
>>>> vote for
>>>> >>>>>>>     "continue using the quickstart" approach.
>>>> >>>>>>>
>>>> >>>>>>>     Currently, I struggle with the archetype and will send a
>>>> pull
>>>> >>>>>>>     request in
>>>> >>>>>>>     the next few days.
>>>> >>>>>>>
>>>> >>>>>>>     Any objections against the name
>>>> >>>>>>> "wildfly-javaee-webapp-ear-archetype"
>>>> >>>>>>>     (which means: a new subdirectory in git)?
>>>> >>>>>>>
>>>> >>>>>>>     If this is done, the next step would be to create a
>>>> >>>>>>>     "wildfly-javaee-webapp-archetype". And then someone could
>>>> clean
>>>> >>>>>>> up the
>>>> >>>>>>>     old archetypes.
>>>> >>>>>>>
>>>> >>>>>>>     I think about adding a small integration test to the web
>>>> project
>>>> >>>>>>> which
>>>> >>>>>>>     shows how to create the @Deployment using ShrinkWrap? The
>>>> test
>>>> >>>>>>> itself
>>>> >>>>>>>     might have only dummy code, just the creation of the EAR
>>>> file is
>>>> >>>>>>>     relevant. This might be helpful to users.
>>>> >>>>>>>
>>>> >>>>>>>     Best regards
>>>> >>>>>>>
>>>> >>>>>>>     Wolfgang
>>>> >>>>>>>
>>>> >>>>>>>     Am 18.03.19 um 09:33 schrieb Eduardo Martins:
>>>> >>>>>>>> The archetype sources should actually be simpler to maintain,
>>>> no
>>>> >>>>>>>     need to ?fix? the imported QS sources... I guess for most
>>>> releases
>>>> >>>>>>>     it would be to simply the effort to sync some dependency
>>>> management
>>>> >>>>>>>     versions for the generated parent pom, e.g. WildFly BOMs
>>>> version.
>>>> >>>>>>>>
>>>> >>>>>>>> Wrt the html5-mobile archetype, I believe it is similar to the
>>>> >>>>>>>     ones you were looking at, but pointing to an old QS that was
>>>> >>>>>>> removed
>>>> >>>>>>>     at some point.
>>>> >>>>>>>>
>>>> >>>>>>>> ?E
>>>> >>>>>>>>
>>>> >>>>>>>>> On 13 Mar 2019, at 19:14, Wolfgang Knauf <
>>>> wolfgang.knauf at gmx.de
>>>> >>>>>>>     <mailto:wolfgang.knauf at gmx.de>> wrote:
>>>> >>>>>>>>>
>>>> >>>>>>>>>
>>>> >>>>>>>>> Am 13.03.19 um 18:25 schrieb Eduardo Martins:
>>>> >>>>>>>>>>
>>>> >>>>>>>>>>> On 12 Mar 2019, at 19:12, Wolfgang Knauf
>>>> >>>>>>>     <wolfgang.knauf at gmx.de <mailto:wolfgang.knauf at gmx.de>>
>>>> wrote:
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> Hi Eduardo,
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> Am 12.03.19 um 08:58 schrieb Eduardo Martins:
>>>> >>>>>>>>>>>> Hi Wolfgang, the kitchensink QS truly depends on the QS
>>>> >>>>>>>     parent pom (dependency management, plugins, etc.), which
>>>> means that
>>>> >>>>>>>     if we replace it with a ?local? parent pom then, for each
>>>> release,
>>>> >>>>>>>     we need to sync manually such parents poms content? I don?t
>>>> see any
>>>> >>>>>>>     issue with using QS parent pom, it seems that those
>>>> archetypes were
>>>> >>>>>>>     designed to generate clones of specific quickstarts with
>>>> just
>>>> >>>>>>>     different Maven GAVs. Have you tried to install the SNAPSHOT
>>>> >>>>>>>     versioned QS parent first (mvn install -N at QS repo root),
>>>> or
>>>> >>>>>>> use a
>>>> >>>>>>>     tag such as 16.0.0.Final, which parent was released to
>>>> Maven,
>>>> >>>>>>>     instead of pointing to QS master branch ?
>>>> >>>>>>>>>>>> Honestly I?m not sure this kind of app archetype is of much
>>>> >>>>>>>     interest as it is, mostly due to the app's complexity,
>>>> probably
>>>> >>>>>>>     would be more helpful almost ?empty? apps, but if the idea
>>>> is to
>>>> >>>>>>>     have a QS clone tool then perhaps a single generic
>>>> archetype for
>>>> >>>>>>>     that would make more sense. I?m open to QS source changes
>>>> needed to
>>>> >>>>>>>     be friendly with such archetype :-)
>>>> >>>>>>>>>>>> ?E
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> I agree that the "wildfly-javaee7-webapp-ear-archetype"
>>>> >>>>>>>     archetype is not really useful. But based on this
>>>> archetype, an
>>>> >>>>>>>     empty archetype
>>>> "wildfly-javaee7-webapp-ear-blank-archetype" is
>>>> >>>>>>>     generated, which consists of all necessary pom.xml files
>>>> and some
>>>> >>>>>>>     deployment descriptor stubs. And *this* archetype is the
>>>> reason why
>>>> >>>>>>>     I started working on it: it is a good starting point for a
>>>> new
>>>> >>>>>>>     JavaEE application which already defines all necessary
>>>> components.
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>> I am willing to maintain this archetype for the next few
>>>> >>>>>>> years
>>>> >>>>>>>     and trying to release a version for each major WildFly
>>>> version. As
>>>> >>>>>>>     suggested I would add a static root pom.xml to the
>>>> archetype github
>>>> >>>>>>>     project which is independent of the quickstart files, as
>>>> they are
>>>> >>>>>>>     not "standalone". This main pom.xml has to be updated for
>>>> each
>>>> >>>>>>>     WildFly version, but all the other files still can be
>>>> pulled from
>>>> >>>>>>>     the "KitchensinkEar" quickstart.
>>>> >>>>>>>>>>>
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> Then why get any sources from QS repo, having a proper
>>>> >>>>>>>     do-nothing app project all locally sounds better to me,
>>>> probably
>>>> >>>>>>>     less effort needed on every release too.
>>>> >>>>>>>>>>
>>>> >>>>>>>>>> ?E
>>>> >>>>>>>>>>
>>>> >>>>>>>>>
>>>> >>>>>>>>> So you prefer to create a blank archetype which has no build
>>>> >>>>>>>>> dependencies, just containing the relevant pom.xml files and
>>>> >>>>>>>     maybe some
>>>> >>>>>>>>> required files (don't know if there are any)? And this
>>>> >>>>>>> archetype is
>>>> >>>>>>>>> updated by someone (e.g. me) each time a new major release
>>>> >>>>>>> is done?
>>>> >>>>>>>>>
>>>> >>>>>>>>> Same applies to the other archetype,
>>>> >>>>>>>     "wildfly-javaee7-webapp-archetype?.
>>>> >>>>>>>>> The wildfly-archetypes project contains two more archetypes
>>>> >>>>>>>>> ("wildfly-html5-mobile-archetype",
>>>> >>>>>>>     "wildfly-subsystem-archetype"), but I
>>>> >>>>>>>>> did not even take a look at those.
>>>> >>>>>>>>>
>>>> >>>>>>>>> Personally, I prefer the standalone approach, too. It means
>>>> >>>>>>> more
>>>> >>>>>>>     work to
>>>> >>>>>>>>> maintain it, but it is simpler ;-)
>>>> >>>>>>>>>
>>>> >>>>>>>>> Please vote for any of those solutions ;-):
>>>> >>>>>>>>> a) continue pulling from KitchensinkEAR quickstart ("blank"
>>>> >>>>>>>     archetype
>>>> >>>>>>>>> and archetype with a basic project)...
>>>> >>>>>>>>> b) create standalone archetype (only "blank" archetype).
>>>> >>>>>>>>>
>>>> >>>>>>>>>
>>>> >>>>>>>>> Best regards
>>>> >>>>>>>>>
>>>> >>>>>>>>> Wolfgang
>>>> >>>>>>
>>>> >>>>>> _______________________________________________
>>>> >>>>>> wildfly-dev mailing list
>>>> >>>>>> wildfly-dev at lists.jboss.org
>>>> >>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >>>>>>
>>>> >>>>
>>>> >>>> _______________________________________________
>>>> >>>> wildfly-dev mailing list
>>>> >>>> wildfly-dev at lists.jboss.org
>>>> >>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >>>
>>>> >>>
>>>> >>
>>>> >> _______________________________________________
>>>> >> wildfly-dev mailing list
>>>> >> wildfly-dev at lists.jboss.org
>>>> >> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >
>>>>
>>>>
>>>
>>> --
>>> Brian Stansberry
>>> Manager, Senior Principal Software Engineer
>>> Red Hat
>>>
>>
>
> --
> Brian Stansberry
> Manager, Senior Principal Software Engineer
> Red Hat
>
>
>
>

-- 
Brian Stansberry
Manager, Senior Principal Software Engineer
Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190603/7e60d89e/attachment-0001.html 

From wolfgang.knauf at gmx.de  Mon Jun  3 15:36:40 2019
From: wolfgang.knauf at gmx.de (Wolfgang Knauf)
Date: Mon, 3 Jun 2019 21:36:40 +0200
Subject: [wildfly-dev] Updating the WildFly archetypes
In-Reply-To: <CAPhbRDajKjMvZSZHsQYb6_zTiN+U6uxiydA-Z18cxY4=YwGZ+A@mail.gmail.com>
References: <2c35697c-c08e-9fbc-d824-dd036ec51dce@gmx.de>
	<928b27fe-eaaf-1b43-1b55-6635fccc4171@gmx.de>
	<28D77BA0-E00F-4144-BF31-62CF8385EA47@redhat.com>
	<96e133b0-bf15-3b3d-9975-02cf6e3dec1e@gmx.de>
	<CALX1fhcOp7eu0AAc5CYhSzr+_GFTVnu9-MVv2wB4TFt=Vagicg@mail.gmail.com>
	<5914b66f-e9d5-b703-3295-84012220d9e1@gmx.de>
	<42a971fe-fd23-df27-c31d-9fdc6148dca7@gmx.de>
	<3a70866d-4621-514e-b329-0fa117219c45@gmx.de>
	<EE0424D8-D48B-4000-AD26-FF3419A0DEF2@redhat.com>
	<736372a6-ead3-2d3b-d9bd-cd7bc346a8de@gmx.de>
	<625CA896-F39B-4270-9D71-0CA71A44C839@redhat.com>
	<88FA5E9A-43B0-4ED6-A18B-4A370CA6CF9C@redhat.com>
	<CAPhbRDZ5x4+5cs7gdXuiy6hs-7bCvhB7FF3p=U40ziCtKkrspQ@mail.gmail.com>
	<CALX1fhfRiyp9iZkn7Tf+s35GRzcv=r8PiLVu2Uj8O6xJzLNsfw@mail.gmail.com>
	<CAPhbRDYeg+vTGrhDOgsxH+CTbkJvt5he3MiW6QM1UYZj79jQpw@mail.gmail.com>
	<5A38A072-F4DA-4646-9A9A-2CD3234C82B8@redhat.com>
	<2A45481D-E369-4E21-BA28-C06ED259C029@redhat.com>
	<CAPhbRDajKjMvZSZHsQYb6_zTiN+U6uxiydA-Z18cxY4=YwGZ+A@mail.gmail.com>
Message-ID: <b3b504ae-f6b7-efc2-f134-acfff9926d12@gmx.de>

Thanks for the deploy, Eduardo!

If you consider it reasonable I will create an archetype for "web app
only", similar to the old "wildfly-javaee7-webapp-archetype".
But I will probably need a few weeks...

What happens to the old archetype
"wildfly-javaee7-webapp-ear-archetype"? It could be deleted, as it does
not build anyway. It might be relevant only for research.

Best regards

Wolfgang



Am 03.06.19 um 17:05 schrieb Brian Stansberry:
> Excellent!? Thank you so much Wolfgang!
>
> On Mon, Jun 3, 2019 at 9:52 AM Eduardo Martins <emartins at redhat.com
> <mailto:emartins at redhat.com>> wrote:
>
>     Wolfgang: yours and mine PRs are merged, and when WFLY 17 Final is
>     out I will also deploy the archetype, thanks a lot for your
>     contribution! Yet now I have to ask, do you plan to submit similar
>     for the other old javaee archetype? :-)
>
>     Brian: yep it was just the JDK, I will deploy these too (no planned
>     updates in such code tho)
>
>     ?E
>
>>     On 16 May 2019, at 10:09, Eduardo Martins <emartins at redhat.com
>>     <mailto:emartins at redhat.com>> wrote:
>>
>>     Hmm ok, maybe it just failed build due to some specific like JDK
>>     11, will recheck that.
>>
>>     ?E
>>
>>>     On 16 May 2019, at 02:25, Brian Stansberry
>>>     <brian.stansberry at redhat.com
>>>     <mailto:brian.stansberry at redhat.com>> wrote:
>>>
>>>     These build for me.
>>>
>>>     They're not as out of date as I'd thought either.
>>>
>>>     On Fri, May 10, 2019 at 6:34 PM Eduardo Martins
>>>     <emartins at redhat.com <mailto:emartins at redhat.com>> wrote:
>>>
>>>         If you think it?s not a small effort task then certainly
>>>         agree that?s not a blocker, I look at the archetypes same way
>>>         as the quickstarts, ?an aggregation project, so we may take
>>>         outdated/faulty ones out of build and release the
>>>         working+actual ones. We may give it a thought later if it
>>>         makes sense effort wise to update or drop the subsystem ones,
>>>         no worries.
>>>
>>>         ?E
>>>


From ropalka at redhat.com  Mon Jun  3 18:03:25 2019
From: ropalka at redhat.com (Richard Opalka)
Date: Tue, 4 Jun 2019 00:03:25 +0200
Subject: [wildfly-dev] JDK 13 - Early Access build 23 is available
In-Reply-To: <f30aa6f0-4f67-fb65-3033-63754e1ddd0a@oracle.com>
References: <f30aa6f0-4f67-fb65-3033-63754e1ddd0a@oracle.com>
Message-ID: <CABSyOEHDYMFXmZkEpm5Hyu5xwKXmXW_ijJHSoDc1jF0KkPiBgQ@mail.gmail.com>

Hi Rory,

   WildFly community application server works like a charm on JDK 13 EA 23

Richard

On Fri, May 31, 2019 at 8:32 AM Rory O'Donnell <rory.odonnell at oracle.com>
wrote:

> Hi David & Richard,
> *OpenJDK builds  *- JDK 13 - Early Access build 23 is available at
> http://jdk.java.net/13/
>
>
>    - These early-access , open-source builds are provided under the
>    - GNU General Public License, version 2, with the Classpath Exception
>       <http://openjdk.java.net/legal/gplv2+ce.html>.
>    - Changes in this build
>    <http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-13%2B22%22%3A%3A%22jdk-13%2B23%22-%22jdk-13%2B22%22%29&revcount=1000>
>    - Release notes [1]
>
> *Significant changes since the last availability email*
>
>    - build 23
>    - Support for Unicode 12.1 (JDK-8221431
>       <https://bugs.openjdk.java.net/browse/JDK-8221431>)
>       - Add new keytool -showinfo -tls command for displaying TLS
>       configuration information (JDK-8219861
>       <https://bugs.openjdk.java.net/browse/JDK-8219861>)
>       - build 22
>       - New methods for creating DOM and SAX factories with Namespace
>       support (JDK-8219692
>       <https://bugs.openjdk.java.net/browse/JDK-8219692>)
>       - Removal of two DocuSign root CA certificates (JDK-8223499
>       <https://bugs.openjdk.java.net/browse/JDK-8223499>)
>    - build 21
>       - JDWP support for IPv6 (JDK-8184770
>       <https://bugs.openjdk.java.net/browse/JDK-8184770>)
>       - Change the mechanism by which JDK loads the platform-specific AWT
>       Toolkit (JDK-8212700
>       <https://bugs.openjdk.java.net/browse/JDK-8212700>)
>       - Upgrade CLDR to Version 35.1 (JDK-8221432
>       <https://bugs.openjdk.java.net/browse/JDK-8221432>)
>       - xConfigurable Read Timeout for CRLs (JDK-8191808
>       <https://bugs.openjdk.java.net/browse/JDK-8191808>)
>    - Removal of two Comodo root CA certificates (JDK-8222136
>       <https://bugs.openjdk.java.net/browse/JDK-8222136>)
>
> Bug fixes for issues reported by Open Source Projects
>
>    - build 22
>       - OutOfMemory on compiling with darcula.jar in classpath (
>       JDK-8222807 <https://bugs.openjdk.java.net/browse/JDK-8222807>)
>       - build 21
>       - java -version output and certain system properties contain "null"
>       text in their values (JDK-8223695
>       <https://bugs.openjdk.java.net/browse/JDK-8223695>)
>       - build 20
>    - assert(Compile::current()->live_nodes() <
>       Compile::current()->max_node_limit()) failed: Live Node limit exceeded
>       limit (JDK-8219520
>       <https://bugs.openjdk.java.net/browse/JDK-8219520>)
>       - C2: MemNode::can_see_stored_value() ignores casts which carry
>       control dependency (JDK-8219902
>       <https://bugs.openjdk.java.net/browse/JDK-8219902>)
>       - New fix of the deadlock in sun.security.ssl.SSLSocketImpl (
>       JDK-8219991 <https://bugs.openjdk.java.net/browse/JDK-8219991>)
>
> JEP updates since last email
>
>    - JEP 350: Dynamic CDS Archives <http://openjdk.java.net/jeps/350> was
>    *Integrated*.
>    - JEP 351: ZGC: Uncommit Unused Memory
>    <http://openjdk.java.net/jeps/351> was *Integrated*.
>    - JEP 353: Reimplement the Legacy Socket API
>    <http://openjdk.java.net/jeps/353> was* Targetted* JDK 13.
>    - JEP 355: Text Blocks (Preview) <http://openjdk.java.net/jeps/355>
>     was *Proposed to target* JDK 13.
>
>
> Rgds,Rory
> [1] http://jdk.java.net/13/release-notes
>
> --
> Rgds, Rory O'Donnell
> Quality Engineering Manager
> Oracle EMEA, Dublin, Ireland
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev



-- 
--
Richard Opalka
Principal Software Engineer
Red Hat JBoss Middleware
Mobile: +420 731 186 942
E-mail: ropalka at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190604/bb983697/attachment.html 

From rory.odonnell at oracle.com  Tue Jun  4 03:39:34 2019
From: rory.odonnell at oracle.com (Rory O'Donnell)
Date: Tue, 4 Jun 2019 08:39:34 +0100
Subject: [wildfly-dev] JDK 13 - Early Access build 23 is available
In-Reply-To: <CABSyOEHDYMFXmZkEpm5Hyu5xwKXmXW_ijJHSoDc1jF0KkPiBgQ@mail.gmail.com>
References: <f30aa6f0-4f67-fb65-3033-63754e1ddd0a@oracle.com>
	<CABSyOEHDYMFXmZkEpm5Hyu5xwKXmXW_ijJHSoDc1jF0KkPiBgQ@mail.gmail.com>
Message-ID: <234057a3-a2a9-05da-4476-a8d28bd6cc7e@oracle.com>

Many thanks for the update Richard!

Rgds,Rory

On 03/06/2019 23:03, Richard Opalka wrote:
> Hi Rory,
>
> ?? WildFly community application server works like a charm on JDK 13 EA 23
>
> Richard
>
> On Fri, May 31, 2019 at 8:32 AM Rory O'Donnell 
> <rory.odonnell at oracle.com <mailto:rory.odonnell at oracle.com>> wrote:
>
>     Hi David & Richard,
>
>
>           *OpenJDK builds *- JDK 13 - Early Access build 23 is
>           available at http://jdk.java.net/13/
>
>       * These early-access , open-source builds are provided under the
>           o GNU General Public License, version?2, with the Classpath
>             Exception <http://openjdk.java.net/legal/gplv2+ce.html>.
>       * Changes in this build
>         <http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-13%2B22%22%3A%3A%22jdk-13%2B23%22-%22jdk-13%2B22%22%29&revcount=1000>
>
>       * Release notes [1]
>
>
>             *Significant changes since the last availability email*
>
>       * build 23
>           o Support for Unicode 12.1 (JDK-8221431
>             <https://bugs.openjdk.java.net/browse/JDK-8221431>)
>           o Add new keytool -showinfo -tls command for displaying TLS
>             configuration information (JDK-8219861
>             <https://bugs.openjdk.java.net/browse/JDK-8219861>)
>       * build 22
>           o New methods for creating DOM and SAX factories with
>             Namespace support (JDK-8219692
>             <https://bugs.openjdk.java.net/browse/JDK-8219692>)
>           o Removal of two DocuSign root CA certificates (JDK-8223499
>             <https://bugs.openjdk.java.net/browse/JDK-8223499>)
>       * build 21
>           o JDWP support for IPv6 (JDK-8184770
>             <https://bugs.openjdk.java.net/browse/JDK-8184770>)
>           o Change the mechanism by which JDK loads the
>             platform-specific AWT Toolkit (JDK-8212700
>             <https://bugs.openjdk.java.net/browse/JDK-8212700>)
>           o Upgrade CLDR to Version 35.1 (JDK-8221432
>             <https://bugs.openjdk.java.net/browse/JDK-8221432>)
>           o xConfigurable Read Timeout for CRLs (JDK-8191808
>             <https://bugs.openjdk.java.net/browse/JDK-8191808>)
>           o Removal of two Comodo root CA certificates (JDK-8222136
>             <https://bugs.openjdk.java.net/browse/JDK-8222136>)
>
>
>             Bug fixes for issues reported by Open Source Projects
>
>       * build 22
>           o OutOfMemory on compiling with darcula.jar in classpath
>             (JDK-8222807
>             <https://bugs.openjdk.java.net/browse/JDK-8222807>)
>       * build 21
>           o java -version output and certain system properties contain
>             "null" text in their values (JDK-8223695
>             <https://bugs.openjdk.java.net/browse/JDK-8223695>)
>       * build 20
>           o assert(Compile::current()->live_nodes() <
>             Compile::current()->max_node_limit()) failed: Live Node
>             limit exceeded limit (JDK-8219520
>             <https://bugs.openjdk.java.net/browse/JDK-8219520>)
>           o C2: MemNode::can_see_stored_value() ignores casts which
>             carry control dependency (JDK-8219902
>             <https://bugs.openjdk.java.net/browse/JDK-8219902>)
>           o New fix of the deadlock in sun.security.ssl.SSLSocketImpl
>             (JDK-8219991
>             <https://bugs.openjdk.java.net/browse/JDK-8219991>)
>
>
>             JEP updates since last email
>
>       * JEP 350: Dynamic CDS Archives
>         <http://openjdk.java.net/jeps/350>?was *Integrated*.
>       * JEP 351: ZGC: Uncommit Unused Memory
>         <http://openjdk.java.net/jeps/351>?was *Integrated*.
>       * JEP 353: Reimplement the Legacy Socket API
>         <http://openjdk.java.net/jeps/353>?was*Targetted* JDK 13.
>       * JEP 355: Text Blocks (Preview)
>         <http://openjdk.java.net/jeps/355>?was *Proposed to
>         target*?JDK 13.
>
>
>     Rgds,Rory
>
>     [1] http://jdk.java.net/13/release-notes
>
>     -- 
>     Rgds, Rory O'Donnell
>     Quality Engineering Manager
>     Oracle EMEA, Dublin, Ireland
>
>     _______________________________________________
>     wildfly-dev mailing list
>     wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>
> -- 
> --
> Richard Opalka
> Principal Software Engineer
> Red Hat JBoss Middleware
> Mobile: +420 731 186 942
> E-mail: ropalka at redhat.com <mailto:ropalka at redhat.com>
>
-- 
Rgds, Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin, Ireland

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190604/8ff661b6/attachment-0001.html 

From tdiesler at redhat.com  Wed Jun  5 04:27:30 2019
From: tdiesler at redhat.com (Thomas Diesler)
Date: Wed, 5 Jun 2019 10:27:30 +0200
Subject: [wildfly-dev] WildFly-Camel 10.1.0
Message-ID: <42CDFBC7-D959-4600-AA10-24BBBEF363D4@redhat.com>

WildFly-Camel 10.1.0 provides Camel-2.24.0 integration with WildFly-16.0.0

This is a minor update release that also adds a number of new components and data formats

Component upgrades include

Camel-2.24.0
Hawtio-2.6.0
Additional components in the supported set <http://wildfly-extras.github.io/wildfly-camel/#_camel_components> are:

xchange <https://github.com/apache/camel/blob/master/components/camel-xchange/src/main/docs/xchange-component.adoc>
ipfs <https://github.com/apache/camel/blob/master/components/camel-ipfs/src/main/docs/ipfs-component.adoc>
nsq <https://github.com/apache/camel/blob/master/components/camel-nsq/src/main/docs/nsq-component.adoc>
In addition to that, we also resolved a number of other tasks and bugs <https://github.com/wildfly-extras/wildfly-camel/blob/master/docs/Changelog.md>.

For details please see the 10.1.0 Milestone <https://github.com/wildfly-extras/wildfly-camel/issues?q=milestone%3A10.1.0>.

Enjoy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190605/3392e7b2/attachment.html 

From darran.lofthouse at jboss.com  Wed Jun  5 09:05:56 2019
From: darran.lofthouse at jboss.com (Darran Lofthouse)
Date: Wed, 5 Jun 2019 14:05:56 +0100
Subject: [wildfly-dev] Proposal to support loading an identity's attributes
	from multiple realms
Message-ID: <CAMxVf4NS7wnY5bpYtq8eRhvzx_Jr30oMdk2NneVS4k50euSH1g@mail.gmail.com>

Here is a proposal to add support for loading an identity's attributes from
multiple security realms: -

https://github.com/wildfly/wildfly-proposals/pull/205

This is being handled under the following Jira issues: -

https://issues.jboss.org/browse/ELY-1804
https://issues.jboss.org/browse/WFCORE-4447
https://issues.jboss.org/browse/WFLY-12051

Regards,
Darran Lofthouse.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190605/21b6a938/attachment.html 

From wolfgang.knauf at gmx.de  Wed Jun  5 15:42:38 2019
From: wolfgang.knauf at gmx.de (Wolfgang Knauf)
Date: Wed, 5 Jun 2019 21:42:38 +0200
Subject: [wildfly-dev] Updating the WildFly archetypes
In-Reply-To: <b3b504ae-f6b7-efc2-f134-acfff9926d12@gmx.de>
References: <2c35697c-c08e-9fbc-d824-dd036ec51dce@gmx.de>
	<28D77BA0-E00F-4144-BF31-62CF8385EA47@redhat.com>
	<96e133b0-bf15-3b3d-9975-02cf6e3dec1e@gmx.de>
	<CALX1fhcOp7eu0AAc5CYhSzr+_GFTVnu9-MVv2wB4TFt=Vagicg@mail.gmail.com>
	<5914b66f-e9d5-b703-3295-84012220d9e1@gmx.de>
	<42a971fe-fd23-df27-c31d-9fdc6148dca7@gmx.de>
	<3a70866d-4621-514e-b329-0fa117219c45@gmx.de>
	<EE0424D8-D48B-4000-AD26-FF3419A0DEF2@redhat.com>
	<736372a6-ead3-2d3b-d9bd-cd7bc346a8de@gmx.de>
	<625CA896-F39B-4270-9D71-0CA71A44C839@redhat.com>
	<88FA5E9A-43B0-4ED6-A18B-4A370CA6CF9C@redhat.com>
	<CAPhbRDZ5x4+5cs7gdXuiy6hs-7bCvhB7FF3p=U40ziCtKkrspQ@mail.gmail.com>
	<CALX1fhfRiyp9iZkn7Tf+s35GRzcv=r8PiLVu2Uj8O6xJzLNsfw@mail.gmail.com>
	<CAPhbRDYeg+vTGrhDOgsxH+CTbkJvt5he3MiW6QM1UYZj79jQpw@mail.gmail.com>
	<5A38A072-F4DA-4646-9A9A-2CD3234C82B8@redhat.com>
	<2A45481D-E369-4E21-BA28-C06ED259C029@redhat.com>
	<CAPhbRDajKjMvZSZHsQYb6_zTiN+U6uxiydA-Z18cxY4=YwGZ+A@mail.gmail.com>
	<b3b504ae-f6b7-efc2-f134-acfff9926d12@gmx.de>
Message-ID: <3f21e2cc-03e4-c8b7-5067-f84cddf42d83@gmx.de>

Hi Eduardo,

while building a "wildfly-javaee-webapp-archetype", I think I found a
small WildFly issue: you remember that you pointed me to the fact that
"beans.xml" is optional?
But when creating a blank project from my new web archetype (which
defines a "faces-config.xml", but no "beans.xml"), the attached error is
in the WildFly console. But it seems the app is deployed anyway.

The error disappears if I add e.g. an annotated EJB, or if I add a
"beans.xml".

Do you think this is a WildFly bug? Or should I add a default
"beans.xml" just to avoid this error?

I did not test it with a blank project from the EAR archetype - will do
this in the next few days.

Best regards

Wolfgang


Am 03.06.19 um 21:36 schrieb Wolfgang Knauf:
> Thanks for the deploy, Eduardo!
>
> If you consider it reasonable I will create an archetype for "web app
> only", similar to the old "wildfly-javaee7-webapp-archetype".
> But I will probably need a few weeks...
>
> What happens to the old archetype
> "wildfly-javaee7-webapp-ear-archetype"? It could be deleted, as it does
> not build anyway. It might be relevant only for research.
>
> Best regards
>
> Wolfgang
>
>
>
> Am 03.06.19 um 17:05 schrieb Brian Stansberry:
>> Excellent!? Thank you so much Wolfgang!
>>
>> On Mon, Jun 3, 2019 at 9:52 AM Eduardo Martins <emartins at redhat.com
>> <mailto:emartins at redhat.com>> wrote:
>>
>> ??? Wolfgang: yours and mine PRs are merged, and when WFLY 17 Final is
>> ??? out I will also deploy the archetype, thanks a lot for your
>> ??? contribution! Yet now I have to ask, do you plan to submit similar
>> ??? for the other old javaee archetype? :-)
>>
>> ??? Brian: yep it was just the JDK, I will deploy these too (no planned
>> ??? updates in such code tho)
>>
>> ??? ?E
>>
>>> ??? On 16 May 2019, at 10:09, Eduardo Martins <emartins at redhat.com
>>> ??? <mailto:emartins at redhat.com>> wrote:
>>>
>>> ??? Hmm ok, maybe it just failed build due to some specific like JDK
>>> ??? 11, will recheck that.
>>>
>>> ??? ?E
>>>
>>>> ??? On 16 May 2019, at 02:25, Brian Stansberry
>>>> ??? <brian.stansberry at redhat.com
>>>> ??? <mailto:brian.stansberry at redhat.com>> wrote:
>>>>
>>>> ??? These build for me.
>>>>
>>>> ??? They're not as out of date as I'd thought either.
>>>>
>>>> ??? On Fri, May 10, 2019 at 6:34 PM Eduardo Martins
>>>> ??? <emartins at redhat.com <mailto:emartins at redhat.com>> wrote:
>>>>
>>>> ??????? If you think it?s not a small effort task then certainly
>>>> ??????? agree that?s not a blocker, I look at the archetypes same way
>>>> ??????? as the quickstarts, ?an aggregation project, so we may take
>>>> ??????? outdated/faulty ones out of build and release the
>>>> ??????? working+actual ones. We may give it a thought later if it
>>>> ??????? makes sense effort wise to update or drop the subsystem ones,
>>>> ??????? no worries.
>>>>
>>>> ??????? ?E
>>>>
-------------- next part --------------
2019-06-05 21:25:06,622 INFO  [org.hibernate.orm.beans] (ServerService Thread Pool -- 123) HHH10005002: No explicit CDI BeanManager reference was passed to Hibernate, but CDI is available on the Hibernate ClassLoader.
2019-06-05 21:25:06,642 INFO  [org.hibernate.tool.schema.internal.SchemaCreatorImpl] (ServerService Thread Pool -- 123) HHH000476: Executing import script 'org.hibernate.tool.schema.internal.exec.ScriptSourceInputNonExistentImpl at 5d0c2020'
2019-06-05 21:25:06,647 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 123) Mojarra 2.3.9.SP02 f?r Kontext '/sample' wird initialisiert.
2019-06-05 21:25:06,663 ERROR [stderr] (ServerService Thread Pool -- 123) javax.faces.FacesException: Unable to find CDI BeanManager
2019-06-05 21:25:06,663 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.Version.isJsf23(Version.java:62)
2019-06-05 21:25:06,664 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.ExpressionLanguage.addELResolver(ExpressionLanguage.java:136)
2019-06-05 21:25:06,664 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.ApplicationImpl.addELResolver(ApplicationImpl.java:221)
2019-06-05 21:25:06,664 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplication.<init>(WeldApplication.java:60)
2019-06-05 21:25:06,664 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplicationFactory.getApplication(WeldApplicationFactory.java:52)
2019-06-05 21:25:06,664 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.InjectionApplicationFactory.getApplication(InjectionApplicationFactory.java:61)
2019-06-05 21:25:06,664 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:109)
2019-06-05 21:25:06,665 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.lifecycle.ClientWindowFactoryImpl.<init>(ClientWindowFactoryImpl.java:39)
2019-06-05 21:25:06,665 ERROR [stderr] (ServerService Thread Pool -- 123) 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
2019-06-05 21:25:06,665 ERROR [stderr] (ServerService Thread Pool -- 123) 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
2019-06-05 21:25:06,665 ERROR [stderr] (ServerService Thread Pool -- 123) 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
2019-06-05 21:25:06,665 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.lang.reflect.Constructor.newInstance(Unknown Source)
2019-06-05 21:25:06,665 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.lang.Class.newInstance(Unknown Source)
2019-06-05 21:25:06,665 ERROR [stderr] (ServerService Thread Pool -- 123) 	at javax.faces.FactoryFinderInstance.getImplGivenPreviousImpl(FactoryFinderInstance.java:458)
2019-06-05 21:25:06,665 ERROR [stderr] (ServerService Thread Pool -- 123) 	at javax.faces.FactoryFinderInstance.getImplementationInstance(FactoryFinderInstance.java:348)
2019-06-05 21:25:06,666 ERROR [stderr] (ServerService Thread Pool -- 123) 	at javax.faces.FactoryFinderInstance.getFactory(FactoryFinderInstance.java:200)
2019-06-05 21:25:06,666 ERROR [stderr] (ServerService Thread Pool -- 123) 	at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:279)
2019-06-05 21:25:06,666 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.FactoryConfigProcessor.lambda$verifyFactoriesExist$0(FactoryConfigProcessor.java:303)
2019-06-05 21:25:06,666 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Spliterators$ArraySpliterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,666 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.stream.ReferencePipeline$Head.forEach(Unknown Source)
2019-06-05 21:25:06,666 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist(FactoryConfigProcessor.java:297)
2019-06-05 21:25:06,666 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:211)
2019-06-05 21:25:06,666 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.lambda$initialize$0(ConfigManager.java:294)
2019-06-05 21:25:06,666 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Iterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,667 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,667 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.stream.ReferencePipeline$Head.forEach(Unknown Source)
2019-06-05 21:25:06,667 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:292)
2019-06-05 21:25:06,667 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:205)
2019-06-05 21:25:06,667 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
2019-06-05 21:25:06,667 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
2019-06-05 21:25:06,667 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
2019-06-05 21:25:06,668 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
2019-06-05 21:25:06,668 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
2019-06-05 21:25:06,668 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
2019-06-05 21:25:06,668 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,668 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,668 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,668 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,668 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,668 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
2019-06-05 21:25:06,669 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
2019-06-05 21:25:06,669 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
2019-06-05 21:25:06,669 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
2019-06-05 21:25:06,669 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.FutureTask.run(Unknown Source)
2019-06-05 21:25:06,669 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
2019-06-05 21:25:06,669 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
2019-06-05 21:25:06,669 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
2019-06-05 21:25:06,669 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
2019-06-05 21:25:06,670 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.lang.Thread.run(Unknown Source)
2019-06-05 21:25:06,670 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
2019-06-05 21:25:06,673 ERROR [stderr] (ServerService Thread Pool -- 123) javax.faces.FacesException: Unable to find CDI BeanManager
2019-06-05 21:25:06,673 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.Version.isJsf23(Version.java:62)
2019-06-05 21:25:06,673 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.ExpressionLanguage.addELResolver(ExpressionLanguage.java:136)
2019-06-05 21:25:06,674 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.ApplicationImpl.addELResolver(ApplicationImpl.java:221)
2019-06-05 21:25:06,674 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplication.<init>(WeldApplication.java:60)
2019-06-05 21:25:06,674 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplicationFactory.getApplication(WeldApplicationFactory.java:52)
2019-06-05 21:25:06,674 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.InjectionApplicationFactory.getApplication(InjectionApplicationFactory.java:61)
2019-06-05 21:25:06,674 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:109)
2019-06-05 21:25:06,675 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.lifecycle.LifecycleImpl.<init>(LifecycleImpl.java:89)
2019-06-05 21:25:06,675 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.lifecycle.LifecycleFactoryImpl.<init>(LifecycleFactoryImpl.java:59)
2019-06-05 21:25:06,675 ERROR [stderr] (ServerService Thread Pool -- 123) 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
2019-06-05 21:25:06,675 ERROR [stderr] (ServerService Thread Pool -- 123) 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
2019-06-05 21:25:06,675 ERROR [stderr] (ServerService Thread Pool -- 123) 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
2019-06-05 21:25:06,675 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.lang.reflect.Constructor.newInstance(Unknown Source)
2019-06-05 21:25:06,675 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.lang.Class.newInstance(Unknown Source)
2019-06-05 21:25:06,675 ERROR [stderr] (ServerService Thread Pool -- 123) 	at javax.faces.FactoryFinderInstance.getImplGivenPreviousImpl(FactoryFinderInstance.java:458)
2019-06-05 21:25:06,676 ERROR [stderr] (ServerService Thread Pool -- 123) 	at javax.faces.FactoryFinderInstance.getImplementationInstance(FactoryFinderInstance.java:348)
2019-06-05 21:25:06,676 ERROR [stderr] (ServerService Thread Pool -- 123) 	at javax.faces.FactoryFinderInstance.getFactory(FactoryFinderInstance.java:200)
2019-06-05 21:25:06,676 ERROR [stderr] (ServerService Thread Pool -- 123) 	at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:279)
2019-06-05 21:25:06,676 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.FactoryConfigProcessor.lambda$verifyFactoriesExist$0(FactoryConfigProcessor.java:303)
2019-06-05 21:25:06,676 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Spliterators$ArraySpliterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,676 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.stream.ReferencePipeline$Head.forEach(Unknown Source)
2019-06-05 21:25:06,676 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist(FactoryConfigProcessor.java:297)
2019-06-05 21:25:06,676 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:211)
2019-06-05 21:25:06,676 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.lambda$initialize$0(ConfigManager.java:294)
2019-06-05 21:25:06,677 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Iterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,677 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,677 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.stream.ReferencePipeline$Head.forEach(Unknown Source)
2019-06-05 21:25:06,677 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:292)
2019-06-05 21:25:06,677 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:205)
2019-06-05 21:25:06,677 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
2019-06-05 21:25:06,677 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
2019-06-05 21:25:06,677 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
2019-06-05 21:25:06,677 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
2019-06-05 21:25:06,678 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
2019-06-05 21:25:06,678 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
2019-06-05 21:25:06,678 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,678 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,678 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,678 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,678 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,678 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
2019-06-05 21:25:06,679 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
2019-06-05 21:25:06,679 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
2019-06-05 21:25:06,679 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
2019-06-05 21:25:06,679 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.FutureTask.run(Unknown Source)
2019-06-05 21:25:06,679 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
2019-06-05 21:25:06,679 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
2019-06-05 21:25:06,679 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
2019-06-05 21:25:06,679 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
2019-06-05 21:25:06,680 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.lang.Thread.run(Unknown Source)
2019-06-05 21:25:06,680 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
2019-06-05 21:25:06,681 SEVERE [javax.faces] (ServerService Thread Pool -- 123) Die Anwendung wurde bei Systemstart nicht einwandfrei initialisiert, Factory konnte nicht gefunden werden: javax.faces.lifecycle.LifecycleFactory.
2019-06-05 21:25:06,682 ERROR [stderr] (ServerService Thread Pool -- 123) java.lang.IllegalStateException: Keine Factory als Backup f?r javax.faces.lifecycle.LifecycleFactory gefunden.
2019-06-05 21:25:06,682 ERROR [stderr] (ServerService Thread Pool -- 123) 	at javax.faces.FactoryFinderInstance.notNullFactory(FactoryFinderInstance.java:524)
2019-06-05 21:25:06,682 ERROR [stderr] (ServerService Thread Pool -- 123) 	at javax.faces.FactoryFinderInstance.getFactory(FactoryFinderInstance.java:207)
2019-06-05 21:25:06,682 ERROR [stderr] (ServerService Thread Pool -- 123) 	at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:279)
2019-06-05 21:25:06,682 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:80)
2019-06-05 21:25:06,682 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.lambda$initialize$0(ConfigManager.java:294)
2019-06-05 21:25:06,682 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Iterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,683 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,683 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.stream.ReferencePipeline$Head.forEach(Unknown Source)
2019-06-05 21:25:06,683 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:292)
2019-06-05 21:25:06,683 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:205)
2019-06-05 21:25:06,683 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
2019-06-05 21:25:06,683 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
2019-06-05 21:25:06,683 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
2019-06-05 21:25:06,683 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
2019-06-05 21:25:06,683 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
2019-06-05 21:25:06,683 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
2019-06-05 21:25:06,684 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,684 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,684 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,684 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,684 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,684 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
2019-06-05 21:25:06,684 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
2019-06-05 21:25:06,684 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
2019-06-05 21:25:06,685 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
2019-06-05 21:25:06,685 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.FutureTask.run(Unknown Source)
2019-06-05 21:25:06,685 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
2019-06-05 21:25:06,685 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
2019-06-05 21:25:06,685 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
2019-06-05 21:25:06,685 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
2019-06-05 21:25:06,685 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.lang.Thread.run(Unknown Source)
2019-06-05 21:25:06,685 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
2019-06-05 21:25:06,687 ERROR [stderr] (ServerService Thread Pool -- 123) javax.faces.FacesException: Unable to find CDI BeanManager
2019-06-05 21:25:06,688 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.Version.isJsf23(Version.java:62)
2019-06-05 21:25:06,688 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.ExpressionLanguage.addELResolver(ExpressionLanguage.java:136)
2019-06-05 21:25:06,688 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.ApplicationImpl.addELResolver(ApplicationImpl.java:221)
2019-06-05 21:25:06,688 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplication.<init>(WeldApplication.java:60)
2019-06-05 21:25:06,688 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplicationFactory.getApplication(WeldApplicationFactory.java:52)
2019-06-05 21:25:06,688 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.InjectionApplicationFactory.getApplication(InjectionApplicationFactory.java:61)
2019-06-05 21:25:06,688 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.AbstractConfigProcessor.getApplication(AbstractConfigProcessor.java:113)
2019-06-05 21:25:06,689 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:242)
2019-06-05 21:25:06,689 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.lambda$initialize$0(ConfigManager.java:294)
2019-06-05 21:25:06,689 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Iterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,689 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,689 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.stream.ReferencePipeline$Head.forEach(Unknown Source)
2019-06-05 21:25:06,689 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:292)
2019-06-05 21:25:06,689 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:205)
2019-06-05 21:25:06,689 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
2019-06-05 21:25:06,689 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
2019-06-05 21:25:06,690 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
2019-06-05 21:25:06,690 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
2019-06-05 21:25:06,690 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
2019-06-05 21:25:06,690 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
2019-06-05 21:25:06,690 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,690 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,691 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,695 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,695 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,695 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
2019-06-05 21:25:06,695 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
2019-06-05 21:25:06,695 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
2019-06-05 21:25:06,695 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
2019-06-05 21:25:06,695 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.FutureTask.run(Unknown Source)
2019-06-05 21:25:06,696 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
2019-06-05 21:25:06,696 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
2019-06-05 21:25:06,696 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
2019-06-05 21:25:06,696 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
2019-06-05 21:25:06,696 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.lang.Thread.run(Unknown Source)
2019-06-05 21:25:06,696 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
2019-06-05 21:25:06,707 ERROR [stderr] (ServerService Thread Pool -- 123) javax.faces.FacesException: Unable to find CDI BeanManager
2019-06-05 21:25:06,708 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.Version.isJsf23(Version.java:62)
2019-06-05 21:25:06,708 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.ExpressionLanguage.addELResolver(ExpressionLanguage.java:136)
2019-06-05 21:25:06,708 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.ApplicationImpl.addELResolver(ApplicationImpl.java:221)
2019-06-05 21:25:06,708 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplication.<init>(WeldApplication.java:60)
2019-06-05 21:25:06,708 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplicationFactory.getApplication(WeldApplicationFactory.java:52)
2019-06-05 21:25:06,708 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.InjectionApplicationFactory.getApplication(InjectionApplicationFactory.java:61)
2019-06-05 21:25:06,708 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.AbstractConfigProcessor.getApplication(AbstractConfigProcessor.java:113)
2019-06-05 21:25:06,709 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.ComponentConfigProcessor.addComponents(ComponentConfigProcessor.java:106)
2019-06-05 21:25:06,709 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.ComponentConfigProcessor.process(ComponentConfigProcessor.java:96)
2019-06-05 21:25:06,709 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.lambda$initialize$1(ConfigManager.java:324)
2019-06-05 21:25:06,709 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Iterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,709 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,713 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.stream.ReferencePipeline$Head.forEach(Unknown Source)
2019-06-05 21:25:06,713 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:307)
2019-06-05 21:25:06,713 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:205)
2019-06-05 21:25:06,714 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
2019-06-05 21:25:06,714 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
2019-06-05 21:25:06,714 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
2019-06-05 21:25:06,714 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
2019-06-05 21:25:06,714 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
2019-06-05 21:25:06,714 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
2019-06-05 21:25:06,714 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,714 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,714 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,715 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,717 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,717 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
2019-06-05 21:25:06,717 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
2019-06-05 21:25:06,717 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
2019-06-05 21:25:06,718 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
2019-06-05 21:25:06,718 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.FutureTask.run(Unknown Source)
2019-06-05 21:25:06,718 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
2019-06-05 21:25:06,718 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
2019-06-05 21:25:06,718 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
2019-06-05 21:25:06,718 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
2019-06-05 21:25:06,718 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.lang.Thread.run(Unknown Source)
2019-06-05 21:25:06,718 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
2019-06-05 21:25:06,720 ERROR [stderr] (ServerService Thread Pool -- 123) javax.faces.FacesException: Unable to find CDI BeanManager
2019-06-05 21:25:06,721 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.Version.isJsf23(Version.java:62)
2019-06-05 21:25:06,721 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.ExpressionLanguage.addELResolver(ExpressionLanguage.java:136)
2019-06-05 21:25:06,721 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.ApplicationImpl.addELResolver(ApplicationImpl.java:221)
2019-06-05 21:25:06,722 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplication.<init>(WeldApplication.java:60)
2019-06-05 21:25:06,722 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplicationFactory.getApplication(WeldApplicationFactory.java:52)
2019-06-05 21:25:06,722 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.InjectionApplicationFactory.getApplication(InjectionApplicationFactory.java:61)
2019-06-05 21:25:06,722 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.AbstractConfigProcessor.getApplication(AbstractConfigProcessor.java:113)
2019-06-05 21:25:06,722 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.ConverterConfigProcessor.addConverters(ConverterConfigProcessor.java:103)
2019-06-05 21:25:06,722 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.ConverterConfigProcessor.process(ConverterConfigProcessor.java:93)
2019-06-05 21:25:06,722 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.lambda$initialize$1(ConfigManager.java:324)
2019-06-05 21:25:06,722 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Iterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,722 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,722 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.stream.ReferencePipeline$Head.forEach(Unknown Source)
2019-06-05 21:25:06,724 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:307)
2019-06-05 21:25:06,724 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:205)
2019-06-05 21:25:06,725 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
2019-06-05 21:25:06,725 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
2019-06-05 21:25:06,725 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
2019-06-05 21:25:06,725 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
2019-06-05 21:25:06,725 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
2019-06-05 21:25:06,725 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
2019-06-05 21:25:06,725 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,725 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,725 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,726 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,726 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,726 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
2019-06-05 21:25:06,726 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
2019-06-05 21:25:06,726 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
2019-06-05 21:25:06,726 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
2019-06-05 21:25:06,726 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.FutureTask.run(Unknown Source)
2019-06-05 21:25:06,726 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
2019-06-05 21:25:06,727 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
2019-06-05 21:25:06,727 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
2019-06-05 21:25:06,727 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
2019-06-05 21:25:06,727 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.lang.Thread.run(Unknown Source)
2019-06-05 21:25:06,727 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
2019-06-05 21:25:06,729 ERROR [stderr] (ServerService Thread Pool -- 123) javax.faces.FacesException: Unable to find CDI BeanManager
2019-06-05 21:25:06,729 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.Version.isJsf23(Version.java:62)
2019-06-05 21:25:06,729 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.ExpressionLanguage.addELResolver(ExpressionLanguage.java:136)
2019-06-05 21:25:06,729 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.ApplicationImpl.addELResolver(ApplicationImpl.java:221)
2019-06-05 21:25:06,730 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplication.<init>(WeldApplication.java:60)
2019-06-05 21:25:06,730 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplicationFactory.getApplication(WeldApplicationFactory.java:52)
2019-06-05 21:25:06,730 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.InjectionApplicationFactory.getApplication(InjectionApplicationFactory.java:61)
2019-06-05 21:25:06,730 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.AbstractConfigProcessor.getApplication(AbstractConfigProcessor.java:113)
2019-06-05 21:25:06,730 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.ValidatorConfigProcessor.addValidators(ValidatorConfigProcessor.java:129)
2019-06-05 21:25:06,730 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.ValidatorConfigProcessor.process(ValidatorConfigProcessor.java:97)
2019-06-05 21:25:06,730 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.lambda$initialize$1(ConfigManager.java:324)
2019-06-05 21:25:06,730 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Iterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,730 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,731 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.stream.ReferencePipeline$Head.forEach(Unknown Source)
2019-06-05 21:25:06,731 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:307)
2019-06-05 21:25:06,731 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:205)
2019-06-05 21:25:06,731 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
2019-06-05 21:25:06,731 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
2019-06-05 21:25:06,731 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
2019-06-05 21:25:06,731 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
2019-06-05 21:25:06,731 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
2019-06-05 21:25:06,731 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
2019-06-05 21:25:06,732 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,732 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,732 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,732 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,737 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,737 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
2019-06-05 21:25:06,737 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
2019-06-05 21:25:06,737 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
2019-06-05 21:25:06,737 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
2019-06-05 21:25:06,738 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.FutureTask.run(Unknown Source)
2019-06-05 21:25:06,738 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
2019-06-05 21:25:06,738 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
2019-06-05 21:25:06,738 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
2019-06-05 21:25:06,738 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
2019-06-05 21:25:06,738 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.lang.Thread.run(Unknown Source)
2019-06-05 21:25:06,738 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
2019-06-05 21:25:06,742 ERROR [stderr] (ServerService Thread Pool -- 123) javax.faces.FacesException: Unable to find CDI BeanManager
2019-06-05 21:25:06,742 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.Version.isJsf23(Version.java:62)
2019-06-05 21:25:06,742 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.ExpressionLanguage.addELResolver(ExpressionLanguage.java:136)
2019-06-05 21:25:06,742 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.ApplicationImpl.addELResolver(ApplicationImpl.java:221)
2019-06-05 21:25:06,742 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplication.<init>(WeldApplication.java:60)
2019-06-05 21:25:06,743 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplicationFactory.getApplication(WeldApplicationFactory.java:52)
2019-06-05 21:25:06,743 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.InjectionApplicationFactory.getApplication(InjectionApplicationFactory.java:61)
2019-06-05 21:25:06,743 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.AbstractConfigProcessor.getApplication(AbstractConfigProcessor.java:113)
2019-06-05 21:25:06,743 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.NavigationConfigProcessor.process(NavigationConfigProcessor.java:184)
2019-06-05 21:25:06,743 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.lambda$initialize$1(ConfigManager.java:324)
2019-06-05 21:25:06,743 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Iterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,743 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,743 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.stream.ReferencePipeline$Head.forEach(Unknown Source)
2019-06-05 21:25:06,744 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:307)
2019-06-05 21:25:06,749 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:205)
2019-06-05 21:25:06,749 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
2019-06-05 21:25:06,749 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
2019-06-05 21:25:06,749 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
2019-06-05 21:25:06,749 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
2019-06-05 21:25:06,749 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
2019-06-05 21:25:06,750 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
2019-06-05 21:25:06,750 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,750 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,750 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,750 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,750 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,752 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
2019-06-05 21:25:06,752 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
2019-06-05 21:25:06,752 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
2019-06-05 21:25:06,752 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
2019-06-05 21:25:06,752 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.FutureTask.run(Unknown Source)
2019-06-05 21:25:06,752 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
2019-06-05 21:25:06,752 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
2019-06-05 21:25:06,753 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
2019-06-05 21:25:06,753 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
2019-06-05 21:25:06,753 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.lang.Thread.run(Unknown Source)
2019-06-05 21:25:06,753 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
2019-06-05 21:25:06,755 ERROR [stderr] (ServerService Thread Pool -- 123) javax.faces.FacesException: Unable to find CDI BeanManager
2019-06-05 21:25:06,756 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.Version.isJsf23(Version.java:62)
2019-06-05 21:25:06,756 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.applicationimpl.ExpressionLanguage.addELResolver(ExpressionLanguage.java:136)
2019-06-05 21:25:06,756 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.ApplicationImpl.addELResolver(ApplicationImpl.java:221)
2019-06-05 21:25:06,756 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplication.<init>(WeldApplication.java:60)
2019-06-05 21:25:06,756 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.as.jsf.injection.weld.WeldApplicationFactory.getApplication(WeldApplicationFactory.java:52)
2019-06-05 21:25:06,757 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.application.InjectionApplicationFactory.getApplication(InjectionApplicationFactory.java:61)
2019-06-05 21:25:06,757 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.AbstractConfigProcessor.getApplication(AbstractConfigProcessor.java:113)
2019-06-05 21:25:06,757 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.BehaviorConfigProcessor.addBehaviors(BehaviorConfigProcessor.java:102)
2019-06-05 21:25:06,757 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.processor.BehaviorConfigProcessor.process(BehaviorConfigProcessor.java:92)
2019-06-05 21:25:06,757 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.lambda$initialize$1(ConfigManager.java:324)
2019-06-05 21:25:06,758 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Iterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,758 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Unknown Source)
2019-06-05 21:25:06,758 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.stream.ReferencePipeline$Head.forEach(Unknown Source)
2019-06-05 21:25:06,758 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:307)
2019-06-05 21:25:06,758 ERROR [stderr] (ServerService Thread Pool -- 123) 	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:205)
2019-06-05 21:25:06,758 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
2019-06-05 21:25:06,759 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
2019-06-05 21:25:06,759 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
2019-06-05 21:25:06,759 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
2019-06-05 21:25:06,759 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
2019-06-05 21:25:06,759 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
2019-06-05 21:25:06,760 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,760 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,760 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,760 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,760 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
2019-06-05 21:25:06,764 ERROR [stderr] (ServerService Thread Pool -- 123) 	at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
2019-06-05 21:25:06,765 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
2019-06-05 21:25:06,765 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
2019-06-05 21:25:06,765 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
2019-06-05 21:25:06,765 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.util.concurrent.FutureTask.run(Unknown Source)
2019-06-05 21:25:06,765 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
2019-06-05 21:25:06,765 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
2019-06-05 21:25:06,765 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
2019-06-05 21:25:06,766 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
2019-06-05 21:25:06,766 ERROR [stderr] (ServerService Thread Pool -- 123) 	at java.lang.Thread.run(Unknown Source)
2019-06-05 21:25:06,766 ERROR [stderr] (ServerService Thread Pool -- 123) 	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
2019-06-05 21:25:06,774 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 123) Critical error during deployment: : com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:205)
	at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
	at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
	at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
	at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
	at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
	at java.lang.Thread.run(Unknown Source)
	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
Caused by: java.lang.NullPointerException
	at com.sun.faces.facelets.impl.DefaultResourceResolver.resolveUrl(DefaultResourceResolver.java:40)
	at com.sun.faces.facelets.impl.DefaultFaceletFactory.init(DefaultFaceletFactory.java:129)
	at com.sun.faces.application.ApplicationAssociate.createFaceletFactory(ApplicationAssociate.java:849)
	at com.sun.faces.application.ApplicationAssociate.initializeFacelets(ApplicationAssociate.java:342)
	at com.sun.faces.application.ApplicationAssociate.getCompiler(ApplicationAssociate.java:420)
	at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:217)
	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:341)
	... 23 more
2019-06-05 21:25:06,782 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 123) MSC000001: Failed to start service jboss.deployment.unit."sample.war".undertow-deployment: org.jboss.msc.service.StartException in service jboss.deployment.unit."sample.war".undertow-deployment: java.lang.RuntimeException: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
	at java.lang.Thread.run(Unknown Source)
	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
	at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:252)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
	... 8 more
Caused by: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:283)
	at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
	at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
	at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
	at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
	at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
	... 10 more
Caused by: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:205)
	... 22 more
Caused by: java.lang.NullPointerException
	at com.sun.faces.facelets.impl.DefaultResourceResolver.resolveUrl(DefaultResourceResolver.java:40)
	at com.sun.faces.facelets.impl.DefaultFaceletFactory.init(DefaultFaceletFactory.java:129)
	at com.sun.faces.application.ApplicationAssociate.createFaceletFactory(ApplicationAssociate.java:849)
	at com.sun.faces.application.ApplicationAssociate.initializeFacelets(ApplicationAssociate.java:342)
	at com.sun.faces.application.ApplicationAssociate.getCompiler(ApplicationAssociate.java:420)
	at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:217)
	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:341)
	... 23 more

From brian.stansberry at redhat.com  Fri Jun  7 16:30:13 2019
From: brian.stansberry at redhat.com (Brian Stansberry)
Date: Fri, 7 Jun 2019 15:30:13 -0500
Subject: [wildfly-dev] WildFly-Camel 10.1.0
In-Reply-To: <42CDFBC7-D959-4600-AA10-24BBBEF363D4@redhat.com>
References: <42CDFBC7-D959-4600-AA10-24BBBEF363D4@redhat.com>
Message-ID: <CAPhbRDbLmfd9StckNgE3KunObLH-4faTnrgxSj5u8BcVuu-5wA@mail.gmail.com>

Nice! Congrats!

On Wed, Jun 5, 2019 at 3:28 AM Thomas Diesler <tdiesler at redhat.com> wrote:

> WildFly-Camel 10.1.0 provides Camel-2.24.0 integration with WildFly-16.0.0
>
> This is a minor update release that also adds a number of new components
> and data formats
>
> Component upgrades include
>
>    - Camel-2.24.0
>    - Hawtio-2.6.0
>
> Additional components in the supported set
> <http://wildfly-extras.github.io/wildfly-camel/#_camel_components> are:
>
>    - xchange
>    <https://github.com/apache/camel/blob/master/components/camel-xchange/src/main/docs/xchange-component.adoc>
>    - ipfs
>    <https://github.com/apache/camel/blob/master/components/camel-ipfs/src/main/docs/ipfs-component.adoc>
>    - nsq
>    <https://github.com/apache/camel/blob/master/components/camel-nsq/src/main/docs/nsq-component.adoc>
>
> In addition to that, we also resolved a number of other tasks and bugs
> <https://github.com/wildfly-extras/wildfly-camel/blob/master/docs/Changelog.md>
> .
>
> For details please see the 10.1.0 Milestone
> <https://github.com/wildfly-extras/wildfly-camel/issues?q=milestone%3A10.1.0>
> .
>
> Enjoy
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev



-- 
Brian Stansberry
Manager, Senior Principal Software Engineer
Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190607/603d5d20/attachment.html 

From brian.stansberry at redhat.com  Fri Jun  7 16:48:49 2019
From: brian.stansberry at redhat.com (Brian Stansberry)
Date: Fri, 7 Jun 2019 15:48:49 -0500
Subject: [wildfly-dev] Status update on WildFly 17.0.0.Final release
Message-ID: <CAPhbRDYK+N28h4SHfXeE0bTCtF1YrUmdxaxP6pVH9Gg+E6VboQ@mail.gmail.com>

Just an FYI that work has begun on producing the WildFly 17.0.0.Final
release. We're on track to publish the release to maven and
https://wildfly.org/downloads on Monday.

Earlier today James Perkins pushed the 17.0.0.Final tag to github, and the
master branch pom versions have moved on to 18.0.0.Beta1-SNAPSHOT. But
other aspects of the release, i.e. publishing the binaries and the final
boms and quickstarts will be completed Monday. So if you see the tag and
wonder what's up, that's what's up. ;)   Doing all the bits of a release
usually takes more than a working day. This time it stretches over a
weekend so it's a bit more noticeable.

Best regards,
Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190607/880bf86f/attachment.html 

From jai.forums2013 at gmail.com  Tue Jun 11 04:56:52 2019
From: jai.forums2013 at gmail.com (Jaikiran Pai)
Date: Tue, 11 Jun 2019 14:26:52 +0530
Subject: [wildfly-dev] Test (please ignore)
Message-ID: <1bdcb3c2-9ab4-3e5a-fd7a-b3b8852c889a@gmail.com>

Haven't been receiving any mails on this list since many months now,
even though I'm subscribed, checking to see if this gets delivered.

-Jaikiran


From wolfgang.knauf at gmx.de  Wed Jun 12 15:57:27 2019
From: wolfgang.knauf at gmx.de (Wolfgang Knauf)
Date: Wed, 12 Jun 2019 21:57:27 +0200
Subject: [wildfly-dev] Updating the WildFly archetypes
In-Reply-To: <3f21e2cc-03e4-c8b7-5067-f84cddf42d83@gmx.de>
References: <2c35697c-c08e-9fbc-d824-dd036ec51dce@gmx.de>
	<96e133b0-bf15-3b3d-9975-02cf6e3dec1e@gmx.de>
	<CALX1fhcOp7eu0AAc5CYhSzr+_GFTVnu9-MVv2wB4TFt=Vagicg@mail.gmail.com>
	<5914b66f-e9d5-b703-3295-84012220d9e1@gmx.de>
	<42a971fe-fd23-df27-c31d-9fdc6148dca7@gmx.de>
	<3a70866d-4621-514e-b329-0fa117219c45@gmx.de>
	<EE0424D8-D48B-4000-AD26-FF3419A0DEF2@redhat.com>
	<736372a6-ead3-2d3b-d9bd-cd7bc346a8de@gmx.de>
	<625CA896-F39B-4270-9D71-0CA71A44C839@redhat.com>
	<88FA5E9A-43B0-4ED6-A18B-4A370CA6CF9C@redhat.com>
	<CAPhbRDZ5x4+5cs7gdXuiy6hs-7bCvhB7FF3p=U40ziCtKkrspQ@mail.gmail.com>
	<CALX1fhfRiyp9iZkn7Tf+s35GRzcv=r8PiLVu2Uj8O6xJzLNsfw@mail.gmail.com>
	<CAPhbRDYeg+vTGrhDOgsxH+CTbkJvt5he3MiW6QM1UYZj79jQpw@mail.gmail.com>
	<5A38A072-F4DA-4646-9A9A-2CD3234C82B8@redhat.com>
	<2A45481D-E369-4E21-BA28-C06ED259C029@redhat.com>
	<CAPhbRDajKjMvZSZHsQYb6_zTiN+U6uxiydA-Z18cxY4=YwGZ+A@mail.gmail.com>
	<b3b504ae-f6b7-efc2-f134-acfff9926d12@gmx.de>
	<3f21e2cc-03e4-c8b7-5067-f84cddf42d83@gmx.de>
Message-ID: <cfcbc2f8-06cc-296b-fde8-8a1670a21ddf@gmx.de>

Hi to all,

just wanted to ask for an update: do you think that the error message is
acceptable and I should create the archetype without "beans.xml" anyway
(and add an info to the readme.txt file)?
Or should I add a default "beans.xml" to the archetype to avoid it?
Or is it worth a JIRA?

Best regards

Wolfgang

Am 05.06.19 um 21:42 schrieb Wolfgang Knauf:
> Hi Eduardo,
>
> while building a "wildfly-javaee-webapp-archetype", I think I found a
> small WildFly issue: you remember that you pointed me to the fact that
> "beans.xml" is optional?
> But when creating a blank project from my new web archetype (which
> defines a "faces-config.xml", but no "beans.xml"), the attached error is
> in the WildFly console. But it seems the app is deployed anyway.
>
> The error disappears if I add e.g. an annotated EJB, or if I add a
> "beans.xml".
>
> Do you think this is a WildFly bug? Or should I add a default
> "beans.xml" just to avoid this error?
>
> I did not test it with a blank project from the EAR archetype - will do
> this in the next few days.
>
> Best regards
>
> Wolfgang
>
>
> Am 03.06.19 um 21:36 schrieb Wolfgang Knauf:
>> Thanks for the deploy, Eduardo!
>>
>> If you consider it reasonable I will create an archetype for "web app
>> only", similar to the old "wildfly-javaee7-webapp-archetype".
>> But I will probably need a few weeks...
>>
>> What happens to the old archetype
>> "wildfly-javaee7-webapp-ear-archetype"? It could be deleted, as it
>> does not build anyway. It might be relevant only for research.
>>
>> Best regards
>>
>> Wolfgang
>>
>>
>>
>> Am 03.06.19 um 17:05 schrieb Brian Stansberry:
>>> Excellent!? Thank you so much Wolfgang!
>>>
>>> On Mon, Jun 3, 2019 at 9:52 AM Eduardo Martins <emartins at redhat.com
>>> <mailto:emartins at redhat.com>> wrote:
>>>
>>> ??? Wolfgang: yours and mine PRs are merged, and when WFLY 17 Final is
>>> ??? out I will also deploy the archetype, thanks a lot for your
>>> ??? contribution! Yet now I have to ask, do you plan to submit similar
>>> ??? for the other old javaee archetype? :-)
>>>
>>> ??? Brian: yep it was just the JDK, I will deploy these too (no planned
>>> ??? updates in such code tho)
>>>
>>> ??? ?E
>>>
>>>> ??? On 16 May 2019, at 10:09, Eduardo Martins <emartins at redhat.com
>>>> ??? <mailto:emartins at redhat.com>> wrote:
>>>>
>>>> ??? Hmm ok, maybe it just failed build due to some specific like JDK
>>>> ??? 11, will recheck that.
>>>>
>>>> ??? ?E
>>>>
>>>>> ??? On 16 May 2019, at 02:25, Brian Stansberry
>>>>> ??? <brian.stansberry at redhat.com
>>>>> ??? <mailto:brian.stansberry at redhat.com>> wrote:
>>>>>
>>>>> ??? These build for me.
>>>>>
>>>>> ??? They're not as out of date as I'd thought either.
>>>>>
>>>>> ??? On Fri, May 10, 2019 at 6:34 PM Eduardo Martins
>>>>> ??? <emartins at redhat.com <mailto:emartins at redhat.com>> wrote:
>>>>>
>>>>> ??????? If you think it?s not a small effort task then certainly
>>>>> ??????? agree that?s not a blocker, I look at the archetypes same way
>>>>> ??????? as the quickstarts, ?an aggregation project, so we may take
>>>>> ??????? outdated/faulty ones out of build and release the
>>>>> ??????? working+actual ones. We may give it a thought later if it
>>>>> ??????? makes sense effort wise to update or drop the subsystem ones,
>>>>> ??????? no worries.
>>>>>
>>>>> ??????? ?E
>>>>>


From emartins at redhat.com  Wed Jun 12 16:37:18 2019
From: emartins at redhat.com (Eduardo Martins)
Date: Wed, 12 Jun 2019 21:37:18 +0100
Subject: [wildfly-dev] Updating the WildFly archetypes
In-Reply-To: <cfcbc2f8-06cc-296b-fde8-8a1670a21ddf@gmx.de>
References: <2c35697c-c08e-9fbc-d824-dd036ec51dce@gmx.de>
	<96e133b0-bf15-3b3d-9975-02cf6e3dec1e@gmx.de>
	<CALX1fhcOp7eu0AAc5CYhSzr+_GFTVnu9-MVv2wB4TFt=Vagicg@mail.gmail.com>
	<5914b66f-e9d5-b703-3295-84012220d9e1@gmx.de>
	<42a971fe-fd23-df27-c31d-9fdc6148dca7@gmx.de>
	<3a70866d-4621-514e-b329-0fa117219c45@gmx.de>
	<EE0424D8-D48B-4000-AD26-FF3419A0DEF2@redhat.com>
	<736372a6-ead3-2d3b-d9bd-cd7bc346a8de@gmx.de>
	<625CA896-F39B-4270-9D71-0CA71A44C839@redhat.com>
	<88FA5E9A-43B0-4ED6-A18B-4A370CA6CF9C@redhat.com>
	<CAPhbRDZ5x4+5cs7gdXuiy6hs-7bCvhB7FF3p=U40ziCtKkrspQ@mail.gmail.com>
	<CALX1fhfRiyp9iZkn7Tf+s35GRzcv=r8PiLVu2Uj8O6xJzLNsfw@mail.gmail.com>
	<CAPhbRDYeg+vTGrhDOgsxH+CTbkJvt5he3MiW6QM1UYZj79jQpw@mail.gmail.com>
	<5A38A072-F4DA-4646-9A9A-2CD3234C82B8@redhat.com>
	<2A45481D-E369-4E21-BA28-C06ED259C029@redhat.com>
	<CAPhbRDajKjMvZSZHsQYb6_zTiN+U6uxiydA-Z18cxY4=YwGZ+A@mail.gmail.com>
	<b3b504ae-f6b7-efc2-f134-acfff9926d12@gmx.de>
	<3f21e2cc-03e4-c8b7-5067-f84cddf42d83@gmx.de>
	<cfcbc2f8-06cc-296b-fde8-8a1670a21ddf@gmx.de>
Message-ID: <21DD1C8C-7E05-4FC8-84B5-07CEBD3E46EE@redhat.com>

Hi Wolfgang, when reviewing it seemed to me that in the *ear* archetype the beans.xml was not needed. I can?t tell if that?s the case for this new archetype without you submitting it for review, but if it fails to deploy without it? ;-)

?E

> On 12 Jun 2019, at 20:57, Wolfgang Knauf <wolfgang.knauf at gmx.de> wrote:
> 
> Hi to all,
> 
> just wanted to ask for an update: do you think that the error message is
> acceptable and I should create the archetype without "beans.xml" anyway
> (and add an info to the readme.txt file)?
> Or should I add a default "beans.xml" to the archetype to avoid it?
> Or is it worth a JIRA?
> 
> Best regards
> 
> Wolfgang
> 
> Am 05.06.19 um 21:42 schrieb Wolfgang Knauf:
>> Hi Eduardo,
>> 
>> while building a "wildfly-javaee-webapp-archetype", I think I found a
>> small WildFly issue: you remember that you pointed me to the fact that
>> "beans.xml" is optional?
>> But when creating a blank project from my new web archetype (which
>> defines a "faces-config.xml", but no "beans.xml"), the attached error is
>> in the WildFly console. But it seems the app is deployed anyway.
>> 
>> The error disappears if I add e.g. an annotated EJB, or if I add a
>> "beans.xml".
>> 
>> Do you think this is a WildFly bug? Or should I add a default
>> "beans.xml" just to avoid this error?
>> 
>> I did not test it with a blank project from the EAR archetype - will do
>> this in the next few days.
>> 
>> Best regards
>> 
>> Wolfgang
>> 
>> 
>> Am 03.06.19 um 21:36 schrieb Wolfgang Knauf:
>>> Thanks for the deploy, Eduardo!
>>> 
>>> If you consider it reasonable I will create an archetype for "web app
>>> only", similar to the old "wildfly-javaee7-webapp-archetype".
>>> But I will probably need a few weeks...
>>> 
>>> What happens to the old archetype
>>> "wildfly-javaee7-webapp-ear-archetype"? It could be deleted, as it
>>> does not build anyway. It might be relevant only for research.
>>> 
>>> Best regards
>>> 
>>> Wolfgang
>>> 
>>> 
>>> 
>>> Am 03.06.19 um 17:05 schrieb Brian Stansberry:
>>>> Excellent!  Thank you so much Wolfgang!
>>>> 
>>>> On Mon, Jun 3, 2019 at 9:52 AM Eduardo Martins <emartins at redhat.com
>>>> <mailto:emartins at redhat.com>> wrote:
>>>> 
>>>>     Wolfgang: yours and mine PRs are merged, and when WFLY 17 Final is
>>>>     out I will also deploy the archetype, thanks a lot for your
>>>>     contribution! Yet now I have to ask, do you plan to submit similar
>>>>     for the other old javaee archetype? :-)
>>>> 
>>>>     Brian: yep it was just the JDK, I will deploy these too (no planned
>>>>     updates in such code tho)
>>>> 
>>>>     ?E
>>>> 
>>>>>     On 16 May 2019, at 10:09, Eduardo Martins <emartins at redhat.com
>>>>>     <mailto:emartins at redhat.com>> wrote:
>>>>> 
>>>>>     Hmm ok, maybe it just failed build due to some specific like JDK
>>>>>     11, will recheck that.
>>>>> 
>>>>>     ?E
>>>>> 
>>>>>>     On 16 May 2019, at 02:25, Brian Stansberry
>>>>>>     <brian.stansberry at redhat.com
>>>>>>     <mailto:brian.stansberry at redhat.com>> wrote:
>>>>>> 
>>>>>>     These build for me.
>>>>>> 
>>>>>>     They're not as out of date as I'd thought either.
>>>>>> 
>>>>>>     On Fri, May 10, 2019 at 6:34 PM Eduardo Martins
>>>>>>     <emartins at redhat.com <mailto:emartins at redhat.com>> wrote:
>>>>>> 
>>>>>>         If you think it?s not a small effort task then certainly
>>>>>>         agree that?s not a blocker, I look at the archetypes same way
>>>>>>         as the quickstarts,  an aggregation project, so we may take
>>>>>>         outdated/faulty ones out of build and release the
>>>>>>         working+actual ones. We may give it a thought later if it
>>>>>>         makes sense effort wise to update or drop the subsystem ones,
>>>>>>         no worries.
>>>>>> 
>>>>>>         ?E
>>>>>> 



From jai.forums2013 at gmail.com  Wed Jun 12 21:15:01 2019
From: jai.forums2013 at gmail.com (Jaikiran Pai)
Date: Thu, 13 Jun 2019 06:45:01 +0530
Subject: [wildfly-dev] Test (please ignore)
In-Reply-To: <1bdcb3c2-9ab4-3e5a-fd7a-b3b8852c889a@gmail.com>
References: <1bdcb3c2-9ab4-3e5a-fd7a-b3b8852c889a@gmail.com>
Message-ID: <d9b674d2-fe91-5681-e5b6-aaf3095603a3@gmail.com>

This has now been sorted out and I have started receiving the mails on
this list. Turns out, the mailing list software automatically disabled
delivery to this account back in November 2018 apparently due to
"excessive bounces". I don't know why the deliveries were bouncing at
that time but I have now re-enabled the delivery by using my
subscription management page. Thanks to Kabir for helping out in this.

-Jaikiran

On 11/06/19 2:26 PM, Jaikiran Pai wrote:
> Haven't been receiving any mails on this list since many months now,
> even though I'm subscribed, checking to see if this gets delivered.
>
> -Jaikiran
>

From rory.odonnell at oracle.com  Sun Jun 16 01:21:19 2019
From: rory.odonnell at oracle.com (Rory O'Donnell)
Date: Sun, 16 Jun 2019 10:51:19 +0530
Subject: [wildfly-dev] JDK 13 enters Rampdown Phase One
Message-ID: <4ff1170d-f420-7941-c52b-7ece88187ed0@oracle.com>

Hi David & Richard,

*JDK 13 Early Access build **25 is now available **at : - jdk.java.net/13/*

  * Per the JDK 13 schedule [1], we are now in Rampdown Phase One.
      o For more details , see Mark Reinhold's email to jdk-dev mailing
        list [2]
      o The overall feature set is frozen, no further JEPs will be
        targeted to this release.
  * Changes in this build 25 [4]

*Request for feedback on JEP 353 integrated in b24
*

JEP 353: Reimplement the Legacy Socket API" has been integrated into 
jdk-13+24. It would be very useful if applications or libraries using 
java.net.Socket or java.net.ServerSocket APIs could test with this build 
and report any issues found. The JEP provides information on the system 
property that can be used to switch back to the old implementation and 
that may be useful to check for behavior differences between the old and 
new implementation. It would be very useful to get feedback via the 
OpenJDK net-dev mailing list, bugs via the usual channel.

*Updates to Release Notes since last email*

  * b25 - Support Kerberos cross-realm referrals (RFC 6806)(JDK-8215032
    <https://bugs.openjdk.java.net/browse/JDK-8215032>)
  * b25 - Add -XX:SoftMaxHeapSize flag(JDK-8222145
    <https://bugs.openjdk.java.net/browse/JDK-8222145>)
  * b24 - Reimplement the Legacy Socket API(JDK-8221481
    <https://bugs.openjdk.java.net/browse/JDK-8221481>)
      o see above request for feedback
  * b24? - Deprecated rmic tool For Removal(JDK-8217412
    <https://bugs.openjdk.java.net/browse/JDK-8217412>)
  * b24 - New String constants for Canonical XML 1.1 URIs(JDK-8224767
    <https://bugs.openjdk.java.net/browse/JDK-8224767>)
  * b23 - Support for Unicode 12.1 (JDK-8221431
    <https://bugs.openjdk.java.net/browse/JDK-8221431>)
  * b21 - Upgrade CLDR to Version 35.1 (JDK-8221432
    <https://bugs.openjdk.java.net/browse/JDK-8221432>)

*OpenJDK 14 **Early Access build 1 **is now available **at : - 
jdk.java.net/14/*

  * These early-access, open-source builds are provided under the GNU
    General Public License, version?2, with the Classpath Exception
    <http://openjdk.java.net/legal/gplv2+ce.html>.
  * Changes in this build [5]

**

Rgds, Rory

[1] http://openjdk.java.net/projects/jdk/13/#Schedule 
<http://openjdk.java.net/projects/jdk/12/#Schedule>
[2] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-June/003060.html
[3] http://jdk.java.net/13/release-notes
[4] JDK 13 - Changes in b25 here 
<http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-13%2B24%22%3A%3A%22jdk-13%2B25%22-%22jdk-13%2B24%22%29&revcount=1000>
[5] JDK 14 - Changes in b1 here 
<http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-14%2B0%22%3A%3A%22jdk-14%2B1%22-%22jdk-14%2B0%22%29&revcount=1000>

-- 
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin,Ireland

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190616/ff26b787/attachment.html 

From wolfgang.knauf at gmx.de  Sun Jun 16 08:12:34 2019
From: wolfgang.knauf at gmx.de (Wolfgang Knauf)
Date: Sun, 16 Jun 2019 14:12:34 +0200
Subject: [wildfly-dev] Updating the WildFly archetypes
In-Reply-To: <21DD1C8C-7E05-4FC8-84B5-07CEBD3E46EE@redhat.com>
References: <2c35697c-c08e-9fbc-d824-dd036ec51dce@gmx.de>
	<5914b66f-e9d5-b703-3295-84012220d9e1@gmx.de>
	<42a971fe-fd23-df27-c31d-9fdc6148dca7@gmx.de>
	<3a70866d-4621-514e-b329-0fa117219c45@gmx.de>
	<EE0424D8-D48B-4000-AD26-FF3419A0DEF2@redhat.com>
	<736372a6-ead3-2d3b-d9bd-cd7bc346a8de@gmx.de>
	<625CA896-F39B-4270-9D71-0CA71A44C839@redhat.com>
	<88FA5E9A-43B0-4ED6-A18B-4A370CA6CF9C@redhat.com>
	<CAPhbRDZ5x4+5cs7gdXuiy6hs-7bCvhB7FF3p=U40ziCtKkrspQ@mail.gmail.com>
	<CALX1fhfRiyp9iZkn7Tf+s35GRzcv=r8PiLVu2Uj8O6xJzLNsfw@mail.gmail.com>
	<CAPhbRDYeg+vTGrhDOgsxH+CTbkJvt5he3MiW6QM1UYZj79jQpw@mail.gmail.com>
	<5A38A072-F4DA-4646-9A9A-2CD3234C82B8@redhat.com>
	<2A45481D-E369-4E21-BA28-C06ED259C029@redhat.com>
	<CAPhbRDajKjMvZSZHsQYb6_zTiN+U6uxiydA-Z18cxY4=YwGZ+A@mail.gmail.com>
	<b3b504ae-f6b7-efc2-f134-acfff9926d12@gmx.de>
	<3f21e2cc-03e4-c8b7-5067-f84cddf42d83@gmx.de>
	<cfcbc2f8-06cc-296b-fde8-8a1670a21ddf@gmx.de>
	<21DD1C8C-7E05-4FC8-84B5-07CEBD3E46EE@redhat.com>
Message-ID: <103ae970-9e8c-1651-c0d7-5bd5a4681afb@gmx.de>

Hi Eduardo,

i sent a pull request for this new archetype, without beans.xml.
Depending on your findings, we can add it afterwards if necessary.

But as far as I understand it, this file is optional now
(https://blogs.oracle.com/theaquarium/default-cdi-enablement-in-java-ee-7)
- so this could be considered a bug...

Best regards

Wolfgang


Am 12.06.19 um 22:37 schrieb Eduardo Martins:
> Hi Wolfgang, when reviewing it seemed to me that in the *ear* archetype the beans.xml was not needed. I can?t tell if that?s the case for this new archetype without you submitting it for review, but if it fails to deploy without it? ;-)
>
> ?E
>
>> On 12 Jun 2019, at 20:57, Wolfgang Knauf <wolfgang.knauf at gmx.de> wrote:
>>
>> Hi to all,
>>
>> just wanted to ask for an update: do you think that the error message is
>> acceptable and I should create the archetype without "beans.xml" anyway
>> (and add an info to the readme.txt file)?
>> Or should I add a default "beans.xml" to the archetype to avoid it?
>> Or is it worth a JIRA?
>>
>> Best regards
>>
>> Wolfgang
>>
>> Am 05.06.19 um 21:42 schrieb Wolfgang Knauf:
>>> Hi Eduardo,
>>>
>>> while building a "wildfly-javaee-webapp-archetype", I think I found a
>>> small WildFly issue: you remember that you pointed me to the fact that
>>> "beans.xml" is optional?
>>> But when creating a blank project from my new web archetype (which
>>> defines a "faces-config.xml", but no "beans.xml"), the attached error is
>>> in the WildFly console. But it seems the app is deployed anyway.
>>>
>>> The error disappears if I add e.g. an annotated EJB, or if I add a
>>> "beans.xml".
>>>
>>> Do you think this is a WildFly bug? Or should I add a default
>>> "beans.xml" just to avoid this error?
>>>
>>> I did not test it with a blank project from the EAR archetype - will do
>>> this in the next few days.
>>>
>>> Best regards
>>>
>>> Wolfgang
>>>
>>>
>>> Am 03.06.19 um 21:36 schrieb Wolfgang Knauf:
>>>> Thanks for the deploy, Eduardo!
>>>>
>>>> If you consider it reasonable I will create an archetype for "web app
>>>> only", similar to the old "wildfly-javaee7-webapp-archetype".
>>>> But I will probably need a few weeks...
>>>>
>>>> What happens to the old archetype
>>>> "wildfly-javaee7-webapp-ear-archetype"? It could be deleted, as it
>>>> does not build anyway. It might be relevant only for research.
>>>>
>>>> Best regards
>>>>
>>>> Wolfgang
>>>>
>>>>
>>>>
>>>> Am 03.06.19 um 17:05 schrieb Brian Stansberry:
>>>>> Excellent!  Thank you so much Wolfgang!
>>>>>
>>>>> On Mon, Jun 3, 2019 at 9:52 AM Eduardo Martins <emartins at redhat.com
>>>>> <mailto:emartins at redhat.com>> wrote:
>>>>>
>>>>>      Wolfgang: yours and mine PRs are merged, and when WFLY 17 Final is
>>>>>      out I will also deploy the archetype, thanks a lot for your
>>>>>      contribution! Yet now I have to ask, do you plan to submit similar
>>>>>      for the other old javaee archetype? :-)
>>>>>
>>>>>      Brian: yep it was just the JDK, I will deploy these too (no planned
>>>>>      updates in such code tho)
>>>>>
>>>>>      ?E
>>>>>
>>>>>>      On 16 May 2019, at 10:09, Eduardo Martins <emartins at redhat.com
>>>>>>      <mailto:emartins at redhat.com>> wrote:
>>>>>>
>>>>>>      Hmm ok, maybe it just failed build due to some specific like JDK
>>>>>>      11, will recheck that.
>>>>>>
>>>>>>      ?E
>>>>>>
>>>>>>>      On 16 May 2019, at 02:25, Brian Stansberry
>>>>>>>      <brian.stansberry at redhat.com
>>>>>>>      <mailto:brian.stansberry at redhat.com>> wrote:
>>>>>>>
>>>>>>>      These build for me.
>>>>>>>
>>>>>>>      They're not as out of date as I'd thought either.
>>>>>>>
>>>>>>>      On Fri, May 10, 2019 at 6:34 PM Eduardo Martins
>>>>>>>      <emartins at redhat.com <mailto:emartins at redhat.com>> wrote:
>>>>>>>
>>>>>>>          If you think it?s not a small effort task then certainly
>>>>>>>          agree that?s not a blocker, I look at the archetypes same way
>>>>>>>          as the quickstarts,  an aggregation project, so we may take
>>>>>>>          outdated/faulty ones out of build and release the
>>>>>>>          working+actual ones. We may give it a thought later if it
>>>>>>>          makes sense effort wise to update or drop the subsystem ones,
>>>>>>>          no worries.
>>>>>>>
>>>>>>>          ?E
>>>>>>>
>
>


From aabdelsa at redhat.com  Tue Jun 18 14:09:02 2019
From: aabdelsa at redhat.com (Ashley Abdel-Sayed)
Date: Tue, 18 Jun 2019 14:09:02 -0400
Subject: [wildfly-dev] Proposal to support adding principal-transformer
	attribute to aggregate-realm
Message-ID: <CABAf=RQVmQw8KxvxAn15RU3BTEYv2D+8RJtz4kYCz-nkQSPAXg@mail.gmail.com>

Here is a proposal to add a principal-transformer attribute to
aggregate-realm

https://github.com/wildfly/wildfly-proposals/pull/209

This is being handled under the following Jira issues: -

https://issues.jboss.org/browse/ELY-1829
https://issues.jboss.org/browse/WFCORE-4496
https://issues.jboss.org/browse/WFLY-12202

Regards,
Ashley Abdel-Sayed
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190618/336e75ff/attachment-0001.html 

From darran.lofthouse at jboss.com  Thu Jun 20 07:10:06 2019
From: darran.lofthouse at jboss.com (Darran Lofthouse)
Date: Thu, 20 Jun 2019 12:10:06 +0100
Subject: [wildfly-dev] Adding Support for Expression Resolution Backed by a
	CredentialStore
Message-ID: <CAMxVf4PcgpQDT9Uz221zWasGA4yp02ReP6xyFSZXtyixaTHcGA@mail.gmail.com>

The following is very much work in progress and I expect it to evolve
greatly based on discussions and the practicality of implementing this
feature - however here are my initial thoughts in relation to adding
support for management model expression resolution backed by a credential
store: -

https://github.com/wildfly/wildfly-proposals/pull/213

As I mention in the analysis we are actually missing documentation for the
credential store anyway so I will add that first under
https://issues.jboss.org/browse/WFLY-11101 before progressing to the next
stages of this feature.

Regards,
Darran Lofthouse.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190620/073debbb/attachment.html 

From aabdelsa at redhat.com  Mon Jun 24 15:02:33 2019
From: aabdelsa at redhat.com (Ashley Abdel-Sayed)
Date: Mon, 24 Jun 2019 15:02:33 -0400
Subject: [wildfly-dev] Proposal to add support for masked passwords in
	client XML config
Message-ID: <CABAf=RSmXR2vnyvkcBVkK9pH7_7+nMm6TvKQBgwG_WXJ_xRkeA@mail.gmail.com>

Here is a proposal to add support for masked passwords in client XML config:

https://github.com/wildfly/wildfly-proposals/pull/214

This is being handled under the following Jira issues:

https://issues.jboss.org/browse/ELY-816
https://issues.jboss.org/browse/ELY-867

Regards,
Ashley Abdel-Sayed
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190624/5ded5a77/attachment.html 

From fjuma at redhat.com  Mon Jun 24 17:21:48 2019
From: fjuma at redhat.com (Farah Juma)
Date: Mon, 24 Jun 2019 17:21:48 -0400
Subject: [wildfly-dev] Proposal to support automatically adding and updating
 credentials in a credential store
Message-ID: <CAFv3guQ6=Wg=VyV=45T0HXJsD3wUYNv-6v1FhMub5G-Cx05i9Q@mail.gmail.com>

Here is a proposal to add support for automatically adding and updating
credentials in a credential store:

https://github.com/wildfly/wildfly-proposals/pull/215

Any feedback is welcome.

Thanks,
Farah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20190624/51ee70c6/attachment.html