August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4448) [Guided Rule] Local Date constraint is lost

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4448?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4448: -------------------------------- Description: User is unable to create guided rule with constraint over {{LocalDate}} field. h2. Acceptance criteria - deferred to DROOLS-4461 Save and reopen all these column types - Free form DRL, constraint - Simple condition column, literal value constraint - BRL condition column, literal value constrain - BRL condition column, template key constraint - Simple action column - BRL action column, literal value - BRL action column, template key was: User is unable to create guided rule with constraint over {{LocalDate}} field. h2. Acceptance criteria Save and reopen all these column types - Free form DRL, constraint - Simple condition column, literal value constraint - BRL condition column, literal value constrain - BRL condition column, template key constraint - Simple action column - BRL action column, literal value - BRL action column, template key > [Guided Rule] Local Date constraint is lost > ------------------------------------------- > > Key: DROOLS-4448 > URL: https://issues.jboss.org/browse/DROOLS-4448 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > User is unable to create guided rule with constraint over {{LocalDate}} field. > h2. Acceptance criteria - deferred to DROOLS-4461 > Save and reopen all these column types > - Free form DRL, constraint > - Simple condition column, literal value constraint > - BRL condition column, literal value constrain > - BRL condition column, template key constraint > - Simple action column > - BRL action column, literal value > - BRL action column, template key -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4448) [Guided Rule] Local Date constraint is lost

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4448?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4448: -------------------------------- Description: User is unable to create guided rule with constraint over {{LocalDate}} field. h2. Acceptance criteria - deferred to DROOLS-4461 -Save and reopen all these column types - Free form DRL, constraint - Simple condition column, literal value constraint - BRL condition column, literal value constrain - BRL condition column, template key constraint - Simple action column - BRL action column, literal value - BRL action column, template key- was: User is unable to create guided rule with constraint over {{LocalDate}} field. h2. Acceptance criteria - deferred to DROOLS-4461 Save and reopen all these column types - Free form DRL, constraint - Simple condition column, literal value constraint - BRL condition column, literal value constrain - BRL condition column, template key constraint - Simple action column - BRL action column, literal value - BRL action column, template key > [Guided Rule] Local Date constraint is lost > ------------------------------------------- > > Key: DROOLS-4448 > URL: https://issues.jboss.org/browse/DROOLS-4448 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > User is unable to create guided rule with constraint over {{LocalDate}} field. > h2. Acceptance criteria - deferred to DROOLS-4461 > -Save and reopen all these column types > - Free form DRL, constraint > - Simple condition column, literal value constraint > - BRL condition column, literal value constrain > - BRL condition column, template key constraint > - Simple action column > - BRL action column, literal value > - BRL action column, template key- -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4448) [Guided Rule] Local Date constraint is lost

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4448?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4448: -------------------------------- Description: User is unable to create guided rule with constraint over {{LocalDate}} field. h2. Acceptance criteria - deferred to DROOLS-4461 Save and reopen all these column types - Free form DRL, constraint - Simple condition column, literal value constraint - BRL condition column, literal value constrain - BRL condition column, template key constraint - Simple action column - BRL action column, literal value - BRL action column, template key was: User is unable to create guided rule with constraint over {{LocalDate}} field. h2. Acceptance criteria - deferred to DROOLS-4461 -Save and reopen all these column types - Free form DRL, constraint - Simple condition column, literal value constraint - BRL condition column, literal value constrain - BRL condition column, template key constraint - Simple action column - BRL action column, literal value - BRL action column, template key- > [Guided Rule] Local Date constraint is lost > ------------------------------------------- > > Key: DROOLS-4448 > URL: https://issues.jboss.org/browse/DROOLS-4448 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > User is unable to create guided rule with constraint over {{LocalDate}} field. > h2. Acceptance criteria - deferred to DROOLS-4461 > Save and reopen all these column types > - Free form DRL, constraint > - Simple condition column, literal value constraint > - BRL condition column, literal value constrain > - BRL condition column, template key constraint > - Simple action column > - BRL action column, literal value > - BRL action column, template key -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4407) [DMN Designer] Search feature - Highlight the current result with colors that follow the PF standard

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4407?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4407: -------------------------------- Attachment: search-edit.webm > [DMN Designer] Search feature - Highlight the current result with colors that follow the PF standard > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-4407 > URL: https://issues.jboss.org/browse/DROOLS-4407 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: search-context-2.webm, search-context.webm, search-edit.webm > > > All places (_DMN Boxed expressions editor, Guided Decision Tables editor, Guided Decision Tables graph editor, and DMN Data Types tab_) that use the search component must follow the PatternFly standard colors to highlight the cells. > Apply the infrastructure code from https://issues.jboss.org/browse/DROOLS-4406 to highlight the grid cells, and pure CSS to highlight the Data Types. > BG: #F9D67A > Stroke: #F5C12E > ⚠️ Notice: > The DMN graph stay as is for now. Since nodes can have their own colors, the current highlight is enough. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4461) Use date picker for LocalDate

by Toni Rikkola (Jira)

Toni Rikkola created DROOLS-4461: ------------------------------------ Summary: Use date picker for LocalDate Key: DROOLS-4461 URL: https://issues.jboss.org/browse/DROOLS-4461 Project: Drools Issue Type: Enhancement Components: Guided Decision Table Editor, Guided Rule Editor, Test Scenarios Editor Reporter: Toni Rikkola Assignee: Toni Rikkola We should use the date picker for LocalDate like we do for Date. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4461) Use date picker for LocalDate

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-4461?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-4461: --------------------------------- Labels: drools-tools (was: ) > Use date picker for LocalDate > ----------------------------- > > Key: DROOLS-4461 > URL: https://issues.jboss.org/browse/DROOLS-4461 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor, Guided Rule Editor, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > We should use the date picker for LocalDate like we do for Date. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4116) [DMN Designer] Documentation tab (7.5)

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4116?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4116: -------------------------------- Fix Version/s: 7.26.0.Final > [DMN Designer] Documentation tab (7.5) > -------------------------------------- > > Key: DROOLS-4116 > URL: https://issues.jboss.org/browse/DROOLS-4116 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Fix For: 7.26.0.Final > > > This is an umbrella for all JIRAs (target to 7.5) related to the *Documentation tab* feature. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12413) IllegalStateException when bad metrics scope requested

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12413?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12413: ----------------------------------------- Problem is in MetricsRequestHandler: {code} MetricRegistry.Type scope = getScopeFromPath(responder, scopePath); if (scope == null) { responder.respondWith(404, "Scope " + scopePath + " not found", Collections.emptyMap()); return; } {code} Problem is that 'getScopeFromPath(...) call also calls 'responder.respondWith(404...)' when the scopePath is wrong. Needs a smallrye bug; WildFly can probably work around it by having the Responder lambda check if it's been invoked and ignore the second request. > IllegalStateException when bad metrics scope requested > ------------------------------------------------------ > > Key: WFLY-12413 > URL: https://issues.jboss.org/browse/WFLY-12413 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Jan Stourac > Assignee: Jeff Mesnil > Priority: Major > > With WildFly build from master branch (commit {{0e13252d9e7a6c82e6e170bac1a2faf727287c1d}}), I can see following exception in log: > {code} > 16:38:57,964 ERROR [io.undertow.request] (management I/O-1) UT005071: Undertow request failed HttpServerExchange{ GET /metrics/test}: java.lang.IllegalStateException: UT000002: The response has already been started > at io.undertow.server.HttpServerExchange.setStatusCode(HttpServerExchange.java:1406) > at org.wildfly.extension.microprofile.metrics.MetricsContextService$1.lambda$handleRequest$0(MetricsContextService.java:85) > at io.smallrye.metrics.MetricsRequestHandler.handleRequest(MetricsRequestHandler.java:142) > at io.smallrye.metrics.MetricsRequestHandler.handleRequest(MetricsRequestHandler.java:73) > at org.wildfly.extension.microprofile.metrics.MetricsContextService$1.handleRequest(MetricsContextService.java:84) > at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51) > at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35) > at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91) > at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211) > at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92) > at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78) > at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49) > at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57) > at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75) > at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:664) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376) > at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255) > at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136) > at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:162) > at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:100) > at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:57) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291) > at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:132) > at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:479) > {code} > This exception is caused by following request: > {code} > $ curl -v http://localhost:9990/metrics/test > * Trying ::1:9990... > * TCP_NODELAY set > * connect to ::1 port 9990 failed: Connection refused > * Trying 127.0.0.1:9990... > * TCP_NODELAY set > * Connected to localhost (127.0.0.1) port 9990 (#0) > > GET /metrics/test HTTP/1.1 > > Host: localhost:9990 > > User-Agent: curl/7.65.3 > > Accept: */* > > > * Mark bundle as not supporting multiuse > < HTTP/1.1 404 Not Found > < Connection: keep-alive > < Content-Length: 25 > < Date: Thu, 22 Aug 2019 14:57:20 GMT > < > * Connection #0 to host localhost left intact > Bad scope requested: test > The 404 Not Found HTTP response code is expected and also 'Bad scope request: test' in this case. Although, I think that mentioned IllegalStateException should be avoided. Also, this exception is not thrown in WildFly 17.0.1. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12417) Clean out subsystem compatibility tests with EAP versions before 6.4

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12417?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-12417: --------------------------------------- Assignee: Brian Stansberry (was: Matěj Novotný) > Clean out subsystem compatibility tests with EAP versions before 6.4 > -------------------------------------------------------------------- > > Key: WFLY-12417 > URL: https://issues.jboss.org/browse/WFLY-12417 > Project: WildFly > Issue Type: Task > Components: CDI / Weld, EE, EJB, JCA, JMS, Web Services > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12417) Clean out subsystem compatibility tests with EAP versions before 6.4

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12417: --------------------------------------- Summary: Clean out subsystem compatibility tests with EAP versions before 6.4 Key: WFLY-12417 URL: https://issues.jboss.org/browse/WFLY-12417 Project: WildFly Issue Type: Task Components: CDI / Weld, EE, EJB, JCA, JMS, Web Services Reporter: Brian Stansberry Assignee: Matěj Novotný -- This message was sent by Atlassian Jira (v7.12.1#712002)

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