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.
4 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
5 years, 4 months
JDK 15 is in Rampdown Phase One
by Rory O'Donnell
Hi David & Richard,
*Per the JDK 15 schedule , we are in Rampdown Phase One* *[1] *
*Please advise if you find any issues while testing the latest Early
Access builds.
*
* Schedule for JDK 15
o *2020/06/11 Rampdown Phase One*
o 2020/07/16 Rampdown Phase Two
o 2020/08/06 Initial Release Candidate
o 2020/08/20 Final Release Candidate
o 2020/09/15 General Availability
* Features included in JDK 15:
o JEP 339: Edwards-Curve Digital Signature Algorithm (EdDSA)
<http://openjdk.java.net/jeps/339>
o JEP 360: Sealed Classes (Preview) <http://openjdk.java.net/jeps/360>
o JEP 371: Hidden Classes <http://openjdk.java.net/jeps/371>
o JEP 372: Remove the Nashorn JavaScript Engine
<http://openjdk.java.net/jeps/372>
o JEP 373: Reimplement the Legacy DatagramSocket API
<https://openjdk.java.net/jeps/373>
o JEP 374: Disable and Deprecate Biased Locking
<http://openjdk.java.net/jeps/374>
o JEP 375: Pattern Matching for instanceof (Second Preview)
<https://openjdk.java.net/jeps/375>
o JEP 377: ZGC: A Scalable Low-Latency Garbage Collector
<http://openjdk.java.net/jeps/377>
o JEP 378: Text Blocks <http://openjdk.java.net/jeps/378>
o JEP 379: Shenandoah: A Low-Pause-Time Garbage Collector
<https://openjdk.java.net/jeps/379>
o JEP 381: Remove the Solaris and SPARC Ports
<https://openjdk.java.net/jeps/381>
o JEP 383: Foreign-Memory Access API (Second Incubator)
<https://openjdk.java.net/jeps/383>
o JEP 384: Records (Second Preview)
<https://openjdk.java.net/jeps/384>
o JEP 385: Deprecate RMI Activation for Removal
<https://openjdk.java.net/jeps/385>
*JDK 15 **Early Access build 28 **is available**at : - jdk.java.net/15/*
These early-access, open-source builds are provided under the GNU
General Public License, version 2, with the Classpath Exception**Release
notes
* Release notes
o http://jdk.java.net/15/release-notes
* Recent fixes that might be of interest
o Build 27
+ JDK-8233215: jpackage doesn't allow enough flexibility for
file type binding
+ JDK-8244582: Remove terminally deprecated Solaris-specific
SO_FLOW_SLA socket option
+ JDK-8245068: Implement Deprecation of RMI Activation
+ JDK-8246770: Atomic::add() with 64 bit value fails to link
on 32-bit platforms
# Reported by JaCoCo
o Build 26
+ JDK-8240871: SSLEngine handshake status immediately after
the handshake can be NOT_HANDSHAKING rather than FINISHED
with TLSv1.3
# Reported by Apache Tomcat
o Build 25
+ JDK-8206925: Support the certificate_authorities extension
+ JDK-8239480: Support for CLDR version 37
+ JDK-8243925: Toolkit#getScreenInsets() returns wrong value
on HiDPI screens (Windows)
*JDK 16 Early Access build 2 ****is available**at : - jdk.java.net/16/*
These early-access, open-source builds are provided under the GNU
General Public License, version 2, with the Classpath Exception.*
*
*_Survey on _**_jinfo, jmap, jstack serviceability tools in JDK:_ *
* Oracle is considering deprecation and (eventual) removal of 3 JDK
tools - jinfo, jmap, jstack.
* The Survey Link
<https://www.questionpro.com/a/TakeSurvey?tt=n%2BDcx/aY3aA%3D> will
remain open through July 15 2020.
Rgds, Rory
[1] https://mail.openjdk.java.net/pipermail/jdk-dev/2020-June/004401.html
--
Rgds, Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin, Ireland
5 years, 4 months
