Plugging in Credential Store backed ExpressionResolver
by Darran Lofthouse
Presently working on WFCORE-4360 adding support for expression resolution
backed by a credential store - the main barrier is going to be the solution
to bridge expression resolution with a subsystem provided component.
I am wondering if the following is going to be viable to support a
configurable expression resolver from a subsystem.
I see the RuntimeExpressionResolver is created very early in the boot
process, however at the time it is created the CapabilityRegistry is also
available. This is making me think if the CapabilityRegistry can be passed
in to the RuntimeExpressionResolver.
I would then imagine the resource handling expression resolution would
register a non-dynamic capability which exposes an expression resolver
runtime API. This in turn may also need to cross reference a credential
store which would also need to be accessible using the runtime API of a
capability.
At the time of expression resolution the RuntimeExpressionResolver would
then check the CapabilityRegistry to see if an expression resolver has been
registered and attempt to use it falling back to vault then default
ModelNode resolution if it does not resolve the expression.
Using a runtime API I suspect I would likely need to trigger the
initialisation of these APIs at the start of Stage.RUNTIME - that looks
feasible by adding a stage to Stage.RUNTIME with addFirst test to true -
maybe to be safe these should also start on demand based on first access.
Regards,
Darran Lofthouse.
3 years, 8 months
Adding a banner to WildFly
by Emmanuel Hugonnet
Hello,
I have submitted a PR[1] 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
12.0.0.Beta2-SNAPSHOT) starting
_ ___ __ __________ ______
| | / (_) /___/ / ____/ /_ __ / ____/___ ________
| | /| / / / / __ / /_ / / / / / / / / __ \/ ___/ _ \
| |/ |/ / / / /_/ / __/ / / /_/ / / /___/ /_/ / / / __/
|__/|__/_/_/\__,_/_/ /_/\__, / \____/\____/_/ \___/
/____/
16:37:54,319 INFO [org.wildfly.security] (ServerService Thread Pool -- 6) ELY00001: WildFly Elytron version 1.11.3.Final
....
Emmanuel
[1]: https://github.com/wildfly/wildfly-core/pull/4145
4 years, 4 months
Updating the wildfly.org site
by Brian Stansberry
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
https://www.stage.jboss.org/wildflysite/
If you'd like to report and issue, you can do so at
https://github.com/jbossorg/wildflysite/issues/new
Best regards,
Brian
4 years, 4 months
Possible component upgrades report - Wildfly
by thofman＠redhat.com
Generated at 02:01:49 SGT 2020-05-31
Searched in following repositories:
* Central: https://repo1.maven.org/maven2/
* JBossPublic: https://repository.jboss.org/nexus/content/repositories/public/
Possible upgrades:
com.github.ben-manes.caffeine:caffeine:2.8.2 -> 2.8.4 (Central)
com.squareup.okhttp3:okhttp:3.9.0 -> 3.9.1 (Central)
com.sun.activation:jakarta.activation:1.2.1 -> 1.2.2 (Central)
com.sun.istack:istack-commons-runtime:3.0.10 -> 3.0.11 (Central)
com.sun.xml.bind.external:relaxng-datatype:2.3.3-b02 -> 2.3.3 (Central)
com.sun.xml.fastinfoset:FastInfoset:1.2.13 -> 1.2.18 (Central)
io.netty:netty-all:4.1.48.Final -> 4.1.50.Final (Central)
io.opentracing.contrib:opentracing-interceptors:0.0.4 -> 0.0.5 (Central)
io.opentracing.contrib:opentracing-tracerresolver:0.1.5 -> 0.1.8 (Central)
io.smallrye:smallrye-fault-tolerance:4.2.0 -> 4.2.1 (Central)
io.smallrye:smallrye-health:2.2.0 -> 2.2.1 (Central)
io.smallrye:smallrye-metrics:2.4.0 -> 2.4.2 (Central)
io.smallrye:smallrye-open-api:1.2.3 -> 1.2.4 (Central)
io.undertow.js:undertow-js:1.0.2.Final -> 1.0.3.Final (Central)
joda-time:joda-time:2.9.7 -> 2.9.9 (Central)
net.bytebuddy:byte-buddy:1.9.11 -> 1.9.16 (Central)
org.apache.activemq:activemq-artemis-native:1.0.0 -> 1.0.1 (Central)
org.apache.activemq:artemis-amqp-protocol:2.10.1 -> 2.12.0 (Central)
org.apache.activemq:artemis-jms-client:2.10.1 -> 2.13.0 (Central)
org.apache.avro:avro:1.7.6 -> 1.7.7 (Central)
org.apache.cxf.xjc-utils:cxf-xjc-runtime:3.3.0 -> 3.3.1 (Central)
org.apache.james:apache-mime4j:0.6 -> 0.6.1 (Central)
org.apache.myfaces.core:myfaces-api:2.3.1 -> 2.3.6 (Central)
org.apache.openjpa:openjpa-kernel:2.4.2 -> 2.4.3 (Central)
org.apache.qpid:proton-j:0.33.2 -> 0.33.4 (Central)
org.apache.santuario:xmlsec:2.1.4 -> 2.1.5 (Central)
org.apache.ws.xmlschema:xmlschema-core:2.2.4 -> 2.2.5 (Central)
org.bitbucket.b_c:jose4j:0.7.0 -> 0.7.1 (Central)
org.bouncycastle:bcprov-jdk15on:1.65 -> 1.65.01 (Central)
org.codehaus.jettison:jettison:1.4.0 -> 1.4.1 (Central)
org.eclipse.microprofile.fault-tolerance:microprofile-fault-tolerance-api:2.1 -> 2.1.1 (Central)
org.eclipse.microprofile.metrics:microprofile-metrics-api:2.3 -> 2.3.2 (Central)
org.eclipse.microprofile.rest.client:microprofile-rest-client-api:1.4.0 -> 1.4.1 (Central)
org.eclipse.persistence:eclipselink:2.7.3 -> 2.7.7 (Central)
org.hibernate:hibernate-search-backend-jms:5.10.7.Final -> 5.10.9.Final (Central)
org.jboss.activemq.artemis.integration:artemis-wildfly-integration:1.0.2 -> 1.0.2-wildfly-1 (JBossPublic)
org.jboss.arquillian.container:arquillian-container-test-spi:1.4.0.Final -> 1.4.1.Final (Central)
org.jboss.security:jbossxacml:2.0.8.Final -> 2.0.9.Final (JBossPublic)
org.wildfly.galleon-plugins:wildfly-config-gen:4.2.6.Final -> 4.2.7.Final (Central)
org.wildfly.transaction:wildfly-transaction-client:1.1.11.Final -> 1.1.12.Final (Central)
xalan:serializer:2.7.1.jbossorg-4 -> 2.7.2 (Central)
41 items
Report generated by Maven Dependency Updater
https://github.com/jboss-set/maven-dependency-updater
4 years, 4 months
Re: [wildfly-dev] Updating the wildfly.org site
by Kabir Khan
On Tue, 26 May 2020 at 14:23, James Cobb <jcobb(a)redhat.com> wrote:
> Inline...
>
> On May 26, 2020, at 7:36 AM, Brian Stansberry <brian.stansberry(a)redhat.com>
> wrote:
>
>
>
> 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?
>>
>
> Yes.
>
> 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.
>
>>
>> Thanks,
>>
>> Kabir
>>
>> 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
>>>
>>> https://www.stage.jboss.org/wildflysite/
>>>
>>> If you'd like to report and issue, you can do so at
>>>
>>> https://github.com/jbossorg/wildflysite/issues/new
>>>
>>> Best regards,
>>> Brian
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>>
>
> --
> Brian Stansberry
> Manager, Senior Principal Software Engineer
> Red Hat
>
>
>
4 years, 5 months
Possible component upgrades report - Wildfly
by thofman＠redhat.com
Generated at 01:49:48 SGT 2020-05-24
Searched in following repositories:
* Central: https://repo1.maven.org/maven2/
* JBossPublic: https://repository.jboss.org/nexus/content/repositories/public/
Possible upgrades:
com.github.ben-manes.caffeine:caffeine:2.8.2 -> 2.8.4 (Central)
com.squareup.okhttp3:okhttp:3.9.0 -> 3.9.1 (Central)
com.sun.activation:jakarta.activation:1.2.1 -> 1.2.2 (Central)
com.sun.istack:istack-commons-runtime:3.0.10 -> 3.0.11 (Central)
com.sun.xml.bind.external:relaxng-datatype:2.3.3-b02 -> 2.3.3 (Central)
com.sun.xml.fastinfoset:FastInfoset:1.2.13 -> 1.2.18 (Central)
io.netty:netty-all:4.1.48.Final -> 4.1.50.Final (Central)
io.opentracing.contrib:opentracing-interceptors:0.0.4 -> 0.0.5 (Central)
io.opentracing.contrib:opentracing-tracerresolver:0.1.5 -> 0.1.8 (Central)
io.smallrye:smallrye-health:2.2.0 -> 2.2.1 (Central)
io.smallrye:smallrye-metrics:2.4.0 -> 2.4.2 (Central)
io.undertow.js:undertow-js:1.0.2.Final -> 1.0.3.Final (Central)
joda-time:joda-time:2.9.7 -> 2.9.9 (Central)
net.bytebuddy:byte-buddy:1.9.11 -> 1.9.16 (Central)
org.apache.activemq:activemq-artemis-native:1.0.0 -> 1.0.1 (Central)
org.apache.activemq:artemis-amqp-protocol:2.10.1 -> 2.12.0 (Central)
org.apache.avro:avro:1.7.6 -> 1.7.7 (Central)
org.apache.cxf.xjc-utils:cxf-xjc-runtime:3.3.0 -> 3.3.1 (Central)
org.apache.james:apache-mime4j:0.6 -> 0.6.1 (Central)
org.apache.myfaces.core:myfaces-api:2.3.1 -> 2.3.6 (Central)
org.apache.openjpa:openjpa-kernel:2.4.2 -> 2.4.3 (Central)
org.apache.qpid:proton-j:0.33.2 -> 0.33.4 (Central)
org.apache.santuario:xmlsec:2.1.4 -> 2.1.5 (Central)
org.apache.ws.xmlschema:xmlschema-core:2.2.4 -> 2.2.5 (Central)
org.bitbucket.b_c:jose4j:0.7.0 -> 0.7.1 (Central)
org.codehaus.jettison:jettison:1.4.0 -> 1.4.1 (Central)
org.eclipse.microprofile.metrics:microprofile-metrics-api:2.3 -> 2.3.2 (Central)
org.eclipse.microprofile.rest.client:microprofile-rest-client-api:1.4.0 -> 1.4.1 (Central)
org.eclipse.persistence:eclipselink:2.7.3 -> 2.7.7 (Central)
org.hibernate:hibernate-search-backend-jms:5.10.7.Final -> 5.10.9.Final (Central)
org.jboss.activemq.artemis.integration:artemis-wildfly-integration:1.0.2 -> 1.0.2-wildfly-1 (JBossPublic)
org.jboss.arquillian.container:arquillian-container-test-spi:1.4.0.Final -> 1.4.1.Final (Central)
org.jboss.genericjms:generic-jms-ra-jar:2.0.4.Final -> 2.0.6.Final (JBossPublic)
org.jboss.security:jbossxacml:2.0.8.Final -> 2.0.9.Final (JBossPublic)
org.wildfly.galleon-plugins:wildfly-config-gen:4.2.6.Final -> 4.2.7.Final (Central)
org.wildfly.transaction:wildfly-transaction-client:1.1.11.Final -> 1.1.12.Final (Central)
xalan:serializer:2.7.1.jbossorg-4 -> 2.7.2 (Central)
37 items
Report generated by Maven Dependency Updater
https://github.com/jboss-set/maven-dependency-updater
4 years, 5 months
