August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4478) [DMN Designer] Decision Service - Models from other vendors are being imported with extra decision services

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4478?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4478: ------------------------------------ Summary: [DMN Designer] Decision Service - Models from other vendors are being imported with extra decision services (was: [DMN Designer] Decision Service - Models from other vendors are being imported with an extra decision service) > [DMN Designer] Decision Service - Models from other vendors are being imported with extra decision services > ----------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4478 > URL: https://issues.jboss.org/browse/DROOLS-4478 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: extra-ds.png > > > When users import models from other vendors, an extra decision service is added. > *Actual:* > !extra-ds.png|thumbnail! > *Expected:* > The node should not be there. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4627) Fix for adding of OCSP responder-certificate and responder-keystore

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/WFCORE-4627?page=com.atlassian.jira.plugi... ] Ashley Abdel-Sayed updated WFCORE-4627: --------------------------------------- Description: Bug fix to fix parsing and adding of responder-certificate and responder-keystore to ocsp configuration. Fix will be adding RESPONDER_CERTIFICATE and RESPONDER_KEYSTORE to the OCSP attribute builder and adding responder-certificate and responder-keystore attributes to the ocspType in elytron schema. (was: Bug fix to fix parsing and adding of responder-certificate and responder-keystore to ocsp configuration. Fix will be adding RESPONDER_CERTIFICATE and RESPONDER_KEYSTORE to the OCSP attribute builder and adding responder-certificate and responder-keystore attributes to the ocsp-type in schema.) > Fix for adding of OCSP responder-certificate and responder-keystore > ------------------------------------------------------------------- > > Key: WFCORE-4627 > URL: https://issues.jboss.org/browse/WFCORE-4627 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > > Bug fix to fix parsing and adding of responder-certificate and responder-keystore to ocsp configuration. Fix will be adding RESPONDER_CERTIFICATE and RESPONDER_KEYSTORE to the OCSP attribute builder and adding responder-certificate and responder-keystore attributes to the ocspType in elytron schema. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4627) Fix for adding of OCSP responder-certificate and responder-keystore

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/WFCORE-4627?page=com.atlassian.jira.plugi... ] Ashley Abdel-Sayed updated WFCORE-4627: --------------------------------------- Description: Bug fix to fix parsing and adding of responder-certificate and responder-keystore to ocsp configuration. Fix will be adding RESPONDER_CERTIFICATE and RESPONDER_KEYSTORE to the OCSP attribute builder and adding responder-certificate and responder-keystore attributes to the ocsp-type in schema. (was: Bug fix to fix parsing and adding of responder-certificate and responder-keystore attributes to an ocsp configuration) > Fix for adding of OCSP responder-certificate and responder-keystore > ------------------------------------------------------------------- > > Key: WFCORE-4627 > URL: https://issues.jboss.org/browse/WFCORE-4627 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > > Bug fix to fix parsing and adding of responder-certificate and responder-keystore to ocsp configuration. Fix will be adding RESPONDER_CERTIFICATE and RESPONDER_KEYSTORE to the OCSP attribute builder and adding responder-certificate and responder-keystore attributes to the ocsp-type in schema. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-273) `Inconsistent stackmap frames` issue while instrumenting Kotlin anonymous class

by Serkan Özal (Jira)

[ https://issues.jboss.org/browse/JASSIST-273?page=com.atlassian.jira.plugi... ] Serkan Özal updated JASSIST-273: -------------------------------- Description: https://github.com/serkan-ozal/javassist-issue-report/blob/master/src/mai... reproduces the following issue with version {{3.25.0-GA}}: {code:java} Exception in thread "main" java.lang.VerifyError: Inconsistent stackmap frames at branch target 170 Exception Details: Location: ozal/serkan/javassist/issue/report/Runner$run$result$1.invokeSuspend(Ljava/lang/Object;)Ljava/lang/Object; @98: goto Reason: Current frame's stack size doesn't match stackmap. Current Frame: bci: @98 flags: { } locals: { 'ozal/serkan/javassist/issue/report/Runner$run$result$1', 'java/lang/Object', 'kotlinx/coroutines/CoroutineScope', top, top, 'java/lang/Object' } stack: { 'java/lang/Object', 'java/lang/Object' } Stackmap Frame: bci: @170 flags: { } locals: { 'ozal/serkan/javassist/issue/report/Runner$run$result$1', 'java/lang/Object', top, top, top, 'java/lang/Object' } stack: { 'java/lang/Object' } Bytecode: 0x0000000: b200 b812 bab6 0062 b800 203a 052a b400 0x0000010: 24aa 0000 0000 008f 0000 0000 0000 0001 0x0000020: 0000 0017 0000 0054 2b59 c100 2699 000a 0x0000030: c000 26b4 002a bf57 2ab4 002c 4d00 b200 0x0000040: 320a b600 36bb 0038 592a 01b7 003c c000 0x0000050: 072a 2a04 b500 24b8 0042 5919 05a6 0019 0x0000060: 1905 a700 482b 59c1 0026 9900 0ac0 0026 0x0000070: b400 2abf 572b c000 444e a700 223a 04b2 0x0000080: 004a bb00 4c59 b700 4f12 51b6 0055 1904 0x0000090: b600 58b6 005c b600 6212 644e 2da7 000d 0x00000a0: bb00 6659 1268 b700 6abf 3a07 b200 b812 0x00000b0: bcb6 0062 1907 b0 Exception Handler Table: bci [61, 90] => handler: 125 bci [101, 122] => handler: 125 Stackmap Table: full_frame(@40,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{}) same_locals_1_stack_item_frame(@55,Object[#113]) same_frame(@101) same_locals_1_stack_item_frame(@116,Object[#113]) full_frame(@118,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{Object[#113]}) same_locals_1_stack_item_frame(@125,Object[#26]) full_frame(@156,{Object[#2],Object[#113],Top,Object[#68],Top,Object[#113]},{}) full_frame(@160,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{}) full_frame(@170,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{Object[#113]}) at ozal.serkan.javassist.issue.report.Runner.run(Runner.kt:19) at ozal.serkan.javassist.issue.report.RunnerInstrumentation.main(RunnerInstrumentation.java:35) {code} The problem is that while instrumenting {{ozal.serkan.javassist.issue.report.Runner$run$result$1}} anonymous Kotlin class, the stackmap inconsistency raises. was: https://github.com/serkan-ozal/javassist-issue-report/blob/master/src/mai... reproduces the following issue: {code:java} Exception in thread "main" java.lang.VerifyError: Inconsistent stackmap frames at branch target 170 Exception Details: Location: ozal/serkan/javassist/issue/report/Runner$run$result$1.invokeSuspend(Ljava/lang/Object;)Ljava/lang/Object; @98: goto Reason: Current frame's stack size doesn't match stackmap. Current Frame: bci: @98 flags: { } locals: { 'ozal/serkan/javassist/issue/report/Runner$run$result$1', 'java/lang/Object', 'kotlinx/coroutines/CoroutineScope', top, top, 'java/lang/Object' } stack: { 'java/lang/Object', 'java/lang/Object' } Stackmap Frame: bci: @170 flags: { } locals: { 'ozal/serkan/javassist/issue/report/Runner$run$result$1', 'java/lang/Object', top, top, top, 'java/lang/Object' } stack: { 'java/lang/Object' } Bytecode: 0x0000000: b200 b812 bab6 0062 b800 203a 052a b400 0x0000010: 24aa 0000 0000 008f 0000 0000 0000 0001 0x0000020: 0000 0017 0000 0054 2b59 c100 2699 000a 0x0000030: c000 26b4 002a bf57 2ab4 002c 4d00 b200 0x0000040: 320a b600 36bb 0038 592a 01b7 003c c000 0x0000050: 072a 2a04 b500 24b8 0042 5919 05a6 0019 0x0000060: 1905 a700 482b 59c1 0026 9900 0ac0 0026 0x0000070: b400 2abf 572b c000 444e a700 223a 04b2 0x0000080: 004a bb00 4c59 b700 4f12 51b6 0055 1904 0x0000090: b600 58b6 005c b600 6212 644e 2da7 000d 0x00000a0: bb00 6659 1268 b700 6abf 3a07 b200 b812 0x00000b0: bcb6 0062 1907 b0 Exception Handler Table: bci [61, 90] => handler: 125 bci [101, 122] => handler: 125 Stackmap Table: full_frame(@40,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{}) same_locals_1_stack_item_frame(@55,Object[#113]) same_frame(@101) same_locals_1_stack_item_frame(@116,Object[#113]) full_frame(@118,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{Object[#113]}) same_locals_1_stack_item_frame(@125,Object[#26]) full_frame(@156,{Object[#2],Object[#113],Top,Object[#68],Top,Object[#113]},{}) full_frame(@160,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{}) full_frame(@170,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{Object[#113]}) at ozal.serkan.javassist.issue.report.Runner.run(Runner.kt:19) at ozal.serkan.javassist.issue.report.RunnerInstrumentation.main(RunnerInstrumentation.java:35) {code} The problem is that while instrumenting {{ozal.serkan.javassist.issue.report.Runner$run$result$1}} anonymous Kotlin class, the stackmap inconsistency raises. > `Inconsistent stackmap frames` issue while instrumenting Kotlin anonymous class > ------------------------------------------------------------------------------- > > Key: JASSIST-273 > URL: https://issues.jboss.org/browse/JASSIST-273 > Project: Javassist > Issue Type: Bug > Reporter: Serkan Özal > Assignee: Shigeru Chiba > Priority: Major > > https://github.com/serkan-ozal/javassist-issue-report/blob/master/src/mai... reproduces the following issue with version {{3.25.0-GA}}: > {code:java} > Exception in thread "main" java.lang.VerifyError: Inconsistent stackmap frames at branch target 170 > Exception Details: > Location: > ozal/serkan/javassist/issue/report/Runner$run$result$1.invokeSuspend(Ljava/lang/Object;)Ljava/lang/Object; @98: goto > Reason: > Current frame's stack size doesn't match stackmap. > Current Frame: > bci: @98 > flags: { } > locals: { 'ozal/serkan/javassist/issue/report/Runner$run$result$1', 'java/lang/Object', 'kotlinx/coroutines/CoroutineScope', top, top, 'java/lang/Object' } > stack: { 'java/lang/Object', 'java/lang/Object' } > Stackmap Frame: > bci: @170 > flags: { } > locals: { 'ozal/serkan/javassist/issue/report/Runner$run$result$1', 'java/lang/Object', top, top, top, 'java/lang/Object' } > stack: { 'java/lang/Object' } > Bytecode: > 0x0000000: b200 b812 bab6 0062 b800 203a 052a b400 > 0x0000010: 24aa 0000 0000 008f 0000 0000 0000 0001 > 0x0000020: 0000 0017 0000 0054 2b59 c100 2699 000a > 0x0000030: c000 26b4 002a bf57 2ab4 002c 4d00 b200 > 0x0000040: 320a b600 36bb 0038 592a 01b7 003c c000 > 0x0000050: 072a 2a04 b500 24b8 0042 5919 05a6 0019 > 0x0000060: 1905 a700 482b 59c1 0026 9900 0ac0 0026 > 0x0000070: b400 2abf 572b c000 444e a700 223a 04b2 > 0x0000080: 004a bb00 4c59 b700 4f12 51b6 0055 1904 > 0x0000090: b600 58b6 005c b600 6212 644e 2da7 000d > 0x00000a0: bb00 6659 1268 b700 6abf 3a07 b200 b812 > 0x00000b0: bcb6 0062 1907 b0 > Exception Handler Table: > bci [61, 90] => handler: 125 > bci [101, 122] => handler: 125 > Stackmap Table: > full_frame(@40,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{}) > same_locals_1_stack_item_frame(@55,Object[#113]) > same_frame(@101) > same_locals_1_stack_item_frame(@116,Object[#113]) > full_frame(@118,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{Object[#113]}) > same_locals_1_stack_item_frame(@125,Object[#26]) > full_frame(@156,{Object[#2],Object[#113],Top,Object[#68],Top,Object[#113]},{}) > full_frame(@160,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{}) > full_frame(@170,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{Object[#113]}) > at ozal.serkan.javassist.issue.report.Runner.run(Runner.kt:19) > at ozal.serkan.javassist.issue.report.RunnerInstrumentation.main(RunnerInstrumentation.java:35) > {code} > The problem is that while instrumenting {{ozal.serkan.javassist.issue.report.Runner$run$result$1}} anonymous Kotlin class, the stackmap inconsistency raises. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-273) `Inconsistent stackmap frames` issue while instrumenting Kotlin anonymous class

by Serkan Özal (Jira)

Serkan Özal created JASSIST-273: ----------------------------------- Summary: `Inconsistent stackmap frames` issue while instrumenting Kotlin anonymous class Key: JASSIST-273 URL: https://issues.jboss.org/browse/JASSIST-273 Project: Javassist Issue Type: Bug Reporter: Serkan Özal Assignee: Shigeru Chiba https://github.com/serkan-ozal/javassist-issue-report/blob/master/src/mai... reproduces the following issue: {code:java} Exception in thread "main" java.lang.VerifyError: Inconsistent stackmap frames at branch target 170 Exception Details: Location: ozal/serkan/javassist/issue/report/Runner$run$result$1.invokeSuspend(Ljava/lang/Object;)Ljava/lang/Object; @98: goto Reason: Current frame's stack size doesn't match stackmap. Current Frame: bci: @98 flags: { } locals: { 'ozal/serkan/javassist/issue/report/Runner$run$result$1', 'java/lang/Object', 'kotlinx/coroutines/CoroutineScope', top, top, 'java/lang/Object' } stack: { 'java/lang/Object', 'java/lang/Object' } Stackmap Frame: bci: @170 flags: { } locals: { 'ozal/serkan/javassist/issue/report/Runner$run$result$1', 'java/lang/Object', top, top, top, 'java/lang/Object' } stack: { 'java/lang/Object' } Bytecode: 0x0000000: b200 b812 bab6 0062 b800 203a 052a b400 0x0000010: 24aa 0000 0000 008f 0000 0000 0000 0001 0x0000020: 0000 0017 0000 0054 2b59 c100 2699 000a 0x0000030: c000 26b4 002a bf57 2ab4 002c 4d00 b200 0x0000040: 320a b600 36bb 0038 592a 01b7 003c c000 0x0000050: 072a 2a04 b500 24b8 0042 5919 05a6 0019 0x0000060: 1905 a700 482b 59c1 0026 9900 0ac0 0026 0x0000070: b400 2abf 572b c000 444e a700 223a 04b2 0x0000080: 004a bb00 4c59 b700 4f12 51b6 0055 1904 0x0000090: b600 58b6 005c b600 6212 644e 2da7 000d 0x00000a0: bb00 6659 1268 b700 6abf 3a07 b200 b812 0x00000b0: bcb6 0062 1907 b0 Exception Handler Table: bci [61, 90] => handler: 125 bci [101, 122] => handler: 125 Stackmap Table: full_frame(@40,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{}) same_locals_1_stack_item_frame(@55,Object[#113]) same_frame(@101) same_locals_1_stack_item_frame(@116,Object[#113]) full_frame(@118,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{Object[#113]}) same_locals_1_stack_item_frame(@125,Object[#26]) full_frame(@156,{Object[#2],Object[#113],Top,Object[#68],Top,Object[#113]},{}) full_frame(@160,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{}) full_frame(@170,{Object[#2],Object[#113],Top,Top,Top,Object[#113]},{Object[#113]}) at ozal.serkan.javassist.issue.report.Runner.run(Runner.kt:19) at ozal.serkan.javassist.issue.report.RunnerInstrumentation.main(RunnerInstrumentation.java:35) {code} The problem is that while instrumenting {{ozal.serkan.javassist.issue.report.Runner$run$result$1}} anonymous Kotlin class, the stackmap inconsistency raises. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4480) [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types (7.6)

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-4480: --------------------------------------- Summary: [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types (7.6) Key: DROOLS-4480 URL: https://issues.jboss.org/browse/DROOLS-4480 Project: Drools Issue Type: Epic Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes This is an umbrella for all JIRAs (target to 7.6) related to Business Central Data Objects as DMN Data Types. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4627) Fix for adding of OCSP responder-certificate and responder-keystore

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/WFCORE-4627?page=com.atlassian.jira.plugi... ] Ashley Abdel-Sayed reassigned WFCORE-4627: ------------------------------------------ Assignee: Ashley Abdel-Sayed (was: Darran Lofthouse) > Fix for adding of OCSP responder-certificate and responder-keystore > ------------------------------------------------------------------- > > Key: WFCORE-4627 > URL: https://issues.jboss.org/browse/WFCORE-4627 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > > Bug fix to fix parsing and adding of responder-certificate and responder-keystore attributes to an ocsp configuration -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4479) [DMN Designer] Automatic Layout - The Automatic Layout feature does not work with models imported to other vendors

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4479?page=com.atlassian.jira.plugi... ] Guilherme Gomes commented on DROOLS-4479: ----------------------------------------- [~dadossan], Here's the DMN file and the model on Trisotech editor: https://gist.github.com/karreiro/8eda1aff0f61df10ff75833950fcc74f > [DMN Designer] Automatic Layout - The Automatic Layout feature does not work with models imported to other vendors > ------------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-4479 > URL: https://issues.jboss.org/browse/DROOLS-4479 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: 2019-08-26 16.55.43.gif > > > The Automatic Layout feature does not work with models imported to other vendors. See the demo: > !2019-08-26 16.55.43.gif|width=800! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4479) [DMN Designer] Automatic Layout - The Automatic Layout feature does not work with models imported to other vendors

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4479?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4479: ------------------------------------ Comment: was deleted (was: [~dadossan], Here's the DMN file and the model on Trisotech editor: https://gist.github.com/karreiro/8eda1aff0f61df10ff75833950fcc74f) > [DMN Designer] Automatic Layout - The Automatic Layout feature does not work with models imported to other vendors > ------------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-4479 > URL: https://issues.jboss.org/browse/DROOLS-4479 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: 2019-08-26 16.55.43.gif > > > The Automatic Layout feature does not work with models imported to other vendors. See the demo: > !2019-08-26 16.55.43.gif|width=800! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4479) [DMN Designer] Automatic Layout - The Automatic Layout feature does not work with models imported to other vendors

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4479?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4479: ------------------------------------ Description: The Automatic Layout feature does not work with models imported to other vendors. See the demo: !2019-08-26 16.55.43.gif|width=800! was: The Automatic Layout feature does not work with models imported to other vendors. See the demo: !2019-08-26 16.55.43.gif|width=600! > [DMN Designer] Automatic Layout - The Automatic Layout feature does not work with models imported to other vendors > ------------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-4479 > URL: https://issues.jboss.org/browse/DROOLS-4479 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: 2019-08-26 16.55.43.gif > > > The Automatic Layout feature does not work with models imported to other vendors. See the demo: > !2019-08-26 16.55.43.gif|width=800! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 August 2019