July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5462) Provide default model name for Pmml models without it

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5462?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5462: ------------------------------------- Summary: Provide default model name for Pmml models without it (was: Provide defualt model name for Pmml models without it) > Provide default model name for Pmml models without it > ----------------------------------------------------- > > Key: DROOLS-5462 > URL: https://issues.redhat.com/browse/DROOLS-5462 > Project: Drools > Issue Type: Feature Request > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > modelName attribute is not mandatory from PMML specs. > With this ticket a "default" one will be provided soon after pmml file is "unmarshalled" to pmml java instance. > Generated name would be > _Pmml File Name_ + _model type_ + _index_ (inside models list) > e.g. > > Pmml File "TestSample.pmml" > Model type "Regression" > Position : second (index =1) > > generated modelName > _TestSampleRegression1_ > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5463) Externalize lambda for ParameterizedType with TypeVariable via From

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5463: ----------------------------------------- Summary: Externalize lambda for ParameterizedType with TypeVariable via From Key: DROOLS-5463 URL: https://issues.redhat.com/browse/DROOLS-5463 Project: Drools Issue Type: Enhancement Components: executable model Affects Versions: 7.39.0.Final Reporter: Toshiya Kobayashi Assignee: Toshiya Kobayashi When ParameterizedType with TypeVariable (e.g. java.util.Collection<V>) is given from "from" clause, lambda is not externalized. for example) AccumulateTest.testGroupBy() FromTest.testFromMapValues() -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5462) Provide defualt model name for Pmml models without it

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5462?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5462: ------------------------------------- Labels: TrustyAI (was: ) > Provide defualt model name for Pmml models without it > ----------------------------------------------------- > > Key: DROOLS-5462 > URL: https://issues.redhat.com/browse/DROOLS-5462 > Project: Drools > Issue Type: Feature Request > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > modelName attribute is not mandatory from PMML specs. > With this ticket a "default" one will be provided soon after pmml file is "unmarshalled" to pmml java instance. > Generated name would be > _Pmml File Name_ + _model type_ + _index_ (inside models list) > e.g. > > Pmml File "TestSample.pmml" > Model type "Regression" > Position : second (index =1) > > generated modelName > _TestSampleRegression1_ > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5461) Overall Transformations Workflow

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5461?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5461: ------------------------------------- Summary: Overall Transformations Workflow (was: Overall Workflow) > Overall Transformations Workflow > -------------------------------- > > Key: DROOLS-5461 > URL: https://issues.redhat.com/browse/DROOLS-5461 > Project: Drools > Issue Type: Sub-task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Overall workflow functionality. Not necessarily completely working. Should be able to compile. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5462) Provide defualt model name for Pmml models without it

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5462: ---------------------------------------- Summary: Provide defualt model name for Pmml models without it Key: DROOLS-5462 URL: https://issues.redhat.com/browse/DROOLS-5462 Project: Drools Issue Type: Feature Request Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi modelName attribute is not mandatory from PMML specs. With this ticket a "default" one will be provided soon after pmml file is "unmarshalled" to pmml java instance. Generated name would be _Pmml File Name_ + _model type_ + _index_ (inside models list) e.g. Pmml File "TestSample.pmml" Model type "Regression" Position : second (index =1) generated modelName _TestSampleRegression1_ -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5461) Overall Workflow

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5461: ---------------------------------------- Summary: Overall Workflow Key: DROOLS-5461 URL: https://issues.redhat.com/browse/DROOLS-5461 Project: Drools Issue Type: Sub-task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Overall workflow functionality. Not necessarily completely working. Should be able to compile. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5448) Prepare PMML for Transformations implementation

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5448?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5448. ------------------------------------ > Prepare PMML for Transformations implementation > ----------------------------------------------- > > Key: DROOLS-5448 > URL: https://issues.redhat.com/browse/DROOLS-5448 > Project: Drools > Issue Type: Sub-task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Add TransformationDictionary parameter to compiler methods to have it available for actual Transformation management. > Setup the main flow for actual transformations usage -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13631) MicroProfile-Health: HealthChecks from WARs within EARs cannot be found

by Jens Borrmann (Jira)

[ https://issues.redhat.com/browse/WFLY-13631?page=com.atlassian.jira.plugi... ] Jens Borrmann updated WFLY-13631: --------------------------------- Description: We want to make use of Microprofile Health in our applications. These are deployed as EARs (due to customers' demand). HealthChecks from WARs within EARs are not displayed when accessing the health endpoint ([http://localhost:9990/health]) With a simple example (such as [https://www.adam-bien.com/roller/abien/entry/simplest_possible_microprofi...]) I have the following situation * Deploying as a WAR: Everything works fine * Deploying as an EAR (containing the WAR) the following information is displayed: {"status":"UP","checks":[\{"name":"ready-deployment.myapp.ear.microprofile.war","status":"UP"}]} Remarks: * Using the new and not deprecated /health/ready does not change anything * Using OpenLiberty everything works fine was: We want to make use of Microprofile Health in our applications. These are deployed as EARs (due to customers' demand). HealthChecks from WARs within EARs are not displayed when accessing the health endpoint ([http://localhost:9990/health]) With a simple example (such as [https://www.adam-bien.com/roller/abien/entry/simplest_possible_microprofi...]) I have the following situation * Deploying as a WAR: Everything works fine * Deploying as an EAR (containing the WAR) the following information is displayed: {{{{{"status":"UP","checks":[ \{"name":"ready-deployment.myapp.ear.microprofile.war","status":"UP"}}} {{]}}} }} Remarks: * Using the new and not deprecated /health/ready does not change anything * Using OpenLiberty everything works fine > MicroProfile-Health: HealthChecks from WARs within EARs cannot be found > ----------------------------------------------------------------------- > > Key: WFLY-13631 > URL: https://issues.redhat.com/browse/WFLY-13631 > Project: WildFly > Issue Type: Bug > Affects Versions: 20.0.0.Final > Reporter: Jens Borrmann > Assignee: Brian Stansberry > Priority: Major > > We want to make use of Microprofile Health in our applications. These are deployed as EARs (due to customers' demand). HealthChecks from WARs within EARs are not displayed when accessing the health endpoint ([http://localhost:9990/health]) > With a simple example (such as [https://www.adam-bien.com/roller/abien/entry/simplest_possible_microprofi...]) I have the following situation > * Deploying as a WAR: Everything works fine > * Deploying as an EAR (containing the WAR) the following information is displayed: > {"status":"UP","checks":[\{"name":"ready-deployment.myapp.ear.microprofile.war","status":"UP"}]} > Remarks: > * Using the new and not deprecated /health/ready does not change anything > * Using OpenLiberty everything works fine -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13631) MicroProfile-Health: HealthChecks from WARs within EARs cannot be found

by Jens Borrmann (Jira)

[ https://issues.redhat.com/browse/WFLY-13631?page=com.atlassian.jira.plugi... ] Jens Borrmann updated WFLY-13631: --------------------------------- Description: We want to make use of Microprofile Health in our applications. These are deployed as EARs (due to customers' demand). HealthChecks from WARs within EARs are not displayed when accessing the health endpoint ([http://localhost:9990/health]) With a simple example (such as [https://www.adam-bien.com/roller/abien/entry/simplest_possible_microprofi...]) I have the following situation * Deploying as a WAR: Everything works fine * Deploying as an EAR (containing the WAR) the following information is displayed: {{{{{"status":"UP","checks":[ \{"name":"ready-deployment.myapp.ear.microprofile.war","status":"UP"}}} {{]}}} }} Remarks: * Using the new and not deprecated /health/ready does not change anything * Using OpenLiberty everything works fine was: We want to make use of Microprofile Health in our applications. These are deployed as EARs (due to customers' demand). HealthChecks from WARs within EARs are not displayed when accessing the health endpoint ([http://localhost:9990/health]) With a simple example (such as [https://www.adam-bien.com/roller/abien/entry/simplest_possible_microprofi...]) I have the following situation * Deploying as a WAR: Everything works fine * Deploying as an EAR (containing the WAR) the following information is displayed: {{{"status":"UP","checks":[ \{"name":"ready-deployment.myapp.ear.microprofile.war","status":"UP"}}} {{]}}} Remarks: * Using the new and not deprecated /health/ready does not change anything * Using OpenLiberty everything works fine > MicroProfile-Health: HealthChecks from WARs within EARs cannot be found > ----------------------------------------------------------------------- > > Key: WFLY-13631 > URL: https://issues.redhat.com/browse/WFLY-13631 > Project: WildFly > Issue Type: Bug > Affects Versions: 20.0.0.Final > Reporter: Jens Borrmann > Assignee: Brian Stansberry > Priority: Major > > We want to make use of Microprofile Health in our applications. These are deployed as EARs (due to customers' demand). HealthChecks from WARs within EARs are not displayed when accessing the health endpoint ([http://localhost:9990/health]) > With a simple example (such as [https://www.adam-bien.com/roller/abien/entry/simplest_possible_microprofi...]) I have the following situation > * Deploying as a WAR: Everything works fine > * Deploying as an EAR (containing the WAR) the following information is displayed: > {{{{{"status":"UP","checks":[ \{"name":"ready-deployment.myapp.ear.microprofile.war","status":"UP"}}} > {{]}}} > }} > Remarks: > * Using the new and not deprecated /health/ready does not change anything > * Using OpenLiberty everything works fine -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13631) MicroProfile-Health: HealthChecks from WARs within EARs cannot be found

by Jens Borrmann (Jira)

[ https://issues.redhat.com/browse/WFLY-13631?page=com.atlassian.jira.plugi... ] Jens Borrmann updated WFLY-13631: --------------------------------- Description: We want to make use of Microprofile Health in our applications. These are deployed as EARs (due to customers' demand). HealthChecks from WARs within EARs are not displayed when accessing the health endpoint ([http://localhost:9990/health]) With a simple example (such as [https://www.adam-bien.com/roller/abien/entry/simplest_possible_microprofi...]) I have the following situation * Deploying as a WAR: Everything works fine * Deploying as an EAR (containing the WAR) the following information is displayed: {{{"status":"UP","checks":[ \{"name":"ready-deployment.myapp.ear.microprofile.war","status":"UP"}}} {{]}}} Remarks: * Using the new and not deprecated /health/ready does not change anything * Using OpenLiberty everything works fine was: We want to make use of Microprofile Health in our applications. These are deployed as EARs (due to customers' demand). HealthChecks from WARs within EARs are not displayed when accessing the health endpoint (http://localhost:9990/health) With a simple example (such as https://www.adam-bien.com/roller/abien/entry/simplest_possible_microprofi...) I have the following situation * Deploying as a WAR: Everything works fine * Deploying as an EAR (containing the WAR) the following information is displayed: \{"status":"UP","checks":[{"name":"ready-deployment.myapp.ear.microprofile.war","status":"UP"}]} Remarks: * Using the new and not deprecated /health/ready does not change anything * Using OpenLiberty everything works fine > MicroProfile-Health: HealthChecks from WARs within EARs cannot be found > ----------------------------------------------------------------------- > > Key: WFLY-13631 > URL: https://issues.redhat.com/browse/WFLY-13631 > Project: WildFly > Issue Type: Bug > Affects Versions: 20.0.0.Final > Reporter: Jens Borrmann > Assignee: Brian Stansberry > Priority: Major > > We want to make use of Microprofile Health in our applications. These are deployed as EARs (due to customers' demand). HealthChecks from WARs within EARs are not displayed when accessing the health endpoint ([http://localhost:9990/health]) > With a simple example (such as [https://www.adam-bien.com/roller/abien/entry/simplest_possible_microprofi...]) I have the following situation > * Deploying as a WAR: Everything works fine > * Deploying as an EAR (containing the WAR) the following information is displayed: {{{"status":"UP","checks":[ \{"name":"ready-deployment.myapp.ear.microprofile.war","status":"UP"}}} > {{]}}} > Remarks: > * Using the new and not deprecated /health/ready does not change anything > * Using OpenLiberty everything works fine -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 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 July 2020