October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11166) Create capabilities for TransactionManager, UserTransaction and TransactionSynchronizationRegistry

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/WFLY-11166?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFLY-11166: ------------------------------------ bq. David Lloyd So all the existing Service injection should be ripped out? Yes. I didn't rip it all out initially because in addition to the (useless) injection of the relevant values, the service dependencies add an ordering facet which would entail a separate stage of testing. That, combined with my unwillingness to move it all to cap/req in one giant refactor (and uncertainty as to how to handle having a global default with the option of a local override), led me to do a minimal refactor which included leaving the compatibility-only services intact and, in some cases, still in use. +1 to your points though. > Create capabilities for TransactionManager, UserTransaction and TransactionSynchronizationRegistry > -------------------------------------------------------------------------------------------------- > > Key: WFLY-11166 > URL: https://issues.jboss.org/browse/WFLY-11166 > Project: WildFly > Issue Type: Sub-task > Components: Management, Transactions > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > See https://issues.jboss.org/browse/WFLY-9587?focusedCommentId=13647549&page=... in the parent issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11203) Update Agroal to 1.3

by Luis Barreiro (Jira)

Luis Barreiro created WFLY-11203: ------------------------------------ Summary: Update Agroal to 1.3 Key: WFLY-11203 URL: https://issues.jboss.org/browse/WFLY-11203 Project: WildFly Issue Type: Component Upgrade Components: Agroal Reporter: Luis Barreiro Assignee: Luis Barreiro -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11166) Create capabilities for TransactionManager, UserTransaction and TransactionSynchronizationRegistry

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11166?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-11166: ----------------------------------------- [~dmlloyd] So all the existing Service injection should be ripped out? That's getting to be a bit beyond what I'm up for doing. But OTOH perhaps I should just "Won't Fix" this and instead add capability requirements for the existing org.wildfly.transactions. There were really two things that sparked my interest in this: 1) Subsystems depending on having a local provider but the management model (and hence galleon too) not having a clue. So you could remove the tx subsystem in admin-only mode and it would be accepted, but then you start in normal mode and boom. So just requiring org.wildfly.transactions or perhaps a more precisely named org.wildfly.transactions.local-provider fixes that. 2) Avoiding classloading dependencies on org.jboss.as.transactions, which itself has a lot transitive dependencies, so possible source of big ball of mud. But investigation since then shows there's very little benefit from not depending on org.jboss.as.transactions (at least not if your feature really requires a local provider). The key thing is to avoid unnecessary hard dependency chains that propagate out from org.jboss.as.transactions, e.g. WFLY-11195. > Create capabilities for TransactionManager, UserTransaction and TransactionSynchronizationRegistry > -------------------------------------------------------------------------------------------------- > > Key: WFLY-11166 > URL: https://issues.jboss.org/browse/WFLY-11166 > Project: WildFly > Issue Type: Sub-task > Components: Management, Transactions > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > See https://issues.jboss.org/browse/WFLY-9587?focusedCommentId=13647549&page=... in the parent issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11166) Create capabilities for TransactionManager, UserTransaction and TransactionSynchronizationRegistry

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/WFLY-11166?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFLY-11166: ------------------------------------ I'd say just "org.wildfly.transactions.local-provider". We don't need capabilities for the individual APIs at all; you can get the TM just by calling {{ContextTransactionManager.getInstance()}}, and likewise for the UT & TSR. > Create capabilities for TransactionManager, UserTransaction and TransactionSynchronizationRegistry > -------------------------------------------------------------------------------------------------- > > Key: WFLY-11166 > URL: https://issues.jboss.org/browse/WFLY-11166 > Project: WildFly > Issue Type: Sub-task > Components: Management, Transactions > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > See https://issues.jboss.org/browse/WFLY-9587?focusedCommentId=13647549&page=... in the parent issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11166) Create capabilities for TransactionManager, UserTransaction and TransactionSynchronizationRegistry

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11166?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-11166: ----------------------------------------- [~dmlloyd] Is this more of a capability naming issue then? For example, not static capability "org.wildfly.transactions.transaction-manager" but rather a dynamic one "org.wildfly.transactions.local-provider.transaction-manager" and then the dynamic part for now is always "narayana"? That's a mouthful of a capability name, but oh well. :) Re: "if no subsystem provides the capability, the system may still be usable", that's an issue for the consumer of the capability. If it's not required they can check for the capability presence and proceed without. > Create capabilities for TransactionManager, UserTransaction and TransactionSynchronizationRegistry > -------------------------------------------------------------------------------------------------- > > Key: WFLY-11166 > URL: https://issues.jboss.org/browse/WFLY-11166 > Project: WildFly > Issue Type: Sub-task > Components: Management, Transactions > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > See https://issues.jboss.org/browse/WFLY-9587?focusedCommentId=13647549&page=... in the parent issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11202) Default ResourceBundle fails to load

by Andrew Schmidt (Jira)

Andrew Schmidt created WFLY-11202: ------------------------------------- Summary: Default ResourceBundle fails to load Key: WFLY-11202 URL: https://issues.jboss.org/browse/WFLY-11202 Project: WildFly Issue Type: Bug Affects Versions: 14.0.1.Final Reporter: Andrew Schmidt Assignee: Jason Greene Attachments: resourcebundle.zip Wildfly 14 no longer loads the default message bundle when a locale is specified and the specific locale has no properties file. For example, in the attached project, I have a messages.properties file, Wildfly 13 and previous releases would simply load the messages.properties if there is no messages_en.properties. But in wildfly 14 this is no longer the case (it appears it provides a different resourcebundle) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4165) The SuspendController is not exposed via a capability

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFCORE-4165?page=com.atlassian.jira.plugi... ] Yeray Borges reassigned WFCORE-4165: ------------------------------------ Assignee: Yeray Borges (was: Jeff Mesnil) > The SuspendController is not exposed via a capability > ----------------------------------------------------- > > Key: WFCORE-4165 > URL: https://issues.jboss.org/browse/WFCORE-4165 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > > Various services in the appserver depend on the SuspendController via SuspendController.SERVICE_NAME. This should be exposed via a capability. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3154) Minor UI improvements/bugfixes for Scenario

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3154?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3154: ------------------------------------- [~Rikkola] I noticed that the table/grid doesn't span the full width of the canvas area by default, just wondering if it could? > Minor UI improvements/bugfixes for Scenario > ------------------------------------------- > > Key: DROOLS-3154 > URL: https://issues.jboss.org/browse/DROOLS-3154 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Toni Rikkola > Priority: Critical > Labels: UX-CSS > > This item contains a list of general UI bugs to be fixed: > - Use grey borders for all the grid and not only for the header > - Add some padding to the cells of the grid > - Add some padding to right panel the tab titles > - Remove scrolling bar from right panel > - Review expression editor component HTML/CSS (paddings, indents, etc) > - Review right panel padding (now it is hardcoded) > - Use text area inputs instead of text box for inline editing > - Reduce the width of Index column -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3112) FEEL Compiler: modularize FEELImpl compiler/interpreter vs. DMNFEELHelper

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3112?page=com.atlassian.jira.plugi... ] Edoardo Vacchi commented on DROOLS-3112: ---------------------------------------- waiting for DROOLS-3088 to be merged for merging this > FEEL Compiler: modularize FEELImpl compiler/interpreter vs. DMNFEELHelper > -------------------------------------------------------------------------- > > Key: DROOLS-3112 > URL: https://issues.jboss.org/browse/DROOLS-3112 > Project: Drools > Issue Type: Enhancement > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Code in FEELImpl could be reused in the DMNFEELHelper, but it cannot be shared, because FEELImpl exposes an interface to evaluate expressions, while DMNFEELHelper needs access to the compiler backend. > Solution: separate the compilation pipeline and the interpreter pipeline from the public FEEL interface to promote code reuse. In particular, CompilerBytecodeLoader can be probably split between some kind of CompiledUnit+CompiledUnaryTest impls that provide methods to retrieve Java source code and/or JVM bytecode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1696) Dead code in ElytronXmlParser - PrivateKeyKeyStoreEntryCredentialFactory

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1696?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1696: ---------------------------------- Fix Version/s: 1.7.0.CR4 > Dead code in ElytronXmlParser - PrivateKeyKeyStoreEntryCredentialFactory > ------------------------------------------------------------------------ > > Key: ELY-1696 > URL: https://issues.jboss.org/browse/ELY-1696 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Martin Mazanek > Assignee: Martin Mazanek > Priority: Major > Fix For: 1.7.0.CR4 > > > There is some dead code left in ElytronXmlParser.java after ELY-1639 > https://github.com/wildfly-security/wildfly-elytron/commit/bd1c6742828d9d... -- 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