March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11832) Transaction for Hibernate Interceptor is null

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11832?page=com.atlassian.jira.plugin... ] Scott Marlow closed WFLY-11832. ------------------------------- Resolution: Duplicate Issue Thanks [~mchur] + [~gbadner]! Closing now as duplicate of [https://hibernate.atlassian.net/browse/HHH-13326] > Transaction for Hibernate Interceptor is null > --------------------------------------------- > > Key: WFLY-11832 > URL: https://issues.jboss.org/browse/WFLY-11832 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate, Transactions > Affects Versions: 14.0.0.Final, 15.0.1.Final, 16.0.0.Final > Reporter: Markus Chur > Assignee: Scott Marlow > Priority: Major > Attachments: hibernate-interceptor-reproducer-0.0.1-SNAPSHOT.jar, src -WFLY-11832.zip > > > With Wildfly 13 - javaee7 transactions in hibernate interceptors were never null. > Since Wildfly 14 - javaee8 transactions in hibernate interceptors are always null. > Attached sources and a jar of a minimal reproducer for Wildfly 16. This is reproducible by using a fresh unchanged Wildfly 16 and unchanged standalone.xml. Extract Wildfly 16, drop in the jar in the deployments folder and start the server. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-643) Refactor Bookinfo to Include Kiali Tesm Mesh Operator

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-643?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-643: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo > Refactor Bookinfo to Include Kiali Tesm Mesh Operator > ----------------------------------------------------- > > Key: SWSQE-643 > URL: https://issues.jboss.org/browse/SWSQE-643 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: infrastructure > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-642) Include the Registry Puller on the Pipeline

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-642?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-642. ------------------------------------------- Resolution: Done Created http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/registry-quay-pu... job > Include the Registry Puller on the Pipeline > ------------------------------------------- > > Key: SWSQE-642 > URL: https://issues.jboss.org/browse/SWSQE-642 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: infrastructure > > https://github.com/knrc/registry-puller needs to be included on Pipeline -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-643) Refactor Bookinfo to Include Kiali Tesm Mesh Operator

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-643: --------------------------------------------- Summary: Refactor Bookinfo to Include Kiali Tesm Mesh Operator Key: SWSQE-643 URL: https://issues.jboss.org/browse/SWSQE-643 Project: Kiali QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3736) DMN DT Analysis Table Completeness

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3736?page=com.atlassian.jira.plugi... ] Matteo Mortari resolved DROOLS-3736. ------------------------------------ Resolution: Won't Do In DMN, a gap would always result generically in a null (and an error, or a zero for C hit policy) so a generic message to report for the gap is deemed sufficient. If a more specific message is needed, either this JIRA will be reopened or a new one created with specific requirements > DMN DT Analysis Table Completeness > ---------------------------------- > > Key: DROOLS-3736 > URL: https://issues.jboss.org/browse/DROOLS-3736 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Gaps in relation with Hit Policy -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3772) DMN DT Analysis Rule masking

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3772: -------------------------------------- Summary: DMN DT Analysis Rule masking Key: DROOLS-3772 URL: https://issues.jboss.org/browse/DROOLS-3772 Project: Drools Issue Type: Feature Request Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Rule masking (in P tables where some rule is never the top priority). A rule is said to be masked if: - it overlaps with other rules - its output is lower priority than the output of other rules - one of the other rules is "wider" than the specific rule being masked -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3761) [DMN Designer] Enumeration constraint entry edit mode

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3761?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3761: ------------------------------------- [~uxdlc] Please, according to our weekly meeting, check the pattern fly spec, and reply here if the value should be lost in case user click out of the input box. > [DMN Designer] Enumeration constraint entry edit mode > ----------------------------------------------------- > > Key: DROOLS-3761 > URL: https://issues.jboss.org/browse/DROOLS-3761 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.19.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Minor > Labels: drools-tools > Attachments: focus_lost.webm, lost_focus_data_types.webm > > > The attached video shows the user interaction with enumeration constraint component. We can see if user fill valid values and clicks somewhere outside of the entry in edit mode, the values are lost. The only way how to save values is to click the *check* button. User should not lost filled in values if he clicks outside of input fields. > Please compare the same behavior with data types list view component. It means [^focus_lost.webm] vs [^lost_focus_data_types.webm] . -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3891) Cannot create xml-formatter and json-formatter with the same name as existing resources in logging subsystem

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-3891?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-3891: --------------------------------------- [~michpetrov] I think we just need to ensure that if the {{named-formatter}} attribute is not used and we use the {{formatter}} attribute which creates which creates a new {{PatternFormatter}} that we just use a unique name. The changes should only be required in WildFly itself. > Cannot create xml-formatter and json-formatter with the same name as existing resources in logging subsystem > ------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-3891 > URL: https://issues.jboss.org/browse/WFCORE-3891 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Nikoleta Žiaková > Assignee: James Perkins > Priority: Major > > When trying to create an {{xml-formatter}} or {{json-formatter}} with the same name as another resource (e.g. a {{file-handler}}), the operation fails: > {code} > [standalone@localhost:9990 /] /subsystem=logging/file-handler=test:add(file={path=aaa.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/xml-formatter=test:add > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: No property \"dateFormat\" setter found for formatter \"test\"", > "rolled-back" => true > } > {code} > Similarly vice-versa, when trying to create another resource in logging subsystem with the same name as an {{xml-formatter}} or a {{json-formatter}}, the operation fails: > {code} > [standalone@localhost:9990 /] /subsystem=logging/json-formatter=test:add > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/file-handler=test:add(file={path=test.log}) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: No property \"pattern\" setter found for formatter \"test\"", > "rolled-back" => true > } > {code} > The same scenario works for e.g. {{pattern-formatter}}: > {code} > [standalone@localhost:9990 /] /subsystem=logging/file-handler=test:add(file={path=test.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/pattern-formatter=test:add > {"outcome" => "success"} > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3771) Avoid handcrafted MVEL conversion in accumulate nodes

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-3771?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-3771: --------------------------------- Summary: Avoid handcrafted MVEL conversion in accumulate nodes (was: Avoid handcraftet mvel conversion in accumulate nodes) > Avoid handcrafted MVEL conversion in accumulate nodes > ----------------------------------------------------- > > Key: DROOLS-3771 > URL: https://issues.jboss.org/browse/DROOLS-3771 > Project: Drools > Issue Type: Enhancement > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > See AccumulateVisitor:525 > Currently in accumulate MVEL expressions are manually converted. > Now that we have a compiler we should use that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3771) Avoid handcraftet mvel conversion in accumulate nodes

by Luca Molteni (Jira)

Luca Molteni created DROOLS-3771: ------------------------------------ Summary: Avoid handcraftet mvel conversion in accumulate nodes Key: DROOLS-3771 URL: https://issues.jboss.org/browse/DROOLS-3771 Project: Drools Issue Type: Enhancement Reporter: Luca Molteni Assignee: Luca Molteni See AccumulateVisitor:525 Currently in accumulate MVEL expressions are manually converted. Now that we have a compiler we should use that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 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 March 2019