September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4126) Remove script tests for shells that require special scripting syntax

by James Perkins (JIRA)

James Perkins created WFCORE-4126: ------------------------------------- Summary: Remove script tests for shells that require special scripting syntax Key: WFCORE-4126 URL: https://issues.jboss.org/browse/WFCORE-4126 Project: WildFly Core Issue Type: Task Components: Scripts, Test Suite Reporter: James Perkins Assignee: James Perkins When the script tests were added there was tests that were ignored added for some shells we won't likely end up supporting. Those tests should just be removed since they're already ignored and those shells likely would require special syntax to get working. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-437) Maistra with Minimal Resource and Minimal Resource with Kiali

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-437?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-437. ------------------------------------------- Resolution: Done > Maistra with Minimal Resource and Minimal Resource with Kiali > ------------------------------------------------------------- > > Key: SWSQE-437 > URL: https://issues.jboss.org/browse/SWSQE-437 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > Minimal resource won't install kiali. > Minimal resource file with Kiali look like: > {code:yaml} > apiVersion: "istio.openshift.com/v1alpha1" > kind: "Installation" > metadata: > name: "istio-installation" > spec: > kiali: > username: ${OPENSHIFT_KIALI_USERNAME} > password: ${OPENSHIFT_KIALI_PASSWORD} > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11010) Document 2lc/JTA integration properties and add better detection of ehcache/JTAFactoryClass use

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-11010?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-11010: -------------------------------- Description: Document the "wildfly.jpa.regionfactory" and "wildfly.jpa.jtaplatform" properties for Hibernate ORM 5.3+ integration. Also automatically treat "wildfly.jpa.regionfactory" as false if [ehcache is being used|http://www.ehcache.org/documentation/2.7/integrations/hibernate.html] (e.g. check if the hibernate.cache.region.factory_class value starts with "net.sf.ehcache"). This should help applications that have configured to use Ehcache. Also automatically treat "wildfly.jpa.jtaplatform" as false if the application sets either "hibernate.transaction.factory_class" or "hibernate.transaction.jta.platform". This should help applications that have configured to use JTA transaction factory or transaction platform classes. was: Document the "wildfly.jpa.regionfactory" and "wildfly.jpa.jtaplatform" properties for Hibernate ORM 5.3+ integration. Also automatically treat "wildfly.jpa.regionfactory" as false if [ehcache is being used|http://www.ehcache.org/documentation/2.7/integrations/hibernate.html] (e.g. check if the hibernate.cache.region.factory_class value starts with "net.sf.ehcache"). Also automatically treat "wildfly.jpa.jtaplatform" as false if the application sets either "hibernate.transaction.factory_class" or "hibernate.transaction.jta.platform" > Document 2lc/JTA integration properties and add better detection of ehcache/JTAFactoryClass use > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11010 > URL: https://issues.jboss.org/browse/WFLY-11010 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 14.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 15.0.0.Alpha1 > > > Document the "wildfly.jpa.regionfactory" and "wildfly.jpa.jtaplatform" properties for Hibernate ORM 5.3+ integration. > Also automatically treat "wildfly.jpa.regionfactory" as false if [ehcache is being used|http://www.ehcache.org/documentation/2.7/integrations/hibernate.html] (e.g. check if the hibernate.cache.region.factory_class value starts with "net.sf.ehcache"). This should help applications that have configured to use Ehcache. > Also automatically treat "wildfly.jpa.jtaplatform" as false if the application sets either "hibernate.transaction.factory_class" or "hibernate.transaction.jta.platform". This should help applications that have configured to use JTA transaction factory or transaction platform classes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11010) Document 2lc/JTA integration properties and add better detection of ehcache/JTAFactoryClass use

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-11010?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-11010: -------------------------------- Description: Document the "wildfly.jpa.regionfactory" and "wildfly.jpa.jtaplatform" properties for Hibernate ORM 5.3+ integration. Also automatically treat "wildfly.jpa.regionfactory" as false if [ehcache is being used|http://www.ehcache.org/documentation/2.7/integrations/hibernate.html] (e.g. check if the hibernate.cache.region.factory_class value starts with "net.sf.ehcache"). Also automatically treat "wildfly.jpa.jtaplatform" as false if the application sets either "hibernate.transaction.factory_class" or "hibernate.transaction.jta.platform" was: Document the "wildfly.jpa.regionfactory" and "wildfly.jpa.jtaplatform" properties for Hibernate ORM 5.3+ integration. Also automatically set "wildfly.jpa.regionfactory" to false if [ehcache is being used|http://www.ehcache.org/documentation/2.7/integrations/hibernate.html] (e.g. check if the hibernate.cache.region.factory_class value starts with "net.sf.ehcache"). > Document 2lc/JTA integration properties and add better detection of ehcache/JTAFactoryClass use > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11010 > URL: https://issues.jboss.org/browse/WFLY-11010 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 14.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 15.0.0.Alpha1 > > > Document the "wildfly.jpa.regionfactory" and "wildfly.jpa.jtaplatform" properties for Hibernate ORM 5.3+ integration. > Also automatically treat "wildfly.jpa.regionfactory" as false if [ehcache is being used|http://www.ehcache.org/documentation/2.7/integrations/hibernate.html] (e.g. check if the hibernate.cache.region.factory_class value starts with "net.sf.ehcache"). > Also automatically treat "wildfly.jpa.jtaplatform" as false if the application sets either "hibernate.transaction.factory_class" or "hibernate.transaction.jta.platform" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11010) Document 2lc/JTA integration properties and add better detection of ehcache/JTAFactoryClass use

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-11010?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-11010: -------------------------------- Summary: Document 2lc/JTA integration properties and add better detection of ehcache/JTAFactoryClass use (was: Document 2lc/JTA integration properties and add better detection of ehcache use) > Document 2lc/JTA integration properties and add better detection of ehcache/JTAFactoryClass use > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11010 > URL: https://issues.jboss.org/browse/WFLY-11010 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 14.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 15.0.0.Alpha1 > > > Document the "wildfly.jpa.regionfactory" and "wildfly.jpa.jtaplatform" properties for Hibernate ORM 5.3+ integration. > Also automatically set "wildfly.jpa.regionfactory" to false if [ehcache is being used|http://www.ehcache.org/documentation/2.7/integrations/hibernate.html] (e.g. check if the hibernate.cache.region.factory_class value starts with "net.sf.ehcache"). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2922) CSS: Pop-over menu for DMN decision tables.

by Sarah Rambacher (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2922?page=com.atlassian.jira.plugi... ] Sarah Rambacher commented on DROOLS-2922: ----------------------------------------- [~manstis] I think I understand, but when I move the div.pull-right after the label, it still displays on the same line as the label. You have some other classes (.input-group and .kie-data-type-container) that I'm guessing might be causing problems. I'm happy to look at a live version if it's possible, or screen share to work through it. {code:java} <form id="#DecisionForm"> <label for="kieName">Name</label> <input class="form-control pf-c-form-control" type="text" aria-label="Name text input" id="kieName" placeholder="Name" aria-placeholder="Name"> <br/> <label for="kieDataType">Data Type</label> <div class="pull-right"> <a href="#0"> <span class="fa fa-gear"></span> Manage </a> </div> <div class="btn-group bootstrap-select form-control pf-c-form-control"> <button class="dropdown-toggle btn btn-default" type="button" id="dropdownMenu1" data-toggle="dropdown"> <span class="pull-left">Select</span> <span class="caret"></span> </button> <ul class="dropdown-menu" role="menu" aria-labelledby="dropdownMenu1"> <li role="presentation"><input role="menuitem" class="form-control pf-c-form-control" type="text" aria-label="Data type text input" id="kieSelectTypeIn" placeholder="Data type" aria-placeholder="Data type"></li> <li role="presentation"><a role="menuitem" tabindex="-1" href="#">any</a></li> <li role="presentation"><a role="menuitem" tabindex="-1" href="#">boolean</a></li> <li role="presentation"><a role="menuitem" tabindex="-1" href="#">date</a></li> <li role="presentation"><a role="menuitem" tabindex="-1" href="#">applicant</a></li> </ul> </div> </form> {code} > CSS: Pop-over menu for DMN decision tables. > ------------------------------------------- > > Key: DROOLS-2922 > URL: https://issues.jboss.org/browse/DROOLS-2922 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-2922.png, DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, pop-overc.png, pop-overcSpecs.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases from the DMN canvas view, as a user I want to: > * Search a list of available data types from a decision table, as part of an input/selection process. > * Select a data type inline from a decision table. > * Have a means to rename the Decision (node.) > * Have a means to access the Manage Data Types dialog. > Notes: > Design requires a Pop-over, which includes: > * Form field labels for usability (context) and accessibility. > * Variant 1 of the PF pop-over patterns, which supports a the pop-up title. > * Drop down component with Live Search > * "Manage" link opens a dialog. > * Pop-up is initiated by a single-left mouse click within the respective decision table cell. > * Design needs to be reasonably consistent with Stunner and PF components. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3027) [DMN Designer] Differentiate zero and non zero custom data types

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3027?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3027: -------------------------------------- Assignee: Guilherme Carreiro (was: Michael Anstis) > [DMN Designer] Differentiate zero and non zero custom data types > ---------------------------------------------------------------- > > Key: DROOLS-3027 > URL: https://issues.jboss.org/browse/DROOLS-3027 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Labels: UX, drools-tools > Attachments: Screenshot from 2018-09-24 18-12-02.png > > > There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3030) [DMN Designer] Expand / Collapse all

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3030?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3030: -------------------------------------- Assignee: Guilherme Carreiro (was: Michael Anstis) > [DMN Designer] Expand / Collapse all > ------------------------------------ > > Key: DROOLS-3030 > URL: https://issues.jboss.org/browse/DROOLS-3030 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Labels: UX, drools-tools > > User should have possibility to easily expand / collapse all data types in the *manage custom data type* dialog. > h2. Manual acceptance test > - Expand > -- All collapsed initially > -- Something collapsed initially, something expanded already > -- All expanded already > - Collapse > -- All expanded initially > -- Something expanded initially, something collapsed already > -- All collapsed already > - No error warning in browser console log -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1678) Avoid NPE in AcmeClientSpi#checkContentType() when the content type is null and try to fix intermittent failures in AcmeClientSpiTest

by Farah Juma (JIRA)

Farah Juma created ELY-1678: ------------------------------- Summary: Avoid NPE in AcmeClientSpi#checkContentType() when the content type is null and try to fix intermittent failures in AcmeClientSpiTest Key: ELY-1678 URL: https://issues.jboss.org/browse/ELY-1678 Project: WildFly Elytron Issue Type: Task Components: Testsuite Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2950) [DMN Editor] Custom data-types - ItemDefinitionRecordEngine - The QName instance should lookup the real prefix from the URI

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2950?page=com.atlassian.jira.plugi... ] Guilherme Carreiro commented on DROOLS-2950: -------------------------------------------- [~jomarko], This ticket was created because of this comment: https://github.com/kiegroup/kie-wb-common/pull/2079#discussion_r214376324 ..the _QName_ was being instantiated like this: {{new QName(FEEL.getUri(), record.getType(), FEEL.getPrefix());}} However, [~manstis] alerted me regarding the importance of looking-up the real prefix. So, the proposed pull request introduces the `ItemDefinitionUtils#normaliseTypeRef` method to solve the issue (that's based on this method https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-dmn/k...). One thing you can do to check if the prefix is being correctly fetched is to change it in the {{definitions}} tag, by replacing the attribute from: {{xmlns:feel="http://www.omg.org/spec/FEEL/20140401"}} to: {{xmlns:cheese="http://www.omg.org/spec/FEEL/20140401"}} Then, you can update a Data Type (like {{tCity.uuid}}) from {{String}} to {{Number}}. You're going to notice that the DMN file will be change from: {{<dmn11:typeRef>feel:string</dmn11:typeRef>}} to: {{<dmn11:typeRef>cheese:number</dmn11:typeRef>}} ..because the new prefix was fetched ;-) > [DMN Editor] Custom data-types - ItemDefinitionRecordEngine - The QName instance should lookup the real prefix from the URI > --------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2950 > URL: https://issues.jboss.org/browse/DROOLS-2950 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Labels: drools-tools > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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 September 2018