[JBoss JIRA] (DROOLS-5225) Constraint grouping fails with executable model
by Matteo Casalino (Jira)
Matteo Casalino created DROOLS-5225:
---------------------------------------
Summary: Constraint grouping fails with executable model
Key: DROOLS-5225
URL: https://issues.redhat.com/browse/DROOLS-5225
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.35.0.Final
Reporter: Matteo Casalino
Assignee: Mario Fusco
Attachments: constraints-grouping.zip
Executable model rule compilation fails when trying to build a pattern using constraint grouping.
Example of DRL that fails to compile:
{noformat}
rule "TestBusiness"
when $p : Pojo(departuretimedayofweek (== 1 || == 2 || == 7) )
then
end
{noformat}
Error:
{noformat}
java.lang.StackOverflowError
at java.base/java.util.LinkedList.unlink(LinkedList.java:215)
at java.base/java.util.LinkedList.remove(LinkedList.java:530)
at com.github.javaparser.ast.Node.setParentNode(Node.java:389)
at com.github.javaparser.ast.Node.setAsParentNodeOf(Node.java:403)
at com.github.javaparser.ast.expr.BinaryExpr.setLeft(BinaryExpr.java:174)
at com.github.javaparser.ast.expr.BinaryExpr.<init>(BinaryExpr.java:131)
at com.github.javaparser.ast.expr.BinaryExpr.<init>(BinaryExpr.java:122)
at org.drools.modelcompiler.builder.generator.DrlxParseUtil.trasformHalfBinaryToBinary(DrlxParseUtil.java:347)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:194)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:185)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:195)
at org.drools.modelcompiler.builder.generator.expressiontyper.ExpressionTyper.toTypedExpressionRec(ExpressionTyper.java:185)
...
{noformat}
The example works fine when compiling without executable model.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-13333) OpenAPI endpoint returns empty file if schema definition contains non ASCII character
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13333?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-13333:
----------------------------------
Summary: OpenAPI endpoint returns empty file if schema definition contains non ASCII character (was: Openapi endpoint returns empty file if schema definition contains non ASCII character)
> OpenAPI endpoint returns empty file if schema definition contains non ASCII character
> -------------------------------------------------------------------------------------
>
> Key: WFLY-13333
> URL: https://issues.redhat.com/browse/WFLY-13333
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenAPI
> Affects Versions: 19.0.0.Final
> Reporter: Márk Petrényi
> Assignee: Paul Ferraro
> Priority: Blocker
> Fix For: 19.0.1.Final, 20.0.0.Beta1
>
>
> Currently the {{/openapi}} endpoint returns empty file if the OpenAPI schema definition contains non ASCII characters (ie. accented letters like á,í...).
> I extended the openapi quickstart for demonstration: https://github.com/petrenyi-mark/quickstart/commit/44096980ff36ff2655859f...
> It seems like it is related to the content-length, since in {{OpenAPIHttpHandler}} the content-length header is set by {{String.length()}} (line 125). However before the response is actually returned, undertow validates that the actual content-length based on ByteBuffer size is not greater then the one declared in the response header. Since non ASCII characters are usually represented by 2 bytes undertow will fail, thus no content will be returned.
> In {{OpenAPIHttpHandler}} setting {{string.getBytes(charset).length}} as Conetnt-Length instead of {{String.length()}} would likely resolve this issue.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-5224) KieBase build fails with forall patterns containing "not equal" constraints on Dates
by Matteo Casalino (Jira)
Matteo Casalino created DROOLS-5224:
---------------------------------------
Summary: KieBase build fails with forall patterns containing "not equal" constraints on Dates
Key: DROOLS-5224
URL: https://issues.redhat.com/browse/DROOLS-5224
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.35.0.Final, 7.34.0.Final, 7.33.0.Final
Reporter: Matteo Casalino
Assignee: Mario Fusco
Attachments: forall-not-equal-constraint-on-dates.zip
This is the same issue as https://issues.redhat.com/browse/DROOLS-5100, but on Dates.
As of Drools 7.33.0.Final, forall patterns with "not equal" (!=) constraints on Dates will break when building the KieBase.
For example the following DRL:
{noformat}
rule "forall with not equal"
when forall(java.util.Date(this != "29-Dec-2019"))
then
end
{noformat}
generates the following error:
{noformat}
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1967)
at org.drools.core.rule.constraint.MvelConstraint.getLeftInExpression(MvelConstraint.java:608)
at org.drools.core.rule.constraint.MvelConstraint.hashCode(MvelConstraint.java:602)
at org.drools.core.reteoo.AlphaNode.calculateHashCode(AlphaNode.java:189)
at org.drools.core.reteoo.AlphaNode.<init>(AlphaNode.java:89)
at org.drools.core.reteoo.builder.PhreakNodeFactory.buildAlphaNode(PhreakNodeFactory.java:88)
at org.drools.core.reteoo.builder.PatternBuilder.buildAlphaNodeChain(PatternBuilder.java:360)
at org.drools.core.reteoo.builder.PatternBuilder.attachAlphaNodes(PatternBuilder.java:346)
at org.drools.core.reteoo.builder.PatternBuilder.attachPattern(PatternBuilder.java:136)
at org.drools.core.reteoo.builder.PatternBuilder.build(PatternBuilder.java:84)
at org.drools.core.reteoo.builder.GroupElementBuilder$NotBuilder.build(GroupElementBuilder.java:220)
at org.drools.core.reteoo.builder.GroupElementBuilder.build(GroupElementBuilder.java:68)
at org.drools.core.reteoo.builder.GroupElementBuilder$AndBuilder.build(GroupElementBuilder.java:108)
at org.drools.core.reteoo.builder.GroupElementBuilder.build(GroupElementBuilder.java:68)
at org.drools.core.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:167)
at org.drools.core.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:139)
at org.drools.core.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:110)
at org.drools.core.impl.KnowledgeBaseImpl.internalAddRule(KnowledgeBaseImpl.java:1525)
at org.drools.core.impl.KnowledgeBaseImpl.internalAddPackages(KnowledgeBaseImpl.java:926)
at org.drools.core.impl.KnowledgeBaseImpl.lambda$addPackages$2(KnowledgeBaseImpl.java:728)
at org.drools.core.impl.KnowledgeBaseImpl.enqueueModification(KnowledgeBaseImpl.java:745)
at org.drools.core.impl.KnowledgeBaseImpl.addPackages(KnowledgeBaseImpl.java:728)
at org.drools.compiler.kie.builder.impl.AbstractKieModule.createKieBase(AbstractKieModule.java:226)
at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:407)
at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:375)
{noformat}
This is working fine when using Drools <= 7.32.0.Final.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-3169) [DMN Designer] Last Context Entry differentiation
by Edson Tirelli (Jira)
[ https://issues.redhat.com/browse/DROOLS-3169?page=com.atlassian.jira.plug... ]
Edson Tirelli commented on DROOLS-3169:
---------------------------------------
Reversing directions a bit from my previous comment, but I actually think the way the tool is presenting this boxed expression now is fine, with the read-only, "<result>" label, in grey italics.
I am ok closing this ticket and if in the future we get a RFE from someone, then we can re-open and implement a change.
> [DMN Designer] Last Context Entry differentiation
> -------------------------------------------------
>
> Key: DROOLS-3169
> URL: https://issues.redhat.com/browse/DROOLS-3169
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Fix For: 7.36.0.Final
>
> Attachments: Screenshot 2018-10-23 18.37.56.png, Screenshot from 2018-10-22 17-35-07.png
>
>
> The last Context Entry, shown in the attachment, should be differentiated to other Context Entries. Currently we differentiate it just by the Name *Default* that user can not change.
> We should improve this in one of the following ways:
> - Keep name *Default*, change font to italics and use grey background color
> - Merge the *Default* and *Value* cells of last entry and remove the name *Default*
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-5223) User cannot open malformed scesim file. Loading popup is spining infinitive times
by Anna Dupliak (Jira)
Anna Dupliak created DROOLS-5223:
------------------------------------
Summary: User cannot open malformed scesim file. Loading popup is spining infinitive times
Key: DROOLS-5223
URL: https://issues.redhat.com/browse/DROOLS-5223
Project: Drools
Issue Type: Bug
Components: Scenario Simulation and Testing
Affects Versions: 7.35.0.Final, 7.34.0.Final, 7.33.0.Final
Reporter: Anna Dupliak
Assignee: Daniele Zonca
Attachments: Traffic.scesim
If user import Scesim file that have xml tag unclosed,
then user gets warning, but loading popup is not disappearing
and user cannot proceed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-5222) DMN BKM / FEEL closure and currying support
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-5222:
--------------------------------------
Summary: DMN BKM / FEEL closure and currying support
Key: DROOLS-5222
URL: https://issues.redhat.com/browse/DROOLS-5222
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
Respect proper definition of closure and currying function definition as specified in the DMN specification
e.g.
* have currying function in FEEL
e.g.: { f : function(a) function(b) a + b, r : f(1)(2) }
* have curried BKM boxed definition at DMN layer.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-3169) [DMN Designer] Last Context Entry differentiation
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-3169?page=com.atlassian.jira.plug... ]
Jozef Marko commented on DROOLS-3169:
-------------------------------------
[~manstis] I agree that it does not follow spec. I do not agree in keeping it opened if there is no input for year and half.
> [DMN Designer] Last Context Entry differentiation
> -------------------------------------------------
>
> Key: DROOLS-3169
> URL: https://issues.redhat.com/browse/DROOLS-3169
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Fix For: 7.36.0.Final
>
> Attachments: Screenshot 2018-10-23 18.37.56.png, Screenshot from 2018-10-22 17-35-07.png
>
>
> The last Context Entry, shown in the attachment, should be differentiated to other Context Entries. Currently we differentiate it just by the Name *Default* that user can not change.
> We should improve this in one of the following ways:
> - Keep name *Default*, change font to italics and use grey background color
> - Merge the *Default* and *Value* cells of last entry and remove the name *Default*
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-13339) Remove transitive dependencies from MP OpenAPI TCKs
by Jan Stourac (Jira)
Jan Stourac created WFLY-13339:
----------------------------------
Summary: Remove transitive dependencies from MP OpenAPI TCKs
Key: WFLY-13339
URL: https://issues.redhat.com/browse/WFLY-13339
Project: WildFly
Issue Type: Bug
Components: MP OpenAPI
Affects Versions: 19.0.0.Final
Reporter: Jan Stourac
Assignee: Paul Ferraro
In MP OpenAPI TCK integration tests module, there is defined dependency 'microprofile-openapi-tck', which broughts in another set of transition dependencies which are not required for execution of these tests in WildFly testsuite.
We should avoid transitive dependencies and explicitely define required ones in WildFly in order to avoid unwanted dependencies in our deptree and to keep version consistency.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months