June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HIBERNATE-165) SequenceInformationExtractor does not take into account the schema indicated in ExtractionContext on PostreSQL

by Thomas Mortagne (Jira)

[ https://issues.jboss.org/browse/HIBERNATE-165?page=com.atlassian.jira.plu... ] Thomas Mortagne updated HIBERNATE-165: -------------------------------------- Environment: Hibernate 5.4.3.Final, PostgreSQL10Dialect, PostgreSQL 11.4 on Ubuntu 19.0.4.1 (but also reproduced on various PostgreSQL versions) (was: PostgreSQL10Dialect, PostgreSQL 11.4 on Ubuntu 19.0.4.1 (but also reproduced on various PostgreSQL versions)) > SequenceInformationExtractor does not take into account the schema indicated in ExtractionContext on PostreSQL > -------------------------------------------------------------------------------------------------------------- > > Key: HIBERNATE-165 > URL: https://issues.jboss.org/browse/HIBERNATE-165 > Project: Hibernate Integration > Issue Type: Bug > Environment: Hibernate 5.4.3.Final, PostgreSQL10Dialect, PostgreSQL 11.4 on Ubuntu 19.0.4.1 (but also reproduced on various PostgreSQL versions) > Reporter: Thomas Mortagne > Assignee: Steve Ebersole > Priority: Major > > When asking for the sequences located on schema "toto" when end up with those stored in the schema "public". > Among other things the consequence is that the SchemaMigrator (my actual use case) create the sequences only on one schema (because when creating others the sequence "already exist"). It's also because the schema migrator totally ignore the schema name from the SequenceInformation but it does not make much sense to me that it end up with sequences from other schemas when asking for them in the first place anyway. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HIBERNATE-165) SequenceInformationExtractor does not take into account the schema indicated in ExtractionContext on PostreSQL

by Thomas Mortagne (Jira)

[ https://issues.jboss.org/browse/HIBERNATE-165?page=com.atlassian.jira.plu... ] Thomas Mortagne updated HIBERNATE-165: -------------------------------------- Environment: Hibernate 5.4.3.Final, PostgreSQL10Dialect, PostgreSQL 11.4 on Ubuntu 19.0.4.1 (but also reproduced on various PostgreSQL versions and other systems) (was: Hibernate 5.4.3.Final, PostgreSQL10Dialect, PostgreSQL 11.4 on Ubuntu 19.0.4.1 (but also reproduced on various PostgreSQL versions)) > SequenceInformationExtractor does not take into account the schema indicated in ExtractionContext on PostreSQL > -------------------------------------------------------------------------------------------------------------- > > Key: HIBERNATE-165 > URL: https://issues.jboss.org/browse/HIBERNATE-165 > Project: Hibernate Integration > Issue Type: Bug > Environment: Hibernate 5.4.3.Final, PostgreSQL10Dialect, PostgreSQL 11.4 on Ubuntu 19.0.4.1 (but also reproduced on various PostgreSQL versions and other systems) > Reporter: Thomas Mortagne > Assignee: Steve Ebersole > Priority: Major > > When asking for the sequences located on schema "toto" when end up with those stored in the schema "public". > Among other things the consequence is that the SchemaMigrator (my actual use case) create the sequences only on one schema (because when creating others the sequence "already exist"). It's also because the schema migrator totally ignore the schema name from the SequenceInformation but it does not make much sense to me that it end up with sequences from other schemas when asking for them in the first place anyway. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HIBERNATE-165) SequenceInformationExtractor does not take into account the schema indicated in ExtractionContext on PostreSQL

by Thomas Mortagne (Jira)

[ https://issues.jboss.org/browse/HIBERNATE-165?page=com.atlassian.jira.plu... ] Thomas Mortagne updated HIBERNATE-165: -------------------------------------- Summary: SequenceInformationExtractor does not take into account the schema indicated in ExtractionContext on PostreSQL (was: SequenceInformationExtractor does not take into account the schema indicate in ExtractionContext on PostreSQL) > SequenceInformationExtractor does not take into account the schema indicated in ExtractionContext on PostreSQL > -------------------------------------------------------------------------------------------------------------- > > Key: HIBERNATE-165 > URL: https://issues.jboss.org/browse/HIBERNATE-165 > Project: Hibernate Integration > Issue Type: Bug > Environment: PostgreSQL10Dialect, PostgreSQL 11.4 on Ubuntu 19.0.4.1 (but also reproduced on various PostgreSQL versions) > Reporter: Thomas Mortagne > Assignee: Steve Ebersole > Priority: Major > > When asking for the sequences located on schema "toto" when end up with those stored in the schema "public". > Among other things the consequence is that the SchemaMigrator (my actual use case) create the sequences only on one schema (because when creating others the sequence "already exist"). It's also because the schema migrator totally ignore the schema name from the SequenceInformation but it does not make much sense to me that it end up with sequences from other schemas when asking for them in the first place anyway. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HIBERNATE-165) SequenceInformationExtractor does not take into account the schema indicate in ExtractionContext on PostreSQL

by Thomas Mortagne (Jira)

Thomas Mortagne created HIBERNATE-165: ----------------------------------------- Summary: SequenceInformationExtractor does not take into account the schema indicate in ExtractionContext on PostreSQL Key: HIBERNATE-165 URL: https://issues.jboss.org/browse/HIBERNATE-165 Project: Hibernate Integration Issue Type: Bug Environment: PostgreSQL10Dialect, PostgreSQL 11.4 on Ubuntu 19.0.4.1 (but also reproduced on various PostgreSQL versions) Reporter: Thomas Mortagne Assignee: Steve Ebersole When asking for the sequences located on schema "toto" when end up with those stored in the schema "public". Among other things the consequence is that the SchemaMigrator (my actual use case) create the sequences only on one schema (because when creating others the sequence "already exist"). It's also because the schema migrator totally ignore the schema name from the SequenceInformation but it does not make much sense to me that it end up with sequences from other schemas when asking for them in the first place anyway. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Tao Zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Tao Zhu updated DROOLS-4161: ---------------------------- Attachment: screenshot-3.png > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, 屏幕快照 2019-06-26 下午3.18.13.png, 屏幕快照 2019-06-26 下午3.37.46.png > > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Tao Zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Tao Zhu updated DROOLS-4161: ---------------------------- Attachment: 屏幕快照 2019-06-26 下午3.37.46.png > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: screenshot-1.png, screenshot-2.png, 屏幕快照 2019-06-26 下午3.18.13.png, 屏幕快照 2019-06-26 下午3.37.46.png > > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Tao Zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Tao Zhu updated DROOLS-4161: ---------------------------- Attachment: screenshot-2.png > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: screenshot-1.png, screenshot-2.png, 屏幕快照 2019-06-26 下午3.18.13.png > > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Tao Zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Tao Zhu updated DROOLS-4161: ---------------------------- Attachment: screenshot-1.png > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: screenshot-1.png, 屏幕快照 2019-06-26 下午3.18.13.png > > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Tao Zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Tao Zhu updated DROOLS-4161: ---------------------------- Attachment: 屏幕快照 2019-06-26 下午3.18.13.png > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: 屏幕快照 2019-06-26 下午3.18.13.png > > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4259) Scenario can not access parent data object fields

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4259?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4259: -------------------------------- Tester: Jozef Marko > Scenario can not access parent data object fields > ------------------------------------------------- > > Key: DROOLS-4259 > URL: https://issues.jboss.org/browse/DROOLS-4259 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Daniele Zonca > Priority: Critical > Labels: ScenarioSimulation > Attachments: Screenshot from 2019-06-26 08-56-23.png, inheritance.zip > > > Scenario Designer can not access parent data object fields, even if the field has public getter and setter. If you check the attached project there are two fields - *price* and *size* while *size* is declared in parent class. If you try to run the scenario, error about not possible initialization of the data object appears. > If you move the *size* field from *Picture* into *Advertisement* class and rerun the scenario, everything works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2019