November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3261) [DMN Designer] The `defaultOutputValue` is being persisted as an `outputValue`

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3261?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3261: ------------------------------------- [~manstis] thanks, I reported the typeRef inconsistency I see as https://issues.jboss.org/browse/DROOLS-3289. > [DMN Designer] The `defaultOutputValue` is being persisted as an `outputValue` > ------------------------------------------------------------------------------ > > Key: DROOLS-3261 > URL: https://issues.jboss.org/browse/DROOLS-3261 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Fix For: 7.14.0.Final > > Attachments: diagram.png, dtable.png > > > When the user persists the following diagram: > !diagram.png|thumbnail! > ..with the following Decision Table: > !dtable.png|thumbnail! > .. select the "Can drink beer?" header, set the default value as {{false}} and the file: > {quote} > <dmn:outputValues id="_A117F7DC-508C-4132-8F5F-8F8F2B0B489F"> > <dmn:text>false</dmn:text> > </dmn:outputValues> > <dmn:defaultOutputEntry id="_A4881AD1-7EDC-4B4D-AC00-078626795BA7" typeRef="string"> > <dmn:text></dmn:text> > </dmn:defaultOutputEntry> > {quote} > ..and the expected behaviour is to persist the value {{false}} in the {{defaultOutputEntry}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3289) [DMN Designer] Default Output Value typeRef

by Jozef Marko (Jira)

Jozef Marko created DROOLS-3289: ----------------------------------- Summary: [DMN Designer] Default Output Value typeRef Key: DROOLS-3289 URL: https://issues.jboss.org/browse/DROOLS-3289 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Jozef Marko Assignee: Michael Anstis If the default output value of decision table is set, its {{typeRef}} doesn't respect its parent {{typeRef}}, example below. {code:xml} <dmn:output id="_8023A5BD-71A4-4C3F-A5B9-B62D5BC34345" name="output-1" typeRef="number"> <dmn:outputValues id="_C9AEC57C-1F1E-4115-9449-F287F010EA07"> <dmn:text>456</dmn:text> </dmn:outputValues> <dmn:defaultOutputEntry id="_36F46818-D5F9-4F58-A758-73B853EC418B" typeRef="string"> <dmn:text>123</dmn:text> </dmn:defaultOutputEntry> </dmn:output> ... {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3289) [DMN Designer] Default Output Value typeRef

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3289?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3289: ------------------------------------- [~manstis] [~tirelli] please advice priority. > [DMN Designer] Default Output Value typeRef > ------------------------------------------- > > Key: DROOLS-3289 > URL: https://issues.jboss.org/browse/DROOLS-3289 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > If the default output value of decision table is set, its {{typeRef}} doesn't respect its parent {{typeRef}}, example below. > {code:xml} > <dmn:output id="_8023A5BD-71A4-4C3F-A5B9-B62D5BC34345" name="output-1" typeRef="number"> > <dmn:outputValues id="_C9AEC57C-1F1E-4115-9449-F287F010EA07"> > <dmn:text>456</dmn:text> > </dmn:outputValues> > <dmn:defaultOutputEntry id="_36F46818-D5F9-4F58-A758-73B853EC418B" typeRef="string"> > <dmn:text>123</dmn:text> > </dmn:defaultOutputEntry> > </dmn:output> > ... > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11313) Does the wildfly 14 support java ee security api 1.0?

by 69699 i (Jira)

69699 i created WFLY-11313: ------------------------------ Summary: Does the wildfly 14 support java ee security api 1.0? Key: WFLY-11313 URL: https://issues.jboss.org/browse/WFLY-11313 Project: WildFly Issue Type: Support Patch Components: EE Affects Versions: 14.0.0.Final Reporter: 69699 i Attachments: EE8Security.7z -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3281) [DMN Designer] The output name is valorized for single output decision table

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3281?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3281: -------------------------------- Description: h2. Manual acceptance test - Decision Table expression with single output, no name stored (/) - Decision Table expression with multiple outputs, name stored (/) was: h2. Manual acceptance test - Decision Table expression with single output, no name stored - Decision Table expression with multiple outputs, name stored > [DMN Designer] The output name is valorized for single output decision table > ---------------------------------------------------------------------------- > > Key: DROOLS-3281 > URL: https://issues.jboss.org/browse/DROOLS-3281 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Blocker > Labels: drools-tools > > h2. Manual acceptance test > - Decision Table expression with single output, no name stored (/) > - Decision Table expression with multiple outputs, name stored (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3281) [DMN Designer] The output name is valorized for single output decision table

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3281?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3281: -------------------------------- Description: h2. Manual acceptance test - Decision Table expression with single output, no name stored - Decision Table expression with multiple outputs, name stored > [DMN Designer] The output name is valorized for single output decision table > ---------------------------------------------------------------------------- > > Key: DROOLS-3281 > URL: https://issues.jboss.org/browse/DROOLS-3281 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Blocker > Labels: drools-tools > > h2. Manual acceptance test > - Decision Table expression with single output, no name stored > - Decision Table expression with multiple outputs, name stored -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11117) Executing legacy operations in mod_cluster subsystem is not possible with configuration with just one proxy

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11117?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11117: --------------------------------- Fix Version/s: 15.0.0.Alpha1 > Executing legacy operations in mod_cluster subsystem is not possible with configuration with just one proxy > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-11117 > URL: https://issues.jboss.org/browse/WFLY-11117 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 14.0.0.Final > Reporter: Jan Kašík > Assignee: Radoslav Husar > Priority: Major > Fix For: 15.0.0.Alpha1 > > > Running legacy operation ends up with an error: > {code} > [standalone@localhost:9990 /] /subsystem=modcluster/:disable > { > "outcome" => "failed", > "failure-description" => "WFLYMODCLS0022: Legacy operations cannot be used with multiple proxy configurations. Use non-deprecated operations at the correct proxy address.", > "rolled-back" => true > } > {code} > mod_cluster configuration: > {code} > [standalone@localhost:9990 /] /subsystem=modcluster/:read-resource > { > "outcome" => "success", > "result" => { > "mod-cluster-config" => {"configuration" => undefined}, > "proxy" => {"default" => undefined} > } > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11279) The org.jboss.as.jpa module includes some unnecessary dependencies

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11279?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11279: --------------------------------- Fix Version/s: 15.0.0.Alpha1 > The org.jboss.as.jpa module includes some unnecessary dependencies > ------------------------------------------------------------------ > > Key: WFLY-11279 > URL: https://issues.jboss.org/browse/WFLY-11279 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 15.0.0.Alpha1 > > > Prune some dependencies that analysis shows are not used by the dependent org.jboss.as.jpa: > org.jboss.jts > org.jboss.jts.integration > org.jboss.as.clustering.common > org.jboss.as.connector > org.jboss.as.web-common > org.wildfly.clustering.service -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-490) b16 cluster is down

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-490?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-490: ------------------------------- Description: B16 cluster is down / not working / broken. Backgroud: - Openshift projects were not deleting - Restarted all (3) nodes - Cluster did not come back up was: B16 cluster is down. Backgroud: - Openshift projects were not deleting - Restarted all (3) nodes - Cluster did not come back up Team: Infrastructure (was: Infrastructure) > b16 cluster is down > ------------------- > > Key: SWSQE-490 > URL: https://issues.jboss.org/browse/SWSQE-490 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Michael Foley > Priority: Major > > B16 cluster is down / not working / broken. > Backgroud: > - Openshift projects were not deleting > - Restarted all (3) nodes > - Cluster did not come back up -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-34) Upgrade WildFly Elytron to 1.7.0.Final

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-34?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELYWEB-34: ----------------------------- Fix Version/s: 1.3.0.CR4 > Upgrade WildFly Elytron to 1.7.0.Final > -------------------------------------- > > Key: ELYWEB-34 > URL: https://issues.jboss.org/browse/ELYWEB-34 > Project: Elytron Web > Issue Type: Component Upgrade > Components: Parent > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.3.0.CR4 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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 November 2018