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, 9 months
Possible component upgrades report - Wildfly
by thofman@redhat.com
Generated at 01:48:50 SGT 2020-03-29
Searched in following repositories:
* Central: https://repo1.maven.org/maven2/
* JBossPublic: https://repository.jboss.org/nexus/content/repositories/public/
Possible upgrades:
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.faces:jsf-impl:2.3.9.SP07 -> 2.3.9.SP08 (JBossPublic)
com.sun.istack:istack-commons-runtime:3.0.10 -> 3.0.11 (Central)
com.sun.xml.fastinfoset:FastInfoset:1.2.13 -> 1.2.18 (Central)
io.netty:netty-all:4.1.45.Final -> 4.1.48.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.reactivex.rxjava2:rxjava:2.2.5 -> 2.2.19 (Central)
io.smallrye:smallrye-metrics:2.4.0 -> 2.4.1 (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.11.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.3 (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.bouncycastle:bcmail-jdk15on:1.62 -> 1.63 (Central)
org.codehaus.jettison:jettison:1.4.0 -> 1.4.1 (Central)
org.eclipse:yasson:1.0.5 -> 1.0.6 (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.6 (Central)
org.hibernate:hibernate-search-backend-jms:5.10.7.Final -> 5.10.9.Final (Central)
org.hibernate.validator:hibernate-validator:6.0.18.Final -> 6.0.19.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.hal:hal-console:3.2.7.Final -> 3.2.8.Final (JBossPublic)
org.jboss.ironjacamar:ironjacamar-common-api:1.4.20.Final -> 1.4.21.Final (Central)
org.jboss.narayana:jbosstxbridge:5.10.1.Final -> 5.10.4.Final (Central)
org.jboss.security:jbossxacml:2.0.8.Final -> 2.0.9.Final (JBossPublic)
org.jboss.weld:weld-core-impl:3.1.3.Final -> 3.1.4.Final (Central)
org.reactivestreams:reactive-streams:1.0.2 -> 1.0.3 (Central)
xalan:serializer:2.7.1.jbossorg-4 -> 2.7.2 (Central)
39 items
Report generated by Maven Dependency Updater
https://github.com/jboss-set/maven-dependency-updater
4 years, 8 months
WildFly CI builds on ARM64
by Martin Grigorov
Hello WildFly team,
I work for one of the bigger ARM64 hardware providers.
My client is willing to donate a build server that could be used as a
TeamCity agent to execute the WildFly test suites on ARM64 Linux.
The aim is to make sure that WildFly is running fine on ARM64 architecture
in the long run.
I've ran 'mvn install' on one of our systems and it is passing
successfully.
If a problem arises in the future on ARM64 then me and my colleagues would
be glad to help with any ARM related issues!
Is this something you would be interested to have ?
Kind regards,
Martin Grigorov
4 years, 8 months
Possible component upgrades report - Wildfly
by thofman@redhat.com
Generated at 01:49:02 SGT 2020-03-22
Searched in following repositories:
* Central: https://repo1.maven.org/maven2/
* JBossPublic: https://repository.jboss.org/nexus/content/repositories/public/
Possible upgrades:
com.fasterxml.jackson.core:jackson-annotations:2.10.1 -> 2.10.3 (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.fastinfoset:FastInfoset:1.2.13 -> 1.2.17 (Central)
io.netty:netty-all:4.1.45.Final -> 4.1.48.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.reactivex.rxjava2:rxjava:2.2.5 -> 2.2.19 (Central)
io.smallrye:smallrye-metrics:2.4.0 -> 2.4.1 (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.11.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.3 (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.bouncycastle:bcmail-jdk15on:1.62 -> 1.63 (Central)
org.codehaus.jettison:jettison:1.4.0 -> 1.4.1 (Central)
org.eclipse:yasson:1.0.5 -> 1.0.6 (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.6 (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.narayana:jbosstxbridge:5.10.1.Final -> 5.10.4.Final (Central)
org.jboss.security:jbossxacml:2.0.8.Final -> 2.0.9.Final (JBossPublic)
org.reactivestreams:reactive-streams:1.0.2 -> 1.0.3 (Central)
xalan:serializer:2.7.1.jbossorg-4 -> 2.7.2 (Central)
35 items
Report generated by Maven Dependency Updater
https://github.com/jboss-set/maven-dependency-updater
4 years, 8 months
WildFly 19 is released!
by Brian Stansberry
Hello everyone,
I'm very happy to announce that WildFly 19.0.0.Final is now available for
download at https://wildfly.org/downloads/! Please try it out and give us
your feedback.
The big new thing in WildFly 19 is support for the Eclipse MicroProfile 3.3
platform specifications. Since WildFly 18 we've added support for
MicroProfile Fault Tolerance, MicroProfile JWT Authentication and
MicroProfile OpenAPI. We also updated our Config, Health Check, Metrics,
OpenTracing and REST Client implementations to support the updated versions
of those specs that were part of MicroProfile 3.3.
Please see my post at
https://wildfly.org/news/2020/03/18/WildFly19-Final-Released/ to learn more.
Onward to WildFly 20!
I hope you enjoy the release, but more importantly I hope you are all safe
and well.
Take care,
Brian Stansberry
Manager, Senior Principal Software Engineer
Red Hat
4 years, 8 months