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, 2 months
Re: WFLYCTL0365 writing default-mdb-instance-pool attribute of ejb3 subsystem
by Cheng Fang
Thanks for reporting. This issue has been fixed (more details please see
1. WFLY-13973 <https://issues.redhat.com/browse/WFLY-13973>
Writing default-mdb-instance-pool to ejb3 subsystem throws
IllegalStateException)
On Wed, Oct 28, 2020 at 12:56 PM David LE BORGNE <dleborgne(a)coheris.com>
wrote:
> Hi everyone !
>
> The following JBoss CLI command :
> /subsystem=ejb3:write-attribute(name="default-mdb-instance-pool",
> value="mdb-strict-max-pool")
>
> is not working anymore with WildFly 21.0.0.Final and gets an error :
> WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException:
> WFLYCTL0365: Capability 'org.wildfly.ejb3.pool-config.mdb-default' is
> unknown in context 'global'.
>
> We used the CLI command since WF17 with no problem. Is there anything
> changed in WF21 (WFLY-13433 ?) that can explain the error ? Is the command
> useless or do we need to run another command before ?
>
> Thank you !
> David Le Borgne
> _______________________________________________
> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
3 years, 6 months
WFLYCTL0365 writing default-mdb-instance-pool attribute of ejb3 subsystem
by David LE BORGNE
Hi everyone !
The following JBoss CLI command :
/subsystem=ejb3:write-attribute(name="default-mdb-instance-pool", value="mdb-strict-max-pool")
is not working anymore with WildFly 21.0.0.Final and gets an error :
WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0365: Capability 'org.wildfly.ejb3.pool-config.mdb-default' is unknown in context 'global'.
We used the CLI command since WF17 with no problem. Is there anything changed in WF21 (WFLY-13433 ?) that can explain the error ? Is the command useless or do we need to run another command before ?
Thank you !
David Le Borgne
3 years, 6 months
JDK 16 EA build 21 is available
by Rory O'Donnell
Hi David & Richard,
OpenJDK 16 Early Access build 21**is now available at
http://jdk.java.net/16
* These early-access , open-source builds are provided under the
o GNU General Public License, version 2, with the Classpath
Exception <http://openjdk.java.net/legal/gplv2+ce.html>.
* Schedule (proposed)
2020/12/10 Rampdown Phase One
2021/01/14 Rampdown Phase Two
2021/02/04 Initial Release Candidate
2021/02/18 Final Release Candidate
2021/03/16 General Availability
* Features:
o JEPs targeted to JDK 16, so far:
+ JEP 338: Vector API (Incubator)
<https://openjdk.java.net/jeps/338>
+ JEP 347: Enable C++14 Language Features
<https://openjdk.java.net/jeps/347>
+ JEP 357: Migrate from Mercurial to Git
<https://openjdk.java.net/jeps/357>
+ JEP 369: Migrate to GitHub <https://openjdk.java.net/jeps/369>
+ JEP 376: ZGC: Concurrent Thread-Stack Processing
<https://openjdk.java.net/jeps/376>
+ JEP 386: Alpine Linux Port <https://openjdk.java.net/jeps/386>
+ JEP 387: Elastic Metaspace <https://openjdk.java.net/jeps/387>
+ JEP 388: Windows/AArch64 Port
<https://openjdk.java.net/jeps/388>
**
* Changes in recent builds that maybe of interest:
o Build 21
+ JDK-8236862: Enhance support of Proxy class
+ JDK-8237990: Added Property to Control LDAP Authentication
Mechanisms Allowed to Authenticate Over Clear Connections
+ JDK-8242068: Signed JAR support for RSASSA-PSS and EdDSA
+ JDK-8245417: Improve certificate chain handling
+ JDK-8253952: Refine ZipOutputStream.putNextEntry() to
recalculate ZipEntry's compressed size
o Build 20
+ JDK-8232092: (fs) Files::isWritable returns false on a
writeable root directory (win)
# Reported by JUnit5
+ JDK-8248262: Wrong link target in
ModuleDescriptor#isAutomatic's API documentation
# Reported by JUnit5
+ JDK-8253965: Delete the outdated java.awt.PeerFixer class
+ JDK-8253566: clazz.isAssignableFrom will return false for
interface implementors
# Found by Hibernate Validator
+ JDK-8254177: US/Pacific-New Zone name removed as part of
tzdata2020b
o Build 19
+ JDK-8253761: Wrong URI syntax printed by jar --describe-module
# Reported by JUnit5
Project Lanai Early-Access Build: EA 6 Build 16-lanai+2-229
<http://jdk.java.net/lanai/> (2020/10/4)
* These early-access builds are provided under the GNU General Public
License, version 2, with the Classpath Exception
<http://openjdk.java.net/legal/gplv2+ce.html>.
* These builds are based upon the latest state of the current in
development JDK, and so may contain new features and unresolved bugs
unrelated to Project Lanai. Project Lanai Wiki:
https://wiki.openjdk.java.net/display/lanai/Main
* Please send feedback via e-mail tolanai-dev(a)openjdk.java.net
<mailto:lanai-dev@openjdk.java.net>. To send e-mail to this address
you must firstsubscribe to the mailing list
<https://mail.openjdk.java.net/mailman/listinfo/lanai-dev>.
Project Panama Early-Access Build: Build 16-panama+2-193
<http://jdk.java.net/panama/> (2020/10/1)
* These early-access, open-source builds are provided under the GNU
General Public License, version 2, with the Classpath Exception
<http://openjdk.java.net/legal/gplv2+ce.html>.
* These builds are based on an incomplete version of JDK 16.
* Please send feedback via e-mail topanama-dev(a)openjdk.java.net
<mailto:panama-dev@openjdk.java.net>. To send e-mail to this address
you must firstsubscribe to the mailing list
<http://mail.openjdk.java.net/mailman/listinfo/panama-dev>.
Oracle JRE and JDK Cryptographic Roadmap has been updated [1]
* Oracle has announced plans to add support for x25519 and x448 named
elliptic curve groups to TLS.
* Support is targeted for JDK 11 with the January 2021 CPU release.
Oracle Critical Patch Update released 21-Oct-2020
* https://www.oracle.com/security-alerts/cpuoct2020.html
*__*
Rgds,Rory
[1] https://java.com/en/jre-jdk-cryptoroadmap.html
--
Rgds, Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin, Ireland
3 years, 6 months
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
3 years, 6 months
WildFly 21 is released!
by Brian Stansberry
Hello everyone,
I'm very happy to announce that WildFly 21.0.0.Final is now available for
download at https://wildfly.org/downloads/. Please try it out and give us
your feedback.
WildFly 21 has a number of new features, but the biggest is GA-level
support for building your app + a customized WildFly server into a bootable
jar. This is particularly useful for cloud use cases. In support of that
feature, we've also significantly expanded the number of Galleon layers we
provide, adding layers for things like EJB, Webservices, JSF, Batch, and
more messaging options. Galleon layers make it easy to provision a WildFly
server slimmed and customized to your needs, either in a bootable jar or in
a traditional filesystem layout. Adding more layers expands the number of
use cases where you can take advantage of that capability
Learn more in my post at
https://www.wildfly.org/news/2020/10/13/WildFly21-Final-Released/.
Onward to WildFly 22!
Thank you for you support of WildFly.
Best regards,
Brian
3 years, 6 months
JDK 16 EA build 18 is now available
by Rory O'Donnell
Hi David & Richard,
OpenJDK 16 Early Access build 18**is now available at http://jdk.java.net/16
* These early-access , open-source builds are provided under the
o GNU General Public License, version 2, with the Classpath
Exception <http://openjdk.java.net/legal/gplv2+ce.html>.
* Features:
o JEPs proposed to target JDK 16
+ JEP 376: ZGC: Concurrent Thread-Stack Processing
<https://openjdk.java.net/jeps/376>
+ JEP 386: Alpine Linux Port <https://openjdk.java.net/jeps/386>
+ JEP 388: Windows/AArch64 Port
<https://openjdk.java.net/jeps/388>
o JEPs targeted to JDK 16, so far:
+ JEP 338: Vector API (Incubator)
<https://openjdk.java.net/jeps/338>
+ JEP 347: Enable C++14 Language Features
<https://openjdk.java.net/jeps/347>
+ JEP 357: Migrate from Mercurial to Git
<https://openjdk.java.net/jeps/357>
+ JEP 369: Migrate to GitHub <https://openjdk.java.net/jeps/369>
+ JEP 387: Elastic Metaspace <https://openjdk.java.net/jeps/387>
* Release Notes are available at http://jdk.java.net/16/release-notes
**
* Changes in recent builds that maybe of interest:
o Build 18
+ JDK-8235710: Removal of Legacy Elliptic Curves
+ JDK-8245527: LDAP Channel Binding support for Java GSS/Kerberos
+ JDK-8252739: Deflater.setDictionary(byte[], int off, int
len) ignores the starting offset for the dictionary
# Reported by Apache Lucene
o Build 17
+ JDK-8247281: Object monitors no longer keep strong
references to their associated object
+ JDK-8202473: A type variable with multiple bounds does not
correctly place type annotation
# Reported by ByteBuddy
+ JDK-8234808: jdb quoted option parsing broken
# Reported by Apache Tomcat
o Build 16
+ JDK-8172366: SUN, SunRsaSign, and SunEC Providers Supports
SHA-3 Based Signature Algorithms
+ JDK-8244706: GZIPOutputStream now sets the GZIP OS Header
Field to the correct default value
* Quality Report for September 2020 was published here [1]. Thanks to
everyone who contributed by creating features or enhancements,
logging bugs, or downloading and testing the early-access builds.
*__*
Rgds,Rory
[1]
https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+Sep...
--
Rgds, Rory O'Donnell
Quality Engineering Manager
Oracle EMEA, Dublin, Ireland
3 years, 6 months
