September 2020 - wildfly-dev - Jboss List Archives

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

2
2
0 / 0

21.0.0.Beta1: Dependency "org.picketbox:picketbox:jar:5.0.3.Final-redhat-00006"

by Wolfgang Knauf

Hi all, I try to upgrade the "wildfly-archetypes" to 21.0.0.Beta1, and compiling a project (named "multi") created from this archetype (profile: arq-managed) fails with this error: [WARNING] The POM for org.picketbox:picketbox:jar:5.0.3.Final-redhat-00006 is missing, no dependency information available [ERROR] Failed to execute goal on project multi: Could not resolve dependencies for project foo.bar:multi:pom:0.1-SNAPSHOT: Failure to find org.picketbox:picketbox:jar:5.0.3.Final-redhat-00006 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] The file seems to be only available here: https://maven.repository.redhat.com/ga/org/picketbox/picketbox/5.0.3.Fina... This repository is defined in https://repo.maven.apache.org/maven2/org/wildfly/bom/wildfly/21.0.0.Beta1... When building a project from archetype for 20.0.0.Final, then picketbox "5.0.3.Final-redhat-00005" is included, which is downloaded by maven from somewhere (after deleting the files in my local repository first). The archetype just defines a dependency "org.wildfly.bom:wildfly-jakartaee8-with-tools:21.0.0.Beta1". It seems this one does not use "wildfly-21.0.0.Beta1.pom" - maybe indirectly? Does anybody have an idea? I probably could define the repository in the pom.xml created of the archetype target project, but it worked before. Attached ("dependencytree.txt") are the download log messages and the dependency tree log. Best regards Wolfgang

4 years

2
6
0 / 0

Possible component upgrades report - Wildfly Core

by JBossAS

4 years

2
1
0 / 0

Proposal for dropping some WildFly OpenSSL natives

by Farah Juma

We are revisiting the natives that we produce for each WildFly OpenSSL Natives release and would like to propose dropping the Solaris x86_64 native, the Windows i386 native, and the Linux i386 native. This would mean that these three natives would no longer be provided as part of WildFly starting from WildFly 22. We would still keep these native modules in the WildFly OpenSSL Natives repository <https://github.com/wildfly-security/wildfly-openssl-natives> so that anyone running on these platforms who needs these natives would still be able to build and make use of them on their own. Are there any thoughts or concerns about this proposal? Thanks, Farah

4 years

1
0
0 / 0

Schedule for WildFly 21.0.0.Final

by Brian Stansberry

We're coming to the end of development on WildFly 21 so I wanted to let you know the key dates: Code freeze (excluding docs): Friday, October 2 Code freeze (docs): Tuesday, October 6 Final release in wildfly.org: Thursday, October 8 By the Oct 2 code freeze, PRs for any changes meant for WF 21 should be up, with an approved review and acceptable CI results. Note that this is several days earlier than the freeze has been for previous releases. We want to cut down on the number of last minute changes. The freeze for changes to both wildfly-core and wildfly are the same day. If you have a fix for full that requires a fix for full, normal CI won't test the combination, so please be sure you've done so manually. Don't wait until the last minute. There's a bit later freeze for changes solely in the docs module ( https://github.com/wildfly/wildfly/tree/master/docs). We want to spend some time on docs related to bootable jar and Galleon layers, and since changes there won't risk introducing problems in the runtime code it's ok to accept changes for a bit longer. Best regards, Brian

4 years, 1 month

1
0
0 / 0

Organization for WildFly bootable JAR

by Jean Francois Denise

Hi, we are approaching the first final release of the WildFly bootable JAR Maven plugin[1]. This project is currently hosted in wildfly-extras organization[2]. Having it in wildfly-extras seems fine (wildfly-extras contains both mature projects and incubating ones) but we are wandering if that would make more sense to have it in the wildfly organization. The community documentation will be hosted on https://docs.wildfly.org/ Feedback welcome. Thank-you. JF [1]https://github.com/wildfly/wildfly-proposals/pull/306 [2]https://github.com/wildfly-extras/wildfly-jar-maven-plugin

4 years, 1 month

2
1
0 / 0

WildFly 21.0.0.Beta1 is now available

by Brian Stansberry

I'm pleased to announce that WildFly 21.0.0.Beta1 is now available at https://www.wildfly.org/downloads/! It's been a very busy summer for the WildFly developers, with over 300 issues resolved in this release between WildFly and WildFly Core. This includes over 20 new features, including a number of security improvements and a bunch of new Galleon layers, including ones for Batch, EJB, JSF, remote Artemis integration and Webservices. Details are at https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12313721&vers... Please try it out and give us your feedback! I expect WildFly 21.0.0.Final will be out in early October. Best regards, Brian

4 years, 1 month

1
0
0 / 0

Proposal for Automatic registration of client side / JVM wide default SSLContext

by Diana Vilkolakova

Here is a proposal for automatic registration of client side / JVM wide default SSLContext: https://github.com/wildfly/wildfly-proposals/pull/336 All feedback is welcomed. Thanks, Diana Křepinská (Vilkoláková)

4 years, 1 month

1
0
0 / 0

Release Announcement: General Availability of Java 15 / JDK 15

by Rory O'Donnell

Hi David & Richard, **Release Announcement: General Availability of Java 15 / JDK 15 [1] ** * JDK 15, the reference implementation of Java 15, is now Generally Available. * GPL-licensed OpenJDK builds from Oracle are available here: http://jdk.java.net/15/ * JDK 15 Release notes <https://www.oracle.com/java/technologies/javase/15-relnote-issues.html> JDK 15 includes fourteen features [2]: * JEP 339: Edwards-Curve Digital Signature Algorithm (EdDSA) <http://openjdk.java.net/jeps/339> * JEP 360: Sealed Classes (Preview) <http://openjdk.java.net/jeps/360> * JEP 371: Hidden Classes <http://openjdk.java.net/jeps/371> * JEP 372: Remove the Nashorn JavaScript Engine <http://openjdk.java.net/jeps/372> * JEP 373: Reimplement the Legacy DatagramSocket API <https://openjdk.java.net/jeps/373> * JEP 374: Disable and Deprecate Biased Locking <http://openjdk.java.net/jeps/374> * JEP 375: Pattern Matching for instanceof (Second Preview) <https://openjdk.java.net/jeps/375> * JEP 377: ZGC: A Scalable Low-Latency Garbage Collector <http://openjdk.java.net/jeps/377> * JEP 378: Text Blocks <http://openjdk.java.net/jeps/378> * JEP 379: Shenandoah: A Low-Pause-Time Garbage Collector <https://openjdk.java.net/jeps/379> * JEP 381: Remove the Solaris and SPARC Ports <https://openjdk.java.net/jeps/381> * JEP 383: Foreign-Memory Access API (Second Incubator) <https://openjdk.java.net/jeps/383> * JEP 384: Records (Second Preview) <https://openjdk.java.net/jeps/384> * JEP 385: Deprecate RMI Activation for Removal <https://openjdk.java.net/jeps/385> Thanks to everyone who contributed to JDK 15, whether by creating features or enhancements, logging bugs, or downloading and testing the early-access builds. OpenJDK 16 Early Access build 15**is now available at http://jdk.java.net/16 * JEPs integrated to JDK 16: o JEP 347: Enable C++14 Language Features <https://openjdk.java.net/jeps/347> o JEP 357: Migrate from Mercurial to Git <https://openjdk.java.net/jeps/357> o JEP 369: Migrate to GitHub <https://openjdk.java.net/jeps/369> * Release Notes are available at http://jdk.java.net/16/release-notes ** * Significant changes since the last availability email: o Build 15 + JDK-8244090: public lookup should find public members of public exported types (Reported by Eclipse Jetty) + JDK-8250968: Symlinks attributes not preserved when using jarsigner on zip files o Build 14 + JDK-8189744: Deprecate the JDK-specific API for setting socket options, jdk.net.Sockets + JDK-8241003: Deprecate "denigrated" java.security.cert APIs that represent DNs as Principal or String objects + JDK-8245462: The default HttpClient implementation returns cancelable futures *__* Rgds,Rory  [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2020-September/004733.html [2] https://openjdk.java.net/projects/jdk/15/ -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland

4 years, 1 month

1
0
0 / 0

Datagen Internet Services PVT LTD

by datagen Internet Services

Datagen provides the best, secure and scalable communication platform at the enterprise’s level. The services include SMS, Voice, Text-to-Speech, Email Validator and many more. Our in-house team built a highly secured platform which can handle millions of traffic that delivers satisfied and user-friendly results.

4 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev September 2020