[JBoss JIRA] (ELY-1745) The AvailableRealmsCallback should not result in a NPE if there is no mechanism configuration.
by Justin Cook (Jira)
[ https://issues.jboss.org/browse/ELY-1745?page=com.atlassian.jira.plugin.s... ]
Justin Cook commented on ELY-1745:
----------------------------------
[~dlofthouse] What do you mean for "if mechanism configuration is mandatory"? I tried callback.isOptional(), but that method always returns true
> The AvailableRealmsCallback should not result in a NPE if there is no mechanism configuration.
> ----------------------------------------------------------------------------------------------
>
> Key: ELY-1745
> URL: https://issues.jboss.org/browse/ELY-1745
> Project: WildFly Elytron
> Issue Type: Bug
> Components: API / SPI
> Reporter: Darran Lofthouse
> Assignee: Justin Cook
> Priority: Major
> Fix For: 1.8.0.CR3
>
>
> The NPE is due to the following code: -
> {noformat}
> } else if (callback instanceof AvailableRealmsCallback) {
> Collection<String> names = stateRef.get().getMechanismConfiguration().getMechanismRealmNames();
> if (log.isTraceEnabled()) {
> log.tracef("Handling AvailableRealmsCallback: realms = [%s]", String.join(", ", names));
> }
> if (! names.isEmpty()) {
> ((AvailableRealmsCallback) callback).setRealmNames(names.toArray(new String[names.size()]));
> }
> handleOne(callbacks, idx + 1);
> {noformat}
> If mechanism configuration is mandatory this should report an appropriate error, if not it should fallback to specifying an empty list.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (WFLY-11715) The layers testsuite should use thin servers
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-11715:
---------------------------------------
Summary: The layers testsuite should use thin servers
Key: WFLY-11715
URL: https://issues.jboss.org/browse/WFLY-11715
Project: WildFly
Issue Type: Enhancement
Components: Test Suite
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The layers testsuite is provisioning a bunch of different servers. It should use thin servers (i.e. jars in the maven repo, not in the modules dirs) as it's not validating anything that differs between a thin and fat server. This will reduce the disk io and peak FS space requirements on the CI servers.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (ELYWEB-36) ElytronHttpExchange.getRequestParameters() is prematurely readying the request.
by Farah Juma (Jira)
[ https://issues.jboss.org/browse/ELYWEB-36?page=com.atlassian.jira.plugin.... ]
Farah Juma updated ELYWEB-36:
-----------------------------
Fix Version/s: 1.2.4.Final
> ElytronHttpExchange.getRequestParameters() is prematurely readying the request.
> -------------------------------------------------------------------------------
>
> Key: ELYWEB-36
> URL: https://issues.jboss.org/browse/ELYWEB-36
> Project: Elytron Web
> Issue Type: Bug
> Components: Undertow Servlet
> Affects Versions: 1.2.3.Final, 1.3.0.Final
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 1.2.4.Final, 1.4.0.CR1
>
>
> When running within Undertow as a Servlet container the method ElytronHttpExchange.getRequestParameters() is prematurely reading the FormData making it unavailable to the HttpServletRequest.
> If instead of handling them manually the request parameters were read from the HttpServletRequest this would not be an issue as the request can re-use it's own prior FormData parsing.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (DROOLS-3652) DMN popover - Enter to apply
by Liz Clayton (Jira)
Liz Clayton created DROOLS-3652:
-----------------------------------
Summary: DMN popover - Enter to apply
Key: DROOLS-3652
URL: https://issues.jboss.org/browse/DROOLS-3652
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Reporter: Liz Clayton
Assignee: Michael Anstis
Attachments: Screen Shot 2019-02-13 at 1.20.35 PM.png
When the user changes the field value (name in this example), it would be nice if hitting ENTER would apply the name, and take the focus highlight off. The other field is being applied dynamically, so the assumption is that this one is as well.
!Screen Shot 2019-02-13 at 1.20.35 PM.png|thumbnail!
p.s. this is the pop-over that needs to be updated to support Expression instead of Name.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months