January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5967) Move implementation details to PMMLRuntimeFactoryInternal

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5967?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5967: ------------------------------------- Summary: Move implementation details to PMMLRuntimeFactoryInternal (was: Extend test coverage on PMMLRuntimeFactories) > Move implementation details to PMMLRuntimeFactoryInternal > --------------------------------------------------------- > > Key: DROOLS-5967 > URL: https://issues.redhat.com/browse/DROOLS-5967 > Project: Drools > Issue Type: Feature Request > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Minor > Labels: TrustyAI > > Extend test coverage on PMMLRuntimeFactoryImpl and PMMLRuntimeFactoryInternal -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5967) Extend test coverage on PMMLRuntimeFactories

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5967: ---------------------------------------- Summary: Extend test coverage on PMMLRuntimeFactories Key: DROOLS-5967 URL: https://issues.redhat.com/browse/DROOLS-5967 Project: Drools Issue Type: Feature Request Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Extend test coverage on PMMLRuntimeFactoryImpl and PMMLRuntimeFactoryInternal -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5950) Support returning PackageDescr from assemblers

by Edoardo Vacchi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5950?page=com.atlassian.jira.plug... ] Edoardo Vacchi updated DROOLS-5950: ----------------------------------- Sprint: 2021 Week 04-06 (from Jan 25) (was: 2020 Week 52-03 (from Dec 21)) > Support returning PackageDescr from assemblers > ---------------------------------------------- > > Key: DROOLS-5950 > URL: https://issues.redhat.com/browse/DROOLS-5950 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Assemblers hook into a later stage of package building, when rules have already been built. We add an API that is invoked *before* rules are built, making it possible to return PackageDescrs that contain unprocessed rules. This is useful both for the DRLX experiment, and possibly for the PMML implementation. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5762) DRLX Research Spike

by Edoardo Vacchi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5762?page=com.atlassian.jira.plug... ] Edoardo Vacchi updated DROOLS-5762: ----------------------------------- Sprint: 2020 Week 49-51 (from Nov 30), 2021 Week 04-06 (from Jan 25) (was: 2020 Week 49-51 (from Nov 30), 2020 Week 52-03 (from Dec 21)) > DRLX Research Spike > ------------------- > > Key: DROOLS-5762 > URL: https://issues.redhat.com/browse/DROOLS-5762 > Project: Drools > Issue Type: Story > Components: core engine > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Create a revised version of the DRLX language, i.e. a revised DRL language for rules definition, with less edge cases, and a slightly different syntax. > Spec design will follow. This story is meant to deliver a small, first version of the language, just to kick off the project. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5253) Incorrect use of 'operation' instead of Resource in the remoting subsystem

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5253?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5253: ------------------------------------- Description: Some of the OperationStepHandler impls in the remoting subsystem are reading the data they provide to runtime services from the current operation instead of reading from the current configuration model. As part of cleaning this up I'll do some conversion of reads of the current address from extracting it from the 'operation' model node to the modern idiom of using OperationContext.getCurrentAddress[Value](). I'll also convert to AttributeDefinition.resolveModelAttribute in a couple places where not-incorrect but non-standard idioms are used. was: Some of the OperationStepHandler impls in the remoting subsystem are reading the data the provide to runtime services from the current operation instead of reading from the current configuration model. As part of cleaning this up I'll do some conversion of reads of the current address from extracting it from the 'operation' model node to the modern idiom of using OperationContext.getCurrentAddress[Value](). I'll also convert to AttributeDefinition.resolveModelAttribute in a couple places where not-incorrect but non-standard idioms are used. > Incorrect use of 'operation' instead of Resource in the remoting subsystem > -------------------------------------------------------------------------- > > Key: WFCORE-5253 > URL: https://issues.redhat.com/browse/WFCORE-5253 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > Some of the OperationStepHandler impls in the remoting subsystem are reading the data they provide to runtime services from the current operation instead of reading from the current configuration model. > As part of cleaning this up I'll do some conversion of reads of the current address from extracting it from the 'operation' model node to the modern idiom of using OperationContext.getCurrentAddress[Value](). > I'll also convert to AttributeDefinition.resolveModelAttribute in a couple places where not-incorrect but non-standard idioms are used. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5253) Incorrect use of 'operation' instead of Resource in the remoting subsystem

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-5253: ---------------------------------------- Summary: Incorrect use of 'operation' instead of Resource in the remoting subsystem Key: WFCORE-5253 URL: https://issues.redhat.com/browse/WFCORE-5253 Project: WildFly Core Issue Type: Bug Components: Remoting Reporter: Brian Stansberry Assignee: Brian Stansberry Some of the OperationStepHandler impls in the remoting subsystem are reading the data the provide to runtime services from the current operation instead of reading from the current configuration model. As part of cleaning this up I'll do some conversion of reads of the current address from extracting it from the 'operation' model node to the modern idiom of using OperationContext.getCurrentAddress[Value](). I'll also convert to AttributeDefinition.resolveModelAttribute in a couple places where not-incorrect but non-standard idioms are used. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14351) Use resolveModelAttribute when reading the XTSSubsystemDefinition.DEFAULT_CONTEXT_PROPAGATION value for runtime use

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-14351: --------------------------------------- Summary: Use resolveModelAttribute when reading the XTSSubsystemDefinition.DEFAULT_CONTEXT_PROPAGATION value for runtime use Key: WFLY-14351 URL: https://issues.redhat.com/browse/WFLY-14351 Project: WildFly Issue Type: Sub-task Reporter: Brian Stansberry Assignee: Brian Stansberry Small code style thing. XTSSubsystemAdd.performBoottime is not using AttributeDefinition.resolveModelAttribute when reading the model for XTSSubsystemDefinition.DEFAULT_CONTEXT_PROPAGATION. This does no harm, as the attribute neither supports expression nor has a default value (see parent issue.) But it's better if we follow the KISS principle and apply the standard idiom without exception. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14350) XTSSubsystemDefinition.DEFAULT_CONTEXT_PROPAGATION should allow expressions and have default value

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-14350: --------------------------------------- Summary: XTSSubsystemDefinition.DEFAULT_CONTEXT_PROPAGATION should allow expressions and have default value Key: WFLY-14350 URL: https://issues.redhat.com/browse/WFLY-14350 Project: WildFly Issue Type: Bug Components: XTS Reporter: Brian Stansberry Assignee: Ondrej Chaloupka The XTS subsystem is deprecated so this is optional; I'm just recording it in case a decision is made to keep it for the long term. XTSSubsystemDefinition.DEFAULT_CONTEXT_PROPAGATION is a basic boolean attribute so there is no reason it should not support expressions. If it has no value the runtime service integration uses 'false' so that means false is the default value. The AttributeDefinition should reflect this so the read-resource-description output does. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14296) Reenable ignored metrics tests

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14296?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-14296: --------------------------------------- Assignee: Jason Lee (was: Brian Stansberry) > Reenable ignored metrics tests > ------------------------------ > > Key: WFLY-14296 > URL: https://issues.redhat.com/browse/WFLY-14296 > Project: WildFly > Issue Type: Task > Components: MP Metrics > Reporter: Kabir Khan > Assignee: Jason Lee > Priority: Blocker > Fix For: 23.0.0.Beta1 > > > https://issues.redhat.com/browse/WFLY-14206 / https://github.com/wildfly/wildfly/pull/13883 ignores a test. We need to reenable this before WF23 -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14349) Enhance the datasource documentation to better cover basic DS addition

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-14349: --------------------------------------- Summary: Enhance the datasource documentation to better cover basic DS addition Key: WFLY-14349 URL: https://issues.redhat.com/browse/WFLY-14349 Project: WildFly Issue Type: Enhancement Components: JCA Reporter: Brian Stansberry Assignee: Tomasz Adamski The https://docs.wildfly.org/22/Admin_Guide.html#DataSource doc could use some improvement. The biggest thing is it should walk through a complete example of adding a datasource. Right now it notes the 'data-source' CLI command and tells you you can use --help. That's good to know but there should be an example of using 'datasource add'. Other inputs in no particular order of importance: 1) 'Any JDBC 4-compliant driver will automatically be recognized and installed into the system by name and version. A JDBC JAR is identified using the Java service provider mechanism. Such JARs will contain a text a file named META-INF/services/java.sql.Driver, which contains the name of the class(es) of the Drivers which exist in that JAR. If your JDBC driver JAR is not JDBC 4-compliant, it can be made deployable in one of a few ways.' -- The last sentence should be a separate paragraph as it's the beginning of a separate subtopic, one that is a distraction for many readers. 2) The 'For a detailed explanation how to deploy JDBC 4 compliant driver jar, please refer to the chapter "Application Deployment"' text in the driver section should be moved before the discussion of non-JDBC4 compliant jars. It's more important info for a typical non-expert user. Also, I suggest a bit more words. 'A JDBC 4 compliant driver jar can be deployed using the CLI, the HAL management console or by copying the jar to the standalone/deployments directory. For a detailed explanation how to deploy a driver jar, please refer to the chapter "Application Deployment".' 3) The 'Datasource Definitions' section includes CLI output of the installed-drivers-list operation. That should be in the previous section, and the example output should include a driver installed as a deployment, not just h2. (Which implies the previous section should include an example CLI command deploying a driver.) 4) Add an actual example of using 'data-source add' -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2021