September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4123) The DomainCommandBuilder does not add modular JDK arguments to the host controler

by James Perkins (JIRA)

James Perkins created WFCORE-4123: ------------------------------------- Summary: The DomainCommandBuilder does not add modular JDK arguments to the host controler Key: WFCORE-4123 URL: https://issues.jboss.org/browse/WFCORE-4123 Project: WildFly Core Issue Type: Bug Components: Launcher Reporter: James Perkins Assignee: James Perkins Currently the launchers {{DomainCommandBuilder}} adds modular JDK arguments to the process controller, but not the host controller. This means when using the default JVM arguments the host controller won't start. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3000) Enhance data type restrictions UX (decision tables & DT dialog)

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3000: -------------------------------- Description: *Background* Persona: Business analyst or Rules practitioner Use Cases: * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... Functional considerations/ pre conditions: * Consider interaction in light of Property panel and consistency. * Underscore the notion of one-off constraints. Verification conditions: * Scrum team and PO review. was: *Background* Persona: Business analyst or Rules practitioner Use Cases: * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... Functional considerations/ pre conditions: * Consider interaction in light of Property panel and consistency. * Underscore the notice of one-off constraints. Verification conditions: * Scrum team and PO review. > Enhance data type restrictions UX (decision tables & DT dialog) > --------------------------------------------------------------- > > Key: DROOLS-3000 > URL: https://issues.jboss.org/browse/DROOLS-3000 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 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 define data type restrictions (one-off instances) from a decision table . > * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > 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] (WFCORE-4122) Modular JDK arguments should not be added if the user overrides the Java options

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4122?page=com.atlassian.jira.plugi... ] James Perkins closed WFCORE-4122. --------------------------------- Resolution: Duplicate Issue This will get fixed in WFCORE-4121 > Modular JDK arguments should not be added if the user overrides the Java options > -------------------------------------------------------------------------------- > > Key: WFCORE-4122 > URL: https://issues.jboss.org/browse/WFCORE-4122 > Project: WildFly Core > Issue Type: Bug > Components: Launcher > Reporter: James Perkins > Assignee: James Perkins > Labels: Java11 > > Currently in the command builder API's the modular JDK arguments are always added to the list of arguments. This should just be added to the default JVM arguments. That could result in arguments being added twice if users override the options. The user should be able to fully override the Java options. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11057) Singleton MDB barrier service starts prematurely

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-11057: ----------------------------------- Summary: Singleton MDB barrier service starts prematurely Key: WFLY-11057 URL: https://issues.jboss.org/browse/WFLY-11057 Project: WildFly Issue Type: Bug Components: Clustering, EJB Affects Versions: 14.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Currently, this service starts actively. However, it only needs to start when demanded by a deployed @Clustered @MessageDriven EJB. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11056) Singleton MDB barrier service starts prematurely

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-11056: ----------------------------------- Summary: Singleton MDB barrier service starts prematurely Key: WFLY-11056 URL: https://issues.jboss.org/browse/WFLY-11056 Project: WildFly Issue Type: Bug Components: Clustering, EJB Affects Versions: 14.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Currently, this service starts actively. However, it only needs to start when demanded by a deployed @Clustered @MessageDriven EJB. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1674) MechanismDatabase ECDHE_PSK ciphers use PSK authentication, not ECDHE

by David Lloyd (JIRA)

David Lloyd created ELY-1674: -------------------------------- Summary: MechanismDatabase ECDHE_PSK ciphers use PSK authentication, not ECDHE Key: ELY-1674 URL: https://issues.jboss.org/browse/ELY-1674 Project: WildFly Elytron Issue Type: Bug Components: SSL Reporter: David Lloyd Assignee: David Lloyd AFAICT the ECHDE_PSK suites use PSK authentication, not ECDHE key authentication. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1673) Draft ciphers in mechanism database

by David Lloyd (JIRA)

David Lloyd created ELY-1673: -------------------------------- Summary: Draft ciphers in mechanism database Key: ELY-1673 URL: https://issues.jboss.org/browse/ELY-1673 Project: WildFly Elytron Issue Type: Bug Components: SSL Reporter: David Lloyd Assignee: David Lloyd We should exclude the list of draft ciphers from the mechanism database. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1672) MechanismDatabase should not use AEAD to describe digest (PRF)

by David Lloyd (JIRA)

David Lloyd created ELY-1672: -------------------------------- Summary: MechanismDatabase should not use AEAD to describe digest (PRF) Key: ELY-1672 URL: https://issues.jboss.org/browse/ELY-1672 Project: WildFly Elytron Issue Type: Bug Components: SSL Reporter: David Lloyd Assignee: David Lloyd AEAD is not a digest (PRF) function, it's a description of a message authentication strategy. We should only use the actual digest names in the mechanism database. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3000) Enhance data type restrictions UX (decision tables & DT dialog)

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3000: -------------------------------- Description: *Background* Persona: Business analyst or Rules practitioner Use Cases: * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... Functional considerations/ pre conditions: * Consider interaction in light of Property panel and consistency. * Underscore the notice of one-off constraints. Verification conditions: * Scrum team and PO review. was: *Background* Persona: Business analyst or Rules practitioner Use Cases: * From the DMN canvas view - as a user I want to define data type restrictions inline from a decision table (pop-over). Functional considerations/ pre conditions: * Required elements could be space intensive. * If using the pop-over: Can implement a responsive HTML that looks good horizontally in the Data Type dialog.. and vertically in the popover. Although even if laid out horizontally in the DT dialog a big enum def will take up a lot of space text enums are ok, a textbox is good enough but a enum for a date/time field with >1 entry will start eating lots of room Verification conditions: * Scrum team and PO review. > Enhance data type restrictions UX (decision tables & DT dialog) > --------------------------------------------------------------- > > Key: DROOLS-3000 > URL: https://issues.jboss.org/browse/DROOLS-3000 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 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 define data type restrictions (one-off instances) from a decision table . > * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E... > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notice of one-off constraints. > 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] (JGRP-2295) Add local Operation System DNS resolver implementation

by Rob Cernich (JIRA)

[ https://issues.jboss.org/browse/JGRP-2295?page=com.atlassian.jira.plugin.... ] Rob Cernich commented on JGRP-2295: ----------------------------------- Full classname? How about having a simple switch for using SRV or A recoreds, where the A impl uses the unadulterated query with InetAddress.getAllByName() and SRV impl uses DnsContext and the suffix? This probably makes the most sense, because you need to use SRV if you've got a normal service (although you can use _endpoints prefix on the query) and A if you've got a headless service (clusterIP=None). WDYT? > Add local Operation System DNS resolver implementation > ------------------------------------------------------ > > Key: JGRP-2295 > URL: https://issues.jboss.org/browse/JGRP-2295 > Project: JGroups > Issue Type: Feature Request > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > The {{DefaultDNSResolver}} queries the DNS server and extracts values it returned. There's however another approach - query the local OS DNS resolver. This approach has some advantages because it takes both {{/etc/hosts}} as well as {{/etc/resolv.conf}} files under consideration. We should provide an {{OSDNSResolver}} implementation that would do it. -- 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