[JBoss JIRA] (DROOLS-4467) PMML with capitalized field names does not work
by Lance Leverich (Jira)
Lance Leverich created DROOLS-4467:
--------------------------------------
Summary: PMML with capitalized field names does not work
Key: DROOLS-4467
URL: https://issues.jboss.org/browse/DROOLS-4467
Project: Drools
Issue Type: Bug
Reporter: Lance Leverich
Assignee: Mario Fusco
Attachments: single_audit_dectree.xml
PMML files that contain field names with the first letter capitalized do not generate the proper POJOs, and consequently do not work.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-3953) DMN UX - overlay validation error reporting
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-3953:
-------------------------------------------
[~karreiro] [~tirelli] [~mmenestr] I updated the click-thru with the changes we discussed:
* Added a Clear button (it's a toggle state of the Validate button.)
* Provided a summary tally for the error message with a link to Alert details.
The Marvel mockup posted above reflects these changes. [~bdellasc] FYI ^^
I'll demo it next meeting, to see if I can mark this issue Resolved.
> DMN UX - overlay validation error reporting
> -------------------------------------------
>
> Key: DROOLS-3953
> URL: https://issues.jboss.org/browse/DROOLS-3953
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
> Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, ut.png, ux-decision button.png, ux-decision table.png
>
>
> As user during DMN model editing, I want to see validation errors on the model in case of wrong FEEL expression or invalid decision table.
> I want to see this kind of errors in the decisions and at diagram level.
> * As a user I want to run a validation test within the DMN editor, using the Validate toolbar action, to be able to identify elements within the graph or grids that have errors, so that I can resolve the issues.
> * As a user when I save a file (and it is validated) I want to be informed if there are any validation errors, so that I'm aware that there are issues that need to be resolved.
> * As a user when I test a rule in the Scenario tool and any scenarios fail due to a syntax errors within DMN, I need to be able to easily identify the portions of the DMN file with errors so that I can fix them.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-4611) Complete AttributeDefinition.getImmutableFlags() -> getFlags() transition
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFCORE-4611?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFCORE-4611:
---------------------------------
Description:
During the 3.0.0 development cycle, the AttributeDefinition.getFlags() methods was deprecated with the intention of letting consumers know to generalize the return type from an EnumSet<AttributeAccess.Flag> to a Set<AttributeAccess.Flag>.
This jira is a note to complete this transition.
was:
During the 3.0.0 development cycle, the AttributeDefinition.getFlags() methods was deprecated with the intention of letting consumers know to generalize the return type from an EnumSet<AttributeAccess.Flag> to a Set<AttributeAccess.Flag>.
I think enough time has passed to complete this transition.
> Complete AttributeDefinition.getImmutableFlags() -> getFlags() transition
> -------------------------------------------------------------------------
>
> Key: WFCORE-4611
> URL: https://issues.jboss.org/browse/WFCORE-4611
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 9.0.2.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Optional
>
> During the 3.0.0 development cycle, the AttributeDefinition.getFlags() methods was deprecated with the intention of letting consumers know to generalize the return type from an EnumSet<AttributeAccess.Flag> to a Set<AttributeAccess.Flag>.
> This jira is a note to complete this transition.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12397) Undertow should not create WebResourcePermission with an action of "!"
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12397?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-12397:
-----------------------------------------
[~dlofthouse] In the last paragraph in the description there is some strange quoted text. I think you meant two occurrences of "!" but some other text got swapped in.
No big deal. I was doing PR review and wanted to understand what I was looking at and that paragraph got me scratching my head a bit. :)
> Undertow should not create WebResourcePermission with an action of "!"
> ----------------------------------------------------------------------
>
> Key: WFLY-12397
> URL: https://issues.jboss.org/browse/WFLY-12397
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 18.0.0.Beta1
>
>
> As Undertow processes a deployment to convert the security constraints to a JACC Policy using JACC Permissions there is a step which adds unchecked permissions based on the HTTP methods seen so far: -
> {noformat}
> if(jbossWebMetaData.getDenyUncoveredHttpMethods() == null) {
> if (seenMethods.size() != NUMBER_OF_HTTP_METHODS) {
> WebResourcePermission wrpUnchecked = new WebResourcePermission(qurl, "!"
> + getCommaSeparatedString(seenMethods.toArray(new String[seenMethods.size()])));
> pc.addToUncheckedPolicy(wrpUnchecked);
> }
> }
> {noformat}
> If no methods have been seen so far this can lead to an action of "!".
> Where an action is null or empty String the meaning is "all methods".
> Where a list of methods of prefixed with "!" the meaning is "all methods except those listed".
> Where we use "!" we mean all methods as we have not already encountered any, however the API does specify the syntax and a single "!" without any actions is invalid so for that scenario we should use null or empty String.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-4622) ReadOnlyModeTestCase.testConfigurationNotUpdated is racy during host reload
by Brian Stansberry (Jira)
Brian Stansberry created WFCORE-4622:
----------------------------------------
Summary: ReadOnlyModeTestCase.testConfigurationNotUpdated is racy during host reload
Key: WFCORE-4622
URL: https://issues.jboss.org/browse/WFCORE-4622
Project: WildFly Core
Issue Type: Bug
Components: Management, Test Suite
Reporter: Brian Stansberry
Assignee: Jeff Mesnil
ReadOnlyModeTestCase.testConfigurationNotUpdated has intermittent failures.
{code}
java.lang.IllegalArgumentException
at org.jboss.dmr.ModelValue.asBoolean(ModelValue.java:69)
at org.jboss.dmr.ModelNode.asBoolean(ModelNode.java:324)
at org.jboss.as.test.integration.domain.ReadOnlyModeTestCase.testConfigurationNotUpdated(ReadOnlyModeTestCase.java:96)
{code}
Problem is the last line here:
{code}
// reload master HC
op = new ModelNode();
op.get(OP_ADDR).add(HOST, "master");
op.get(OP).set("reload");
domainMasterLifecycleUtil.executeAwaitConnectionClosed(op);
// Try to reconnect to the hc
domainMasterLifecycleUtil.connect();
domainMasterLifecycleUtil.awaitHostController(System.currentTimeMillis());
Assert.assertTrue(Operations.readResult(masterClient.execute(Operations.createReadAttributeOperation(domainAddress, "value"))).asBoolean());
Assert.assertTrue(Operations.readResult(masterClient.execute(Operations.createReadAttributeOperation(masterAddress, "value"))).asBoolean());
Assert.assertTrue(Operations.readResult(masterClient.execute(Operations.createReadAttributeOperation(slaveAddress, "value"))).asBoolean());
{code}
The test reloads the master, waits for the master to reload, and then tries to read the slave via the master. But just because the master has reloaded doesn't mean the slave has reconnected. The slave should loop or something until the slave is connected.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months