There is ws deployment failure issue which is caused by Webservice
subsystem doesn't correctly get mapped elytron security domain from web
deployment's default "other"
application security domain. I tried to fix this by reading Elytron
security domain from Undertow started services, but it looks now
ApplicationSecurityDomainService is private static and it doesn't provide a
getter which allows to get Elytron security domain. Webservice subsystem
requires an Undertow service like ApplicationSecurityDomainService
started by EJB subsystem to read the Elytron security domain. Is it doable
to change Undertow's ApplicationSecurityDomainService to provide mapped
security domain ? Or any better approach to get the mapped Elytron domain ?
I have submitted a PR to enable the use of a cool ASCII banner during WildFly startup.
The banner content is externalized to a banner.txt file and removing that file or its content is supported.
What do you think about this ?
6:37:53,123 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
16:37:53,587 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
16:37:53,594 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
16:37:53,706 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 12.0.0.Beta2-SNAPSHOT (WildFly Core
_ ___ __ __________ ______
| | / (_) /___/ / ____/ /_ __ / ____/___ ________
| | /| / / / / __ / /_ / / / / / / / / __ \/ ___/ _ \
| |/ |/ / / / /_/ / __/ / / /_/ / / /___/ /_/ / / / __/
|__/|__/_/_/\__,_/_/ /_/\__, / \____/\____/_/ \___/
16:37:54,319 INFO [org.wildfly.security] (ServerService Thread Pool -- 6) ELY00001: WildFly Elytron version 1.11.3.Final
You may recall that last year we advertised a likely refresh of the
https://wildfly.org site, and asked for input. The rollout of that refresh
took a back burner for a while, but Adela Arreola and James Cobb are
working on it now and I'd like to move over soon. So I encourage the
community to have a look and provide any feedback. (Note there's no need
to provide feedback about the beta content being behind the live site;
that's being addressed.)
The beta version of the revised site is at
If you'd like to report and issue, you can do so at
On Tue, 26 May 2020 at 14:23, James Cobb <jcobb(a)redhat.com> wrote:
> On May 26, 2020, at 7:36 AM, Brian Stansberry <brian.stansberry(a)redhat.com>
> On Tue, May 26, 2020 at 4:53 AM Kabir Khan <kkhan(a)redhat.com> wrote:
>> It looks great! A few niggles from my POV:
>> * The blog post summaries on the main page don't stand out to me as being
>> a 'News' section
> I'm not sure what you mean.
> I take it that the intent of the content blocks are unclear. The simplest
> solution would be to add a “Latest News” or “Blogs” header above them (see
> attached screenshot).
Yes something like that is exactly what I mean :)
> But for sure thanks, as your comment made me realize all the existing
> 'news' URLs which are linked to in many places will be broken with the
> current site draft. So I filed
> https://github.com/jbossorg/wildflysite/issues/34. Adela I think that's a
> blocker problem.
>> * Is the absence of the tweets section we have in the current
>> https://wildfly.org intentional?
> 1) AIUI generally tweets are meant to drive traffic to sites as opposed to
> the opposite. This is a philosophical question where I have no strong
> opinion. But,
> 2) The current tweets section doesn't actually work on a number of browser
> combos. Doesn't work for me in most browsers I have; didn't work for James
> Perkins in at least some. I'm not enthused about maintaining such a thing.
>> On Wed, 20 May 2020 at 20:46, Brian Stansberry <
>> brian.stansberry(a)redhat.com> wrote:
>>> You may recall that last year we advertised a likely refresh of the
>>> https://wildfly.org site, and asked for input. The rollout of that
>>> refresh took a back burner for a while, but Adela Arreola and James Cobb
>>> are working on it now and I'd like to move over soon. So I encourage the
>>> community to have a look and provide any feedback. (Note there's no need
>>> to provide feedback about the beta content being behind the live site;
>>> that's being addressed.)
>>> The beta version of the revised site is at
>>> If you'd like to report and issue, you can do so at
>>> Best regards,
>>> wildfly-dev mailing list
> Brian Stansberry
> Manager, Senior Principal Software Engineer
> Red Hat