[JBoss JIRA] (DROOLS-3280) DMNRuntime API for evaluateByID/Name to error if empty array
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-3280?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-3280:
-----------------------------------
Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9))
> DMNRuntime API for evaluateByID/Name to error if empty array
> ------------------------------------------------------------
>
> Key: DROOLS-3280
> URL: https://issues.redhat.com/browse/DROOLS-3280
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Affects Versions: 7.30.0.Final
> Reporter: Matteo Mortari
> Assignee: Toshiya Kobayashi
> Priority: Optional
> Labels: good-first-issue
>
> there is already some null-check for the public API parameters. However if passing an empty array (e.g. in the varargs) is still semantically wrong when calling these public API method (e.g. evaluate by ID, without passing any IDs). Augment to extend proper checks to support end-user using public API
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (DROOLS-4561) DMN introspect PMML for output types
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4561?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4561:
-----------------------------------
Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9))
> DMN introspect PMML for output types
> ------------------------------------
>
> Key: DROOLS-4561
> URL: https://issues.redhat.com/browse/DROOLS-4561
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Toshiya Kobayashi
> Priority: Critical
> Labels: good-first-issue
>
> Currently PMML is introspected for input parameters names and types.
> Also for output parameters names.
> Currently the feature is missing PMML introspection for output parameters types.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (DROOLS-4870) Materialize consequences using Drools
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4870?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4870:
-----------------------------------
Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9))
> Materialize consequences using Drools
> -------------------------------------
>
> Key: DROOLS-4870
> URL: https://issues.redhat.com/browse/DROOLS-4870
> Project: Drools
> Issue Type: Bug
> Reporter: Luca Molteni
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> Currently consequences using Drools are not materialized (extracted in a different lambda) because they are capturing, as they use the relative bitmask instance.
> We should find a way to pass the bitmask instance to the consequence so that we can materialize them.
> This means we should probably not change only the compiler, but also the interpreter of the DSL
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFLY-12913:
---------------------------------------
Assignee: (was: Scott Marlow)
> Rationalize com.sum.xml.bind module dependencies
> ------------------------------------------------
>
> Key: WFLY-12913
> URL: https://issues.redhat.com/browse/WFLY-12913
> Project: WildFly
> Issue Type: Task
> Components: JPA / Hibernate, REST, Web Services
> Reporter: Brian Stansberry
> Priority: Major
>
> The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents:
> {code}
> <module name="com.github.relaxng" export="true" />
> <module name="com.sun.istack" export="true" />
> <module name="com.sun.xml.txw2" export="true" />
> <module name="com.sun.xsom" export="true" />
> {code}
> Task is to:
> 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules.
> 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules.
> 3) Assuming no positive responses, make the artifacts from the above four modules direct artifacts of the com.sun.xml.bind module, add any needed module dependencies to con.sum.xml.bind, and get rid of those four modules.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-12913:
------------------------------------
Priority: Minor (was: Major)
> Rationalize com.sum.xml.bind module dependencies
> ------------------------------------------------
>
> Key: WFLY-12913
> URL: https://issues.redhat.com/browse/WFLY-12913
> Project: WildFly
> Issue Type: Task
> Components: JPA / Hibernate, REST, Web Services
> Reporter: Brian Stansberry
> Priority: Minor
>
> The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents:
> {code}
> <module name="com.github.relaxng" export="true" />
> <module name="com.sun.istack" export="true" />
> <module name="com.sun.xml.txw2" export="true" />
> <module name="com.sun.xsom" export="true" />
> {code}
> Task is to:
> 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules.
> 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules.
> 3) Assuming no positive responses, make the artifacts from the above four modules direct artifacts of the com.sun.xml.bind module, add any needed module dependencies to con.sum.xml.bind, and get rid of those four modules.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-12913:
------------------------------------
Description:
The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents:
{code}
<module name="com.github.relaxng" export="true" />
<module name="com.sun.istack" export="true" />
<module name="com.sun.xml.txw2" export="true" />
<module name="com.sun.xsom" export="true" />
{code}
Task is to:
1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules.
2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules.
3) Assuming no positive responses, make the artifacts from the above four direct artifacts of the com.sun.xml.bind module,
> Rationalize com.sum.xml.bind module dependencies
> ------------------------------------------------
>
> Key: WFLY-12913
> URL: https://issues.redhat.com/browse/WFLY-12913
> Project: WildFly
> Issue Type: Task
> Components: JPA / Hibernate, REST, Web Services
> Reporter: Brian Stansberry
> Assignee: Scott Marlow
> Priority: Major
>
> The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents:
> {code}
> <module name="com.github.relaxng" export="true" />
> <module name="com.sun.istack" export="true" />
> <module name="com.sun.xml.txw2" export="true" />
> <module name="com.sun.xsom" export="true" />
> {code}
> Task is to:
> 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules.
> 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules.
> 3) Assuming no positive responses, make the artifacts from the above four direct artifacts of the com.sun.xml.bind module,
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months