[JBoss JIRA] (WFLY-12229) Missing license info from core feature pack
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12229?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-12229:
------------------------------------
Fix Version/s: 17.0.1.Final
18.0.0.Beta1
> Missing license info from core feature pack
> -------------------------------------------
>
> Key: WFLY-12229
> URL: https://issues.jboss.org/browse/WFLY-12229
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 17.0.0.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 17.0.1.Final, 18.0.0.Beta1
>
>
> The docs/licenses/core-feature-pack-licenses.html file and thus the overall docs/licenses/licenses.html file is missing most of the expected content. Seems to have only org.wildfly.core:wildfly-event-logger and various org.wildfly.security items.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months
[JBoss JIRA] (WFCORE-4557) The read http-upgrade-enabled attribute operation acquires the write lock unnecessarily
by Yeray Borges (Jira)
Yeray Borges created WFCORE-4557:
------------------------------------
Summary: The read http-upgrade-enabled attribute operation acquires the write lock unnecessarily
Key: WFCORE-4557
URL: https://issues.jboss.org/browse/WFCORE-4557
Project: WildFly Core
Issue Type: Bug
Components: Management
Reporter: Yeray Borges
Assignee: Yeray Borges
When we are reading the http-upgrade-enabled, the model is read acquiring the write lock. That could make the operation block until the write lock is released by any other underlying operation that previously has acquired it.
The read handler only reads the value and put it in the response, so taking the write lock here is unnecessary.
This issue affects the ongoing work in WFCORE-4283, there, we could have servers starting with the write lock taken, so it negatively affects to any reading of this attribute.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months
[JBoss JIRA] (ELY-1840) Strong type defined credential store in client schema
by Darran Lofthouse (Jira)
Darran Lofthouse created ELY-1840:
-------------------------------------
Summary: Strong type defined credential store in client schema
Key: ELY-1840
URL: https://issues.jboss.org/browse/ELY-1840
Project: WildFly Elytron
Issue Type: Feature Request
Components: Authentication Client, Credential Store
Reporter: Darran Lofthouse
We are trying to use more strongly typed self describing configuration however the credential store still depends on configuration properties - this is fine for custom stores but our implementation needs to be easy to configure.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months