January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3452: -------------------------------- Attachment: 1atatimeB.png 1atatimeC.png 1atatimeD.png > Data type constraints: Date/Time > -------------------------------- > > Key: DROOLS-3452 > URL: https://issues.jboss.org/browse/DROOLS-3452 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: 1atatimeA.png, 1atatimeB.png, 1atatimeC.png, 1atatimeD.png, Screen Shot 2019-01-15 at 11.49.58 AM.png, enumeration.png, range.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 tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.) > 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.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5531) Messaging Failover Tests are failing intermittently

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-5531?page=com.atlassian.jira.plugin.... ] ehsavoie Hugonnet resolved WFLY-5531. ------------------------------------- Fix Version/s: 11.0.0.Final Resolution: Done > Messaging Failover Tests are failing intermittently > --------------------------------------------------- > > Key: WFLY-5531 > URL: https://issues.jboss.org/browse/WFLY-5531 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR2 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Labels: IntermittentFailure > Fix For: 11.0.0.Final > > > org.jboss.as.test.manualmode.messaging.ha.SharedStoreFailoverTestCase & org.jboss.as.test.manualmode.messaging.ha.ReplicatedFailoverTestCase are @Ignore-d as they fail intermittently on the CI. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3452: -------------------------------- Attachment: (was: enumeration.png) > Data type constraints: Date/Time > -------------------------------- > > Key: DROOLS-3452 > URL: https://issues.jboss.org/browse/DROOLS-3452 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: 1atatimeA.png, 1atatimeB.png, 1atatimeC.png, 1atatimeD.png, Screen Shot 2019-01-15 at 11.49.58 AM.png, range.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 tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.) > 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.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8643) RestEasy GZIP Compression Not Setting Content-Encoding

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-8643?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski resolved WFLY-8643. -------------------------------------- Resolution: Out of Date > RestEasy GZIP Compression Not Setting Content-Encoding > ------------------------------------------------------ > > Key: WFLY-8643 > URL: https://issues.jboss.org/browse/WFLY-8643 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 11.0.0.Alpha1 > Environment: Encountered the issue running in a Windows 7 environment > Reporter: Xavier Hammond > Assignee: Bartosz Baranowski > Priority: Major > > The Content-Encoding is not set to gzip when a RESTful service endpoint returns GZIP compressed data. > This only occurs when I deploy to the Wildfly 11 Alpha release. No issues with Wildfly 10 Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11593) Typo and ambiguity in 'integrated-jaspi' attribute of 'application-security-domain' element

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11593?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFLY-11593: ------------------------------------ Fix Version/s: 16.0.0.Beta1 > Typo and ambiguity in 'integrated-jaspi' attribute of 'application-security-domain' element > ------------------------------------------------------------------------------------------- > > Key: WFLY-11593 > URL: https://issues.jboss.org/browse/WFLY-11593 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Affects Versions: 15.0.0.Final, 15.0.1.Final > Reporter: Jan Stourac > Assignee: Jan Stourac > Priority: Minor > Fix For: 16.0.0.Beta1 > > > There is a typo and a little bit of ambiguity in the current description of the '{{/subsystem=undertow/application-security-domain=foo\[integrated-jaspi\]}}' attribute: > {quote} > Should integrated JASPI be used or allow AsHoc identity creation. > {quote} > proposed change: > {quote} > Whether integrated JASPI should be used. If this is disabled, ad hoc identity will be created instead. > {quote} > And [here is full attribute description|https://github.com/wildfly/wildfly/blob/7172799ce7bda7f82b944...] in related XSD file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3452: -------------------------------- Attachment: 1atatimeA.png > Data type constraints: Date/Time > -------------------------------- > > Key: DROOLS-3452 > URL: https://issues.jboss.org/browse/DROOLS-3452 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: 1atatimeA.png, Screen Shot 2019-01-15 at 11.49.58 AM.png, enumeration.png, range.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 tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.) > 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.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3452: -------------------------------- Attachment: (was: range-cal2tip.png) > Data type constraints: Date/Time > -------------------------------- > > Key: DROOLS-3452 > URL: https://issues.jboss.org/browse/DROOLS-3452 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: 1atatimeA.png, Screen Shot 2019-01-15 at 11.49.58 AM.png, enumeration.png, range.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 tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.) > 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.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4271) Exclude Servlet 3.1 transitive dependency from JACC API dependency

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4271?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4271: ------------------------------------- Fix Version/s: 8.0.0.Beta3 > Exclude Servlet 3.1 transitive dependency from JACC API dependency > ------------------------------------------------------------------ > > Key: WFCORE-4271 > URL: https://issues.jboss.org/browse/WFCORE-4271 > Project: WildFly Core > Issue Type: Task > Components: Security > Affects Versions: 8.0.0.Beta2 > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > Fix For: 8.0.0.Beta3 > > > As a follow-up to WFLY-11573 we could exclude transitive Servlet 3.1 dependency in wildfly-core project from jboss-jacc-api_1.5_spec dependency. > While jboss-jacc-api_1.5_spec depends on jboss-servlet-api-3.1-spec and we are trying to remove the depedency without providing another one, this still should be correct: > 1) testsuite passes with the exclusion in place, ie. the classes from Servlet 3.1 aren't used here > 2) both feature and galleon pack excludes it too > https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/pom... > https://github.com/wildfly/wildfly-core/blob/master/core-galleon-pack/pom... > 3) the module contains it as optional dependency > https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/src... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3452) Data type constraints: Date/Time

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3452?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3452: -------------------------------- Attachment: (was: range-cal1.png) > Data type constraints: Date/Time > -------------------------------- > > Key: DROOLS-3452 > URL: https://issues.jboss.org/browse/DROOLS-3452 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: 1atatimeA.png, Screen Shot 2019-01-15 at 11.49.58 AM.png, enumeration.png, range.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 tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.) > 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.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4271) Exclude Servlet 3.1 transitive dependency from JACC API dependency

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4271?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-4271: ---------------------------------------- Assignee: Jan Blizňák (was: Darran Lofthouse) > Exclude Servlet 3.1 transitive dependency from JACC API dependency > ------------------------------------------------------------------ > > Key: WFCORE-4271 > URL: https://issues.jboss.org/browse/WFCORE-4271 > Project: WildFly Core > Issue Type: Task > Components: Security > Affects Versions: 8.0.0.Beta2 > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > Fix For: 8.0.0.Beta3 > > > As a follow-up to WFLY-11573 we could exclude transitive Servlet 3.1 dependency in wildfly-core project from jboss-jacc-api_1.5_spec dependency. > While jboss-jacc-api_1.5_spec depends on jboss-servlet-api-3.1-spec and we are trying to remove the depedency without providing another one, this still should be correct: > 1) testsuite passes with the exclusion in place, ie. the classes from Servlet 3.1 aren't used here > 2) both feature and galleon pack excludes it too > https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/pom... > https://github.com/wildfly/wildfly-core/blob/master/core-galleon-pack/pom... > 3) the module contains it as optional dependency > https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/src... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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 January 2019