October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11165) Eliminate unessential module dependencies on the org.jboss.as.transactions module

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11165?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11165: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/11745 > Eliminate unessential module dependencies on the org.jboss.as.transactions module > --------------------------------------------------------------------------------- > > Key: WFLY-11165 > URL: https://issues.jboss.org/browse/WFLY-11165 > Project: WildFly > Issue Type: Enhancement > Components: Class Loading, Management, Transactions > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > As part of our work on getting maximum benefit from Galleon, we want to eliminate unnecessary hard dependencies between Galleon packages, most of which are just provisioning wrappers around the FS content for our JBoss Modules modules. So that means cutting dependency links between modules. > The org.jboss.as.transactions module necessarily has a large dependency tree, so if other modules depend on it, they then also have a large dependency tree, perhaps much larger than whatever they really need. So I want to eliminate such dependencies whereever possible. > There are quite a few modules that depend on org.jboss.as.transactions solely for ServiceName constants for services that provide value types not from org.jboss.as.transactions, e.g. TransactionManager which is from the javax.transaction.api module. So the main (perhaps only) task here will be to eliminate those links. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3142) [DMN Designer] Relation: Add additional Properties to drill-down

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3142?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3142: ----------------------------------- Description: The Properties Panel currently shows properties for Stunner-level "graph" components. *Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".* h2. Properties on the Grid Level The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel. (everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property) h3. Relation ||Selected item||Properties panel items||type|| || |Row|n/a|n/a|n/a| |Column|type Ref|ItemDefinition ref|(x)| |Cell|ExpressionLanguage|URI|(/)| h2. Manual Acceptance Test - Switching between DRG and Grid editor, check proper fields shown - Switching between rows, columns, cells in Grid editor, check proper fields -- In same expression kind -- Across different expression kinds - Clear expression kind - Read only mode - older asset version - All Grid specific properties saved was: The Properties Panel currently shows properties for Stunner-level "graph" components. *Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".* h2. Properties on the Grid Level The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel. (everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property) h3. Relation ||Selected item||Properties panel items||type|| || |Row|n/a|n/a|n/a| |Column|type Ref|ItemDefinition ref|(x)| |Cell|ExpressionLanguage|URI|(x)| h2. Manual Acceptance Test - Switching between DRG and Grid editor, check proper fields shown - Switching between rows, columns, cells in Grid editor, check proper fields -- In same expression kind -- Across different expression kinds - Clear expression kind - Read only mode - older asset version - All Grid specific properties saved > [DMN Designer] Relation: Add additional Properties to drill-down > ---------------------------------------------------------------- > > Key: DROOLS-3142 > URL: https://issues.jboss.org/browse/DROOLS-3142 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > > The Properties Panel currently shows properties for Stunner-level "graph" components. > *Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".* > h2. Properties on the Grid Level > The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel. > (everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property) > h3. Relation > ||Selected item||Properties panel items||type|| || > |Row|n/a|n/a|n/a| > |Column|type Ref|ItemDefinition ref|(x)| > |Cell|ExpressionLanguage|URI|(/)| > h2. Manual Acceptance Test > - Switching between DRG and Grid editor, check proper fields shown > - Switching between rows, columns, cells in Grid editor, check proper fields > -- In same expression kind > -- Across different expression kinds > - Clear expression kind > - Read only mode - older asset version > - All Grid specific properties saved -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2804) [DMN Designer] Literal Expression: Properties Panel to drill-down to DMN component level

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-2804?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2804: ----------------------------------- Summary: [DMN Designer] Literal Expression: Properties Panel to drill-down to DMN component level (was: [DMN Designer] Properties Panel to drill-down to DMN component level - Literal Expression) > [DMN Designer] Literal Expression: Properties Panel to drill-down to DMN component level > ---------------------------------------------------------------------------------------- > > Key: DROOLS-2804 > URL: https://issues.jboss.org/browse/DROOLS-2804 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Fix For: 7.13.0.Final > > > The Properties Panel currently shows properties for Stunner-level "graph" components. > We need, for DMN, the Properties Panel to show the properties of DMN elements' properties at the "grid" level. For example, when a {{Context}} is selected the Properties Panel should show only the top level properties for the {{Context}} (i.e. not those of its {{ContextEntries}}). Selection of a {{ContextEntry}} should refresh the Properties Panel to show only the top-level properties of the {{ContextEntry}}. Selection of the {{ContextEntry}}'s {{Expression}} should again refresh the Properties Panel to show only the top-level properties of the {{Expression}} and so forth. > h2. Properties on the Grid Level > The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel. > (everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property) > h3. Literal expression > ||Selected item||Properties panel items||type||Found Issues|| > |Cell|ExpressionLanguage|URI|DROOLS-3116, DROOLS-3117, DROOLS-3118, DROOLS-3122| > h2. Manual Acceptance Test > - Switching between DRG and Grid editor, check proper fields shown > - Switching between rows, columns, cells in Grid editor, check proper fields > -- In same expression kind > -- Across different expression kinds > - Clear expression kind > - Read only mode - older asset version > - All Grid specific properties saved -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11177) Add an initial private capability for the JPA subsystem

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11177?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11177: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/11745 > Add an initial private capability for the JPA subsystem > ------------------------------------------------------- > > Key: WFLY-11177 > URL: https://issues.jboss.org/browse/WFLY-11177 > Project: WildFly > Issue Type: Sub-task > Components: JPA / Hibernate > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > At some point we want a public capability for JPA, so it can expose a formal contract to other subsystem (e.g. weld.) But sorting out what that capability exposes doesn't need to block adding a private capability first. Having the private capability will allow the JPA subsystem to properly expose the requirements it has on capabilities exposed by other subsystems. And that will allow Galleon to properly understand those relationships when it generates configurations as part of server configuration. > So this subtask is to add such a private capability, with the remaining work of sorting out what public contract it will provide leftover as part of the parent issue. > It's not a problem to take a private capability and in the future make it public. And it's not a problem to change what a private capability exposes, i.e. in preparation for making it public. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11191) appclient module doesn't contain all deps required to start appclient config

by Jean-Francois Denise (Jira)

Jean-Francois Denise created WFLY-11191: ------------------------------------------- Summary: appclient module doesn't contain all deps required to start appclient config Key: WFLY-11191 URL: https://issues.jboss.org/browse/WFLY-11191 Project: WildFly Issue Type: Enhancement Components: Application Client Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise In a galleon context appclient could be provisioned as a separate artifact, the org.jboss.ass.appclient module should reference all the dependencies the bundled configuration is referencing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11181) XAResourceRecoveryServiceConfigurator adds a TX service dependency for non-transactional caches

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11181?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11181: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/11745 > XAResourceRecoveryServiceConfigurator adds a TX service dependency for non-transactional caches > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11181 > URL: https://issues.jboss.org/browse/WFLY-11181 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > I _think_ this is wrong... > XAResourceRecoveryServiceConfigurator is installed for all caches, not just ones with the ones with the component=transaction child resource. That's basically ok because its accept and get methods only do things if this.cache.get().getCacheConfiguration().transaction().recovery().enabled(). But, the problem is the service dependency on the XAResourceRecoveryRegistry service the transaction subsystem provides is always added, so even if is wouldn't be used the dependency is added. > I think WFLY-11167 will make it possible to correct this by 1) doing capability checking before adding the service dependency and 2) adding a capability requirement in TransactionResourceDefinition. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3149) [DMN Designer] Context top level data type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3149?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3149: ------------------------------------- [~manstis] solution sounds perfect to me, adding to my PR review todo list, thanks. > [DMN Designer] Context top level data type > ------------------------------------------ > > Key: DROOLS-3149 > URL: https://issues.jboss.org/browse/DROOLS-3149 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: DROOLS-3149.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-457) Jenkins Job for Complex Mesh

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-457: --------------------------------------------- Summary: Jenkins Job for Complex Mesh Key: SWSQE-457 URL: https://issues.jboss.org/browse/SWSQE-457 Project: Kiali QE Issue Type: QE Task Reporter: Guilherme Baufaker Rêgo Assignee: Guilherme Baufaker Rêgo -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3150) Race condition on clicks to enable inline editing into Scenario grid

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3150?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3150: --------------------------------- Tester: Klara Kufova > Race condition on clicks to enable inline editing into Scenario grid > -------------------------------------------------------------------- > > Key: DROOLS-3150 > URL: https://issues.jboss.org/browse/DROOLS-3150 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Minor > Attachments: 47010974-e8e16d80-d140-11e8-84dd-758c8253490f.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3150) Race condition on clicks to enable inline editing into Scenario grid

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3150?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3150: --------------------------------------- Originally reported by [~kkufova] > Race condition on clicks to enable inline editing into Scenario grid > -------------------------------------------------------------------- > > Key: DROOLS-3150 > URL: https://issues.jboss.org/browse/DROOLS-3150 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Minor > Attachments: 47010974-e8e16d80-d140-11e8-84dd-758c8253490f.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

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 October 2018