January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14006) Consider having the Extension implementation for extensions with deprecated subsystems register themselves as such

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14006?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-14006: ----------------------------------------- +1 [~yersan] > Consider having the Extension implementation for extensions with deprecated subsystems register themselves as such > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-14006 > URL: https://issues.redhat.com/browse/WFLY-14006 > Project: WildFly > Issue Type: Task > Components: Management > Reporter: Brian Stansberry > Priority: Minor > > ExtensionContext.registerSubsystem has an overloaded variant that takes a boolean 'deprecated' parameter. We never use it. > For deprecated subsystems we *perhaps* should. > I think most of our deprecated subsystems are using the SimpleResourceDefinition.setDeprecated API to trigger deprecation logging if the subsystem is actually added. So this extension call really is just for the case where the extension is included in the config but is not used for adding a subsystem. That's kind of a corner case so it's a valid question whether we want to add this setting and end up writing *two* messages to the log. > So this issue is to track at least considering it. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14263) Outdated "Remote EJB invocations via JNDI - EJB client API or remote-naming project" document

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-14263?page=com.atlassian.jira.plugi... ] Cheng Fang commented on WFLY-14263: ----------------------------------- Need to update {{docs/src/main/asciidoc/_developer-guide/Remote_EJB_invocations_via_JNDI_-_EJB_client_API_or_remote-naming_project.adoc}} to remove the reference to {{jboss-remote-naming}}, and also remove some unnecessary use of {{wildflyVersion}}. {{org.jboss.naming.remote.client.InitialContextFactory}} has been deprecated and should use {{org.wildfly.naming.client.WildFlyInitialContextFactory}} instead. > Outdated "Remote EJB invocations via JNDI - EJB client API or remote-naming project" document > --------------------------------------------------------------------------------------------- > > Key: WFLY-14263 > URL: https://issues.redhat.com/browse/WFLY-14263 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Brian Stansberry > Assignee: Cheng Fang > Priority: Major > > This doc looks wrong: > https://docs.wildfly.org/21/Developer_Guide.html#Remote_EJB_invocations_v... > AFAICT WildFly no longer ships org.jboss:jboss-remote-naming. > There are also a number of places where that doc refers to WildFly 21 which I believe is a dynamic value that is now incorrect. It's generally better to not include specific WildFly versions in the docs, as the URL for our docs already include a version number. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (AG-147) Add SpringBoot starter

by Luis Barreiro (Jira)

[ https://issues.redhat.com/browse/AG-147?page=com.atlassian.jira.plugin.sy... ] Luis Barreiro updated AG-147: ----------------------------- Issue Type: Feature Request (was: Bug) > Add SpringBoot starter > ---------------------- > > Key: AG-147 > URL: https://issues.redhat.com/browse/AG-147 > Project: Agroal > Issue Type: Feature Request > Components: spring > Affects Versions: 1.8 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Major > Fix For: 1.9 > > > A SpringBoot starter project will allow SpringBoot applications to use Agroal as the connection provider. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14248) Sync fixes/improvements of o:socket into f:websocket

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-14248?page=com.atlassian.jira.plugi... ] Parul Sharma reassigned WFLY-14248: ----------------------------------- Assignee: Parul Sharma (was: Farah Juma) > Sync fixes/improvements of o:socket into f:websocket > ---------------------------------------------------- > > Key: WFLY-14248 > URL: https://issues.redhat.com/browse/WFLY-14248 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 22.0.0.Beta1 > Reporter: erick leal > Assignee: Parul Sharma > Priority: Major > > https://github.com/eclipse-ee4j/mojarra/pull/4803 -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5926) Executable Model compiler interprets numeric strings with leading 0 as Octal values

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5926?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-5926. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/2510ff59c9627ed72ced159f2f15c07... > Executable Model compiler interprets numeric strings with leading 0 as Octal values > ----------------------------------------------------------------------------------- > > Key: DROOLS-5926 > URL: https://issues.redhat.com/browse/DROOLS-5926 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.47.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: integer-string-interpreted-as-octal-value-with-exec-model.zip > > > The Executable Model compiler interprets numeric strings with leading 0 as Octal values. This behaviour breaks compatibility with the MVEL compiler, which interprets them as decimal. > For example the following rule will fail to compile with Executable Model, because 800 is not a valid octal value: > {noformat} > rule "Test" > when > Fact(x == "0800") > then > end > {noformat} > The following error is given at compilation time: > {noformat} > Error Messages: > Message [id=1, level=ERROR, path=src/main/java/org/build/example/rules/Rules3F1F75C706B36DFEDB0E8DD2A7622BF6RuleMethods0.java, line=23, column=123 > text=integer number too large] > {noformat} > The compilation works fine with the MVEL compiler. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5238) The Elytron applicationKS uses a different type to the legacy realm.

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-5238: ---------------------------------------- Summary: The Elytron applicationKS uses a different type to the legacy realm. Key: WFCORE-5238 URL: https://issues.redhat.com/browse/WFCORE-5238 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 14.0.0.Beta5 The legacy security realm automatically can generate a JKS keystore based on the following configuration: {code:java} <security-realm name="ApplicationRealm"> <server-identities> <ssl> <keystore path="application.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/> </ssl> </server-identities> <authentication> <local default-user="$local" allowed-users="*" skip-group-loading="true"/> <properties path="application-users.properties" relative-to="jboss.server.config.dir"/> </authentication> <authorization> <properties path="application-roles.properties" relative-to="jboss.server.config.dir"/> </authorization> </security-realm> {code} The Elytron subsystem can also generate one but is configured to use PKCS#12: {code:java} <tls> <key-stores> <key-store name="applicationKS"> <credential-reference clear-text="password"/> <implementation type="PKCS12"/> <file path="application.keystore" relative-to="jboss.server.config.dir"/> </key-store> </key-stores> <key-managers> <key-manager name="applicationKM" key-store="applicationKS" generate-self-signed-certificate-host="localhost"> <credential-reference clear-text="password"/> </key-manager> </key-managers> <server-ssl-contexts> <server-ssl-context name="applicationSSC" key-manager="applicationKM"/> </server-ssl-contexts> </tls> {code} PKCS#12 would be the better option for the future but as this KeyStore definition is potentially reusing an existing generated KeyStore we will need to drop back to JKS. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14264) microprofile test failure "IOException: DerInputStream.getLength(): lengthTag=109, too big."

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-14264?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFLY-14264: ------------------------------------ Priority: Blocker (was: Major) > microprofile test failure "IOException: DerInputStream.getLength(): lengthTag=109, too big." > -------------------------------------------------------------------------------------------- > > Key: WFLY-14264 > URL: https://issues.redhat.com/browse/WFLY-14264 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 22.0.0.Beta1 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 22.0.0.Final > > Attachments: TEST-org.wildfly.test.integration.microprofile.health.MicroProfileHealthApplicationReadyHTTPEndpointTestCase.xml, org.wildfly.test.integration.microprofile.health.MicroProfileHealthApplicationReadyHTTPEndpointTestCase-output.txt, org.wildfly.test.integration.microprofile.health.MicroProfileHealthApplicationReadyHTTPEndpointTestCase.txt > > > The following error is being encountered running the microprofile tests: > {code:java} > [0m[31m16:57:56,276 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service org.wildfly.security.key-store.applicationKS: org.jboss.msc.service.StartException in service org.wildfly.security.key-store.applicationKS: WFLYELY00004: Unable to start the service.[0m[31m16:57:56,276 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service org.wildfly.security.key-store.applicationKS: org.jboss.msc.service.StartException in service org.wildfly.security.key-store.applicationKS: WFLYELY00004: Unable to start the service. at org.wildfly.extension.elytron.KeyStoreService.start(KeyStoreService.java:191) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363) at java.lang.Thread.run(Thread.java:748)Caused by: java.io.IOException: DerInputStream.getLength(): lengthTag=109, too big. at sun.security.util.DerInputStream.getLength(DerInputStream.java:605) at sun.security.util.DerValue.init(DerValue.java:391) at sun.security.util.DerValue.<init>(DerValue.java:332) at sun.security.util.DerValue.<init>(DerValue.java:345) at sun.security.pkcs12.PKCS12KeyStore.engineLoad(PKCS12KeyStore.java:1941) at java.security.KeyStore.load(KeyStore.java:1445) at org.wildfly.security.keystore.AtomicLoadKeyStoreSpi.engineLoad(AtomicLoadKeyStoreSpi.java:53) at java.security.KeyStore.load(KeyStore.java:1445) at org.wildfly.extension.elytron.KeyStoreService.start(KeyStoreService.java:163) ... 8 more {code} > > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14170) Remove wildfly-ee and wildfly-servlet feature pack's dependency on the wildfly-core feature pack

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14170?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14170: ------------------------------------ Fix Version/s: 23.0.0.Beta1 (was: 22.0.0.Final) > Remove wildfly-ee and wildfly-servlet feature pack's dependency on the wildfly-core feature pack > ------------------------------------------------------------------------------------------------ > > Key: WFLY-14170 > URL: https://issues.redhat.com/browse/WFLY-14170 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 23.0.0.Beta1 > > > Have the wildfly-ee and wildfly-servlet feature packs incorporate the source used for the wildfly-core feature pack instead of having a feature pack dependency. > As the relevant source is in a different git repo, use GAL-319 to incorporate the source. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14169) Remove the wildfly-ee feature pack dependency on wildfly-servlet

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14169?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14169: ------------------------------------ Fix Version/s: 23.0.0.Beta1 (was: 22.0.0.Final) > Remove the wildfly-ee feature pack dependency on wildfly-servlet > ---------------------------------------------------------------- > > Key: WFLY-14169 > URL: https://issues.redhat.com/browse/WFLY-14169 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 23.0.0.Beta1 > > > Have the wildfly-ee feature pack share source with the wildfly-servlet feature pack instead of having a feature pack dependency. > As the relevant source is in the same git repo as the wildfly-ee fp's maven module this source sharing would be via maven resource plugin copying during the build, not via GAL-319. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14265) Upgrade Hibernate Validator to 6.0.22

by Jason Lee (Jira)

[ https://issues.redhat.com/browse/WFLY-14265?page=com.atlassian.jira.plugi... ] Jason Lee updated WFLY-14265: ----------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13852 (was: https://github.com/wildfly/wildfly/pull/13851) > Upgrade Hibernate Validator to 6.0.22 > ------------------------------------- > > Key: WFLY-14265 > URL: https://issues.redhat.com/browse/WFLY-14265 > Project: WildFly > Issue Type: Component Upgrade > Components: Bean Validation > Reporter: Jason Lee > Assignee: Jason Lee > Priority: Major > Fix For: 23.0.0.Beta1 > > > Tracker for Hibernate Validator upgrade to pick up incorporated fixes. > https://github.com/hibernate/hibernate-validator/compare/6.0.21.Final...6... -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2021