December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9608) WildFly Jandexification should explicitly ignore module-info.class

by Bob McWhirter (JIRA)

Bob McWhirter created WFLY-9608: ----------------------------------- Summary: WildFly Jandexification should explicitly ignore module-info.class Key: WFLY-9608 URL: https://issues.jboss.org/browse/WFLY-9608 Project: WildFly Issue Type: Enhancement Reporter: Bob McWhirter Assignee: Jason Greene Sometimes dependencies have module-info.class. When WildFly jandexes them, it burps a warning: 2017-12-11 15:04:20,124 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0003: Could not index class module-info.class at /content/microservice-session.war/WEB-INF/lib/asm-tree-6.0.jar: java.lang.IllegalStateException: Unknown tag! pos=3 poolCount = 12 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9607) Remove DigestAuthenticationMechanism code duplication between Wildfly, Undertow and Elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9607?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-9607: ---------------------------------------- The legacy implementation is to support integration with the PicketBox login modules due to the differences in the APIs to get the required credentials into the LoginModule - PicketBox has been deprecated so that code is already deprecated. The legacy security realms are now wrapped in Elytron components so the management interfaces use the Elytron implementation now and not the Undertow implementation. So at this stage we only have two implementations actively in use but one of them is for legacy integration already deprecated to be removed at a future point. > Remove DigestAuthenticationMechanism code duplication between Wildfly, Undertow and Elytron > ------------------------------------------------------------------------------------------- > > Key: WFLY-9607 > URL: https://issues.jboss.org/browse/WFLY-9607 > Project: WildFly > Issue Type: Enhancement > Components: Security > Affects Versions: 11.0.0.Final > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Darran Lofthouse > > Digest authentication mechanism is currently implemented in 3 places - in Wildfly undertow subsystem (legacy web authentication), Undertow itself (web console authentication) and Elytron (web authentication). > Any issue found in one of those scenarios is likely to affect others requiring fixing multiple codebases - ideally there should be a single implementation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2154) Design navigation between the DRG and DRD's

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2154?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2154: ------------------------------------- [~tirelli] [~manstis] I added a Requirement to the jira based on our discussions. > Design navigation between the DRG and DRD's > ------------------------------------------- > > Key: DROOLS-2154 > URL: https://issues.jboss.org/browse/DROOLS-2154 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > > *Use case description: * > As a business user (Citizen Developer…), I want to navigate between the DRG and the DRDs, and the content of each node, to model business decision logic. > *Requirements:* > * Diagram modeling must be absolutely consistent with Process Modeler: Process Designer and DMN editors should provide the same features, support the same interactions and appear visually similar in all aspects to one and other at "Level 1". Divergence may exist at "Level 2". > *Verification Conditions* > * The user of this feature is able to understand that the the DRDs are subsets of the whole DRG model/file. > * The user of this feature can seamlessly navigate between the diagrams and the content of the nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2154) Design navigation between the DRG and DRD's

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2154?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2154: -------------------------------- Description: *Use case description: * As a business user (Citizen Developer…), I want to navigate between the DRG and the DRDs, and the content of each node, to model business decision logic. *Requirements:* * Diagram modeling must be absolutely consistent with Process Modeler: Process Designer and DMN editors should provide the same features, support the same interactions and appear visually similar in all aspects to one and other at "Level 1". Divergence may exist at "Level 2". *Verification Conditions* * The user of this feature is able to understand that the the DRDs are subsets of the whole DRG model/file. * The user of this feature can seamlessly navigate between the diagrams and the content of the nodes. was: *Use case description: * As a business user (Citizen Developer…), I want to navigate between the DRG and the DRDs, and the content of each node, to model business decision logic. *Verification Conditions* * The user of this feature is able to understand that the the DRDs are subsets of the whole DRG model/file. * The user of this feature can seamlessly navigate between the diagrams and the content of the nodes. > Design navigation between the DRG and DRD's > ------------------------------------------- > > Key: DROOLS-2154 > URL: https://issues.jboss.org/browse/DROOLS-2154 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > > *Use case description: * > As a business user (Citizen Developer…), I want to navigate between the DRG and the DRDs, and the content of each node, to model business decision logic. > *Requirements:* > * Diagram modeling must be absolutely consistent with Process Modeler: Process Designer and DMN editors should provide the same features, support the same interactions and appear visually similar in all aspects to one and other at "Level 1". Divergence may exist at "Level 2". > *Verification Conditions* > * The user of this feature is able to understand that the the DRDs are subsets of the whole DRG model/file. > * The user of this feature can seamlessly navigate between the diagrams and the content of the nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9607) Remove DigestAuthenticationMechanism code duplication between Wildfly, Undertow and Elytron

by Bartosz Spyrko-Śmietanko (JIRA)

Bartosz Spyrko-Śmietanko created WFLY-9607: ---------------------------------------------- Summary: Remove DigestAuthenticationMechanism code duplication between Wildfly, Undertow and Elytron Key: WFLY-9607 URL: https://issues.jboss.org/browse/WFLY-9607 Project: WildFly Issue Type: Enhancement Components: Security Affects Versions: 11.0.0.Final Reporter: Bartosz Spyrko-Śmietanko Assignee: Darran Lofthouse Digest authentication mechanism is currently implemented in 3 places - in Wildfly undertow subsystem (legacy web authentication), Undertow itself (web console authentication) and Elytron (web authentication). Any issue found in one of those scenarios is likely to affect others requiring fixing multiple codebases - ideally there should be a single implementation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2173) Segment split can cause the resulting segments to be associated to the wrong path

by Anton Giertli (JIRA)

Anton Giertli created DROOLS-2173: ------------------------------------- Summary: Segment split can cause the resulting segments to be associated to the wrong path Key: DROOLS-2173 URL: https://issues.jboss.org/browse/DROOLS-2173 Project: Drools Issue Type: Bug Components: core engine Reporter: Anton Giertli Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9606) Upgrade ejb-client to 4.0.10.Final

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-9606?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-9606: ----------------------------------- There is no 4.0.10.Final. Following the chain of links leads me to EJBCLIENT-253 which has been fixed since 4.0.2.Final. Is there another JIRA that should be incorporated here? > Upgrade ejb-client to 4.0.10.Final > ---------------------------------- > > Key: WFLY-9606 > URL: https://issues.jboss.org/browse/WFLY-9606 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: Ivo Studensky > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9606) Upgrade ejb-client to 4.0.10.Final

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9606?page=com.atlassian.jira.plugin.... ] Ivo Studensky moved JBEAP-13955 to WFLY-9606: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9606 (was: JBEAP-13955) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB (was: EJB) Fix Version/s: (was: 7.1.1.GA) > Upgrade ejb-client to 4.0.10.Final > ---------------------------------- > > Key: WFLY-9606 > URL: https://issues.jboss.org/browse/WFLY-9606 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: Ivo Studensky > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9605) Upgrade JBoss Build Tools to 1.2.3.Final

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-9605?page=com.atlassian.jira.plugin.... ] David Lloyd moved WFCORE-3453 to WFLY-9605: ------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-9605 (was: WFCORE-3453) > Upgrade JBoss Build Tools to 1.2.3.Final > ---------------------------------------- > > Key: WFLY-9605 > URL: https://issues.jboss.org/browse/WFLY-9605 > Project: WildFly > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3396) Provide certificate authority integration

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3396?page=com.atlassian.jira.plugi... ] Farah Juma commented on WFCORE-3396: ------------------------------------ Analysis Document: https://developer.jboss.org/wiki/AnalysisDesign-IntegrationWithTheLetsEnc... > Provide certificate authority integration > ----------------------------------------- > > Key: WFCORE-3396 > URL: https://issues.jboss.org/browse/WFCORE-3396 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 4.0.0.Alpha2 > Reporter: Martin Choma > Assignee: Farah Juma > > Let's Encrypt provide API to fully automate (gain/renew) certificate retrieval using ACME protocol. Integrate this capability into wildfly. > This can simplify administrator work. No need to perform certification renewal routine tasks. > This is follow up on WFCORE-3305 and piece of bigger task "Simplify SSL configuration in wildfly". That said it is just "User experience" issue. Administrator still can work with Let's Encrypt by third party client and just reference wildfly to this certificate. > [1] Latest draft: https://tools.ietf.org/html/draft-ietf-acme-acme-08 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 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 December 2017