August 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5562) Confirm strongly typed inheritance use case

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5562?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5562: -------------------------------------- Description: Generated class may have a super type which is a baseType of the DMN type. Firstly, I think I should fix the order of this logic (call ucFirst() at last). https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/m... However, I'm not able to write a meaningful test case because DMN type may have baseType but it results in the same structure (other than collection). See tEmployee in inheritType.dmn If we want to allow Employee class to extends Person class, we will need some more fixes in class generation (currently, Employee has its own fields like name, age. Make super class fields protected? or access super class's fields with getter?) was: Generated class may have a super type which is a baseType of the DMN type. Firstly, I think I should fix the order of this logic (call ucFirst() at last). https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/m... However, I'm not able to write a meaningful test case because DMN type may have baseType but it results in the same structure. See tEmployee in inheritType.dmn If we want to allow Employee class to extends Person class, we will need some more fixes in class generation (currently, Employee has its own fields like name, age. Make super class fields protected? or access super class's fields with getter?) > Confirm strongly typed inheritance use case > ------------------------------------------- > > Key: DROOLS-5562 > URL: https://issues.redhat.com/browse/DROOLS-5562 > Project: Drools > Issue Type: Task > Components: dmn engine > Affects Versions: 7.41.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Minor > Attachments: inheritType.dmn > > > Generated class may have a super type which is a baseType of the DMN type. Firstly, I think I should fix the order of this logic (call ucFirst() at last). > https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/m... > However, I'm not able to write a meaningful test case because DMN type may have baseType but it results in the same structure (other than collection). See tEmployee in inheritType.dmn > If we want to allow Employee class to extends Person class, we will need some more fixes in class generation (currently, Employee has its own fields like name, age. Make super class fields protected? or access super class's fields with getter?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5562) Confirm strongly typed inheritance use case

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5562?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5562: -------------------------------------- Attachment: inheritType.dmn > Confirm strongly typed inheritance use case > ------------------------------------------- > > Key: DROOLS-5562 > URL: https://issues.redhat.com/browse/DROOLS-5562 > Project: Drools > Issue Type: Task > Components: dmn engine > Affects Versions: 7.41.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Minor > Attachments: inheritType.dmn > > > Generated class may have a super type which is a baseType of the DMN type. Firstly, I think I should fix the order of this logic (call ucFirst() at last). > https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/m... > However, I'm not able to write a meaningful test case because DMN type may have baseType but it results in the same structure. See tEmployee in inheritType.dmn > If we want to allow Employee class to extends Person class, we will need some more fixes in class generation (currently, Employee has its own fields like name, age. Make super class fields protected? or access super class's fields with getter?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5562) Confirm strongly typed inheritance use case

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5562?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5562: -------------------------------------- Description: Generated class may have a super type which is a baseType of the DMN type. Firstly, I think I should fix the order of this logic (call ucFirst() at last). https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/m... However, I'm not able to write a meaningful test case because DMN type may have baseType but it results in the same structure. See tEmployee in inheritType.dmn If we want to allow Employee class to extends Person class, we will need some more fixes in class generation (currently, Employee has its own fields like name, age. Make super class fields protected? or access super class's fields with getter?) was: Generated class may have a super type which is a baseType of the DMN type. Firstly, I think I should fix the order of this logic (call ucFirst() at last). https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/m... However, I'm not able to write a meaningful test case because DMN type may have baseType but it results in the same structure. See tEmployee in inheritType.dmn If we want to allow Employee class to extends Person class, we will need some more fixes in class generation (currently, Employee has its own fields name, age. Make super class fields protected? or access super class's fields with getter?) > Confirm strongly typed inheritance use case > ------------------------------------------- > > Key: DROOLS-5562 > URL: https://issues.redhat.com/browse/DROOLS-5562 > Project: Drools > Issue Type: Task > Components: dmn engine > Affects Versions: 7.41.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Minor > > Generated class may have a super type which is a baseType of the DMN type. Firstly, I think I should fix the order of this logic (call ucFirst() at last). > https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/m... > However, I'm not able to write a meaningful test case because DMN type may have baseType but it results in the same structure. See tEmployee in inheritType.dmn > If we want to allow Employee class to extends Person class, we will need some more fixes in class generation (currently, Employee has its own fields like name, age. Make super class fields protected? or access super class's fields with getter?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5562) Confirm strongly typed inheritance use case

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5562?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5562: -------------------------------------- Priority: Minor (was: Major) > Confirm strongly typed inheritance use case > ------------------------------------------- > > Key: DROOLS-5562 > URL: https://issues.redhat.com/browse/DROOLS-5562 > Project: Drools > Issue Type: Task > Components: dmn engine > Affects Versions: 7.41.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Minor > > Generated class may have a super type which is a baseType of the DMN type. Firstly, I think I should fix the order of this logic (call ucFirst() at last). > https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/m... > However, I'm not able to write a meaningful test case because DMN type may have baseType but it results in the same structure. See tEmployee in inheritType.dmn > If we want to allow Employee class to extends Person class, we will need some more fixes in class generation (currently, Employee has its own fields name, age. Make super class fields protected? or access super class's fields with getter?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5562) Confirm strongly typed inheritance use case

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5562: ----------------------------------------- Summary: Confirm strongly typed inheritance use case Key: DROOLS-5562 URL: https://issues.redhat.com/browse/DROOLS-5562 Project: Drools Issue Type: Task Components: dmn engine Affects Versions: 7.41.0.Final Reporter: Toshiya Kobayashi Assignee: Toshiya Kobayashi Generated class may have a super type which is a baseType of the DMN type. Firstly, I think I should fix the order of this logic (call ucFirst() at last). https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core/src/m... However, I'm not able to write a meaningful test case because DMN type may have baseType but it results in the same structure. See tEmployee in inheritType.dmn If we want to allow Employee class to extends Person class, we will need some more fixes in class generation (currently, Employee has its own fields name, age. Make super class fields protected? or access super class's fields with getter?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13745) Upgrade version.org.hibernate from 5.3.17 to 5.3.18

by Amit Nijhawan (Jira)

[ https://issues.redhat.com/browse/WFLY-13745?page=com.atlassian.jira.plugi... ] Amit Nijhawan deleted WFLY-13745: --------------------------------- > Upgrade version.org.hibernate from 5.3.17 to 5.3.18 > --------------------------------------------------- > > Key: WFLY-13745 > URL: https://issues.redhat.com/browse/WFLY-13745 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Amit Nijhawan > Assignee: Brian Stansberry > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13745) Upgrade version.org.hibernate from 5.3.17 to 5.3.18

by Amit Nijhawan (Jira)

Amit Nijhawan created WFLY-13745: ------------------------------------ Summary: Upgrade version.org.hibernate from 5.3.17 to 5.3.18 Key: WFLY-13745 URL: https://issues.redhat.com/browse/WFLY-13745 Project: WildFly Issue Type: Component Upgrade Reporter: Amit Nijhawan Assignee: Brian Stansberry -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5561) Add DMN strongly typed tests for collection of collection

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5561: ----------------------------------------- Summary: Add DMN strongly typed tests for collection of collection Key: DROOLS-5561 URL: https://issues.redhat.com/browse/DROOLS-5561 Project: Drools Issue Type: Task Components: dmn engine Affects Versions: 7.41.0.Final Reporter: Toshiya Kobayashi Assignee: Toshiya Kobayashi Add tests for collection of collection (of collection)* in DMNRuntimeTypesTest https://github.com/kiegroup/drools/pull/3030#discussion_r465987525 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5084) Why does the elytron layer bring in access control?

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5084?page=com.atlassian.jira.plug... ] Brian Stansberry commented on WFCORE-5084: ------------------------------------------ [~dlofthouse] What did you add it to? There are other ways to get the access-control feature-group besides the elytron layer, so why it wasn't already there depends on what you were adding elytron to. That said it's not clear to me why the elytron layer adds it itself since as you say it's an aspect of authenticated management in general. The 'management' feature-group, which is used by layers that provide management, itself brings in access-control. > Why does the elytron layer bring in access control? > --------------------------------------------------- > > Key: WFCORE-5084 > URL: https://issues.redhat.com/browse/WFCORE-5084 > Project: WildFly Core > Issue Type: Task > Components: Build System, Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 13.0.0.Beta4 > > > The following shows the set of changes created by adding the elytron layer to a provisioned server: > https://gist.github.com/darranl/68f4a3d60560dae9a9225ec1a0e35a9f/revisions > This includes the following: > {code:xml} > <management> > <access-control provider="simple"> > <role-mapping> > <role name="SuperUser"> > <include> > <user name="$local"/> > </include> > </role> > </role-mapping> > </access-control> > </management> > {code} > Shouldn't this section be added if any form of authenticated management is added instead? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5085) The CommandBuilder Environment should not check the JAVA_HOME environment variable

by James Perkins (Jira)

James Perkins created WFCORE-5085: ------------------------------------- Summary: The CommandBuilder Environment should not check the JAVA_HOME environment variable Key: WFCORE-5085 URL: https://issues.redhat.com/browse/WFCORE-5085 Project: WildFly Core Issue Type: Bug Components: Launcher Reporter: James Perkins Assignee: James Perkins The {{CommandBuilder}} API checks the {{JAVA_HOME}} environment variable then the {{java.home}} system property to determine the currently running JVM. The {{JAVA_HOME}} environment variables should be ignored as that may point to a JVM that is going to be used by the new process. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2020