May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2771) Wildfly Management Console should log bound ports

by Jason Tedor (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2771?page=com.atlassian.jira.plugi... ] Jason Tedor updated WFCORE-2771: -------------------------------- Description: When binding Wildfly Management Console to an ephemeral port (i.e., by specifying port 0), Wildfly states that the management console: {code} 23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled 23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled {code} This isn't right. For example, using {{lsof}} I can see that Wildfly bound to an ephemeral port. After starting Wildfly with {{-Djboss.management.http.port=0}}: {code} $ lsof -p `jps | grep jboss-modules.jar | awk '{print $1}'` -P -n | grep TCP java 59501 jason 379u IPv4 0xd038b817c1abd6a5 0t0 TCP 127.0.0.1:8080 (LISTEN) java 59501 jason 387u IPv4 0xd038b817acfc6a85 0t0 TCP 127.0.0.1:65238 (LISTEN) java 59501 jason 390u IPv4 0xd038b817b86956a5 0t0 TCP 127.0.0.1:8443 (LISTEN) $ curl -v -XGET localhost:65238 Note: Unnecessary use of -X or --request, GET is already inferred. * Rebuilt URL to: localhost:65238/ * Trying ::1... * TCP_NODELAY set * Connection failed * connect to ::1 port 65238 failed: Connection refused * Trying 127.0.0.1... * TCP_NODELAY set * Connected to localhost (127.0.0.1) port 65238 (#0) > GET / HTTP/1.1 > Host: localhost:65238 > User-Agent: curl/7.51.0 > Accept: */* > < HTTP/1.1 301 Moved Permanently < Connection: keep-alive < Location: http://localhost:65238/console/index.html < Content-Length: 0 < Date: Sun, 07 May 2017 03:25:04 GMT < * Curl_http_done: called premature == 0 * Connection #0 to host localhost left intact {code} showing that Wildfly is indeed listening and giving the usual redirect to the Console index. Instead, Wildfly should log the ephemeral port that it actually bound to: {code} 23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:65301/management 23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:65301 {code} was: When binding Wildfly Management Console to an ephemeral port (i.e., by specifying port 0), Wildfly states that the management console: {{23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled 23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled}} This isn't right. For example, using {{lsof}} I can see that Wildfly bound to an ephemeral port. After starting Wildfly with {{-Djboss.management.http.port=0}}: {code} $ lsof -p `jps | grep jboss-modules.jar | awk '{print $1}'` -P -n | grep TCP java 59501 jason 379u IPv4 0xd038b817c1abd6a5 0t0 TCP 127.0.0.1:8080 (LISTEN) java 59501 jason 387u IPv4 0xd038b817acfc6a85 0t0 TCP 127.0.0.1:65238 (LISTEN) java 59501 jason 390u IPv4 0xd038b817b86956a5 0t0 TCP 127.0.0.1:8443 (LISTEN) $ curl -v -XGET localhost:65238 Note: Unnecessary use of -X or --request, GET is already inferred. * Rebuilt URL to: localhost:65238/ * Trying ::1... * TCP_NODELAY set * Connection failed * connect to ::1 port 65238 failed: Connection refused * Trying 127.0.0.1... * TCP_NODELAY set * Connected to localhost (127.0.0.1) port 65238 (#0) > GET / HTTP/1.1 > Host: localhost:65238 > User-Agent: curl/7.51.0 > Accept: */* > < HTTP/1.1 301 Moved Permanently < Connection: keep-alive < Location: http://localhost:65238/console/index.html < Content-Length: 0 < Date: Sun, 07 May 2017 03:25:04 GMT < * Curl_http_done: called premature == 0 * Connection #0 to host localhost left intact {code} showing that Wildfly is indeed listening and giving the usual redirect to the Console index. Instead, Wildfly should log the ephemeral port that it actually bound to: {{23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:65301/management 23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:65301}} > Wildfly Management Console should log bound ports > ------------------------------------------------- > > Key: WFCORE-2771 > URL: https://issues.jboss.org/browse/WFCORE-2771 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Jason Tedor > Assignee: Jason Greene > > When binding Wildfly Management Console to an ephemeral port (i.e., by specifying port 0), Wildfly states that the management console: > {code} > 23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled > 23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled > {code} > This isn't right. For example, using {{lsof}} I can see that Wildfly bound to an ephemeral port. After starting Wildfly with {{-Djboss.management.http.port=0}}: > {code} > $ lsof -p `jps | grep jboss-modules.jar | awk '{print $1}'` -P -n | grep TCP > java 59501 jason 379u IPv4 0xd038b817c1abd6a5 0t0 TCP 127.0.0.1:8080 (LISTEN) > java 59501 jason 387u IPv4 0xd038b817acfc6a85 0t0 TCP 127.0.0.1:65238 (LISTEN) > java 59501 jason 390u IPv4 0xd038b817b86956a5 0t0 TCP 127.0.0.1:8443 (LISTEN) > $ curl -v -XGET localhost:65238 > Note: Unnecessary use of -X or --request, GET is already inferred. > * Rebuilt URL to: localhost:65238/ > * Trying ::1... > * TCP_NODELAY set > * Connection failed > * connect to ::1 port 65238 failed: Connection refused > * Trying 127.0.0.1... > * TCP_NODELAY set > * Connected to localhost (127.0.0.1) port 65238 (#0) > > GET / HTTP/1.1 > > Host: localhost:65238 > > User-Agent: curl/7.51.0 > > Accept: */* > > > < HTTP/1.1 301 Moved Permanently > < Connection: keep-alive > < Location: http://localhost:65238/console/index.html > < Content-Length: 0 > < Date: Sun, 07 May 2017 03:25:04 GMT > < > * Curl_http_done: called premature == 0 > * Connection #0 to host localhost left intact > {code} > showing that Wildfly is indeed listening and giving the usual redirect to the Console index. > Instead, Wildfly should log the ephemeral port that it actually bound to: > {code} > 23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:65301/management > 23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:65301 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2771) Wildfly Management Console should log bound ports

by Jason Tedor (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2771?page=com.atlassian.jira.plugi... ] Jason Tedor updated WFCORE-2771: -------------------------------- Description: When binding Wildfly Management Console to an ephemeral port (i.e., by specifying port 0), Wildfly states that the management console: {{23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled 23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled}} This isn't right. For example, using {{lsof}} I can see that Wildfly bound to an ephemeral port. After starting Wildfly with {{-Djboss.management.http.port=0}}: {code} $ lsof -p `jps | grep jboss-modules.jar | awk '{print $1}'` -P -n | grep TCP java 59501 jason 379u IPv4 0xd038b817c1abd6a5 0t0 TCP 127.0.0.1:8080 (LISTEN) java 59501 jason 387u IPv4 0xd038b817acfc6a85 0t0 TCP 127.0.0.1:65238 (LISTEN) java 59501 jason 390u IPv4 0xd038b817b86956a5 0t0 TCP 127.0.0.1:8443 (LISTEN) $ curl -v -XGET localhost:65238 Note: Unnecessary use of -X or --request, GET is already inferred. * Rebuilt URL to: localhost:65238/ * Trying ::1... * TCP_NODELAY set * Connection failed * connect to ::1 port 65238 failed: Connection refused * Trying 127.0.0.1... * TCP_NODELAY set * Connected to localhost (127.0.0.1) port 65238 (#0) > GET / HTTP/1.1 > Host: localhost:65238 > User-Agent: curl/7.51.0 > Accept: */* > < HTTP/1.1 301 Moved Permanently < Connection: keep-alive < Location: http://localhost:65238/console/index.html < Content-Length: 0 < Date: Sun, 07 May 2017 03:25:04 GMT < * Curl_http_done: called premature == 0 * Connection #0 to host localhost left intact {code} showing that Wildfly is indeed listening and giving the usual redirect to the Console index. Instead, Wildfly should log the ephemeral port that it actually bound to: {{23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:65301/management 23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:65301}} was: When binding Wildfly Management Console to an ephemeral port (i.e., by specifying port 0), Wildfly states that the management console: {{23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled 23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled}} This isn't right. For example, using {{lsof}} I can see that Wildfly bound to an ephemeral port. After starting Wildfly with {{-Djboss.management.http.port=0}}: {{$ lsof -p `jps | grep jboss-modules.jar | awk '{print $1}'` -P -n | grep TCP java 59501 jason 379u IPv4 0xd038b817c1abd6a5 0t0 TCP 127.0.0.1:8080 (LISTEN) java 59501 jason 387u IPv4 0xd038b817acfc6a85 0t0 TCP 127.0.0.1:65238 (LISTEN) java 59501 jason 390u IPv4 0xd038b817b86956a5 0t0 TCP 127.0.0.1:8443 (LISTEN) $ curl -v -XGET localhost:65238 Note: Unnecessary use of -X or --request, GET is already inferred. * Rebuilt URL to: localhost:65238/ * Trying ::1... * TCP_NODELAY set * Connection failed * connect to ::1 port 65238 failed: Connection refused * Trying 127.0.0.1... * TCP_NODELAY set * Connected to localhost (127.0.0.1) port 65238 (#0) > GET / HTTP/1.1 > Host: localhost:65238 > User-Agent: curl/7.51.0 > Accept: */* > < HTTP/1.1 301 Moved Permanently < Connection: keep-alive < Location: http://localhost:65238/console/index.html < Content-Length: 0 < Date: Sun, 07 May 2017 03:25:04 GMT < * Curl_http_done: called premature == 0 * Connection #0 to host localhost left intact}} showing that Wildfly is indeed listening and giving the usual redirect to the Console index. Instead, Wildfly should log the ephemeral port that it actually bound to: {{23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:65301/management 23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:65301}} > Wildfly Management Console should log bound ports > ------------------------------------------------- > > Key: WFCORE-2771 > URL: https://issues.jboss.org/browse/WFCORE-2771 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Jason Tedor > Assignee: Jason Greene > > When binding Wildfly Management Console to an ephemeral port (i.e., by specifying port 0), Wildfly states that the management console: > {{23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled > 23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled}} > This isn't right. For example, using {{lsof}} I can see that Wildfly bound to an ephemeral port. After starting Wildfly with {{-Djboss.management.http.port=0}}: > {code} > $ lsof -p `jps | grep jboss-modules.jar | awk '{print $1}'` -P -n | grep TCP > java 59501 jason 379u IPv4 0xd038b817c1abd6a5 0t0 TCP 127.0.0.1:8080 (LISTEN) > java 59501 jason 387u IPv4 0xd038b817acfc6a85 0t0 TCP 127.0.0.1:65238 (LISTEN) > java 59501 jason 390u IPv4 0xd038b817b86956a5 0t0 TCP 127.0.0.1:8443 (LISTEN) > $ curl -v -XGET localhost:65238 > Note: Unnecessary use of -X or --request, GET is already inferred. > * Rebuilt URL to: localhost:65238/ > * Trying ::1... > * TCP_NODELAY set > * Connection failed > * connect to ::1 port 65238 failed: Connection refused > * Trying 127.0.0.1... > * TCP_NODELAY set > * Connected to localhost (127.0.0.1) port 65238 (#0) > > GET / HTTP/1.1 > > Host: localhost:65238 > > User-Agent: curl/7.51.0 > > Accept: */* > > > < HTTP/1.1 301 Moved Permanently > < Connection: keep-alive > < Location: http://localhost:65238/console/index.html > < Content-Length: 0 > < Date: Sun, 07 May 2017 03:25:04 GMT > < > * Curl_http_done: called premature == 0 > * Connection #0 to host localhost left intact > {code} > showing that Wildfly is indeed listening and giving the usual redirect to the Console index. > Instead, Wildfly should log the ephemeral port that it actually bound to: > {{23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:65301/management > 23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:65301}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2771) Wildfly Management Console should log bound ports

by Jason Tedor (JIRA)

Jason Tedor created WFCORE-2771: ----------------------------------- Summary: Wildfly Management Console should log bound ports Key: WFCORE-2771 URL: https://issues.jboss.org/browse/WFCORE-2771 Project: WildFly Core Issue Type: Bug Components: Server Reporter: Jason Tedor Assignee: Jason Greene When binding Wildfly Management Console to an ephemeral port (i.e., by specifying port 0), Wildfly states that the management console: {{23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled 23:15:55,138 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled}} This isn't right. For example, using {{lsof}} I can see that Wildfly bound to an ephemeral port. After starting Wildfly with {{-Djboss.management.http.port=0}}: {{$ lsof -p `jps | grep jboss-modules.jar | awk '{print $1}'` -P -n | grep TCP java 59501 jason 379u IPv4 0xd038b817c1abd6a5 0t0 TCP 127.0.0.1:8080 (LISTEN) java 59501 jason 387u IPv4 0xd038b817acfc6a85 0t0 TCP 127.0.0.1:65238 (LISTEN) java 59501 jason 390u IPv4 0xd038b817b86956a5 0t0 TCP 127.0.0.1:8443 (LISTEN) $ curl -v -XGET localhost:65238 Note: Unnecessary use of -X or --request, GET is already inferred. * Rebuilt URL to: localhost:65238/ * Trying ::1... * TCP_NODELAY set * Connection failed * connect to ::1 port 65238 failed: Connection refused * Trying 127.0.0.1... * TCP_NODELAY set * Connected to localhost (127.0.0.1) port 65238 (#0) > GET / HTTP/1.1 > Host: localhost:65238 > User-Agent: curl/7.51.0 > Accept: */* > < HTTP/1.1 301 Moved Permanently < Connection: keep-alive < Location: http://localhost:65238/console/index.html < Content-Length: 0 < Date: Sun, 07 May 2017 03:25:04 GMT < * Curl_http_done: called premature == 0 * Connection #0 to host localhost left intact}} showing that Wildfly is indeed listening and giving the usual redirect to the Console index. Instead, Wildfly should log the ephemeral port that it actually bound to: {{23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:65301/management 23:27:09,347 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:65301}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1554) Implement the java scripting interfaces (old JSR 223) for the FEEL engine

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1554: ------------------------------------- Summary: Implement the java scripting interfaces (old JSR 223) for the FEEL engine Key: DROOLS-1554 URL: https://issues.jboss.org/browse/DROOLS-1554 Project: Drools Issue Type: Feature Request Components: dmn engine Affects Versions: 7.0.0.CR3 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.1.0.Final Implement the java scripting interfaces (old JSR 223) for the FEEL engine, allowing it to be embedded in any java scripting shell. The interfaces are part of the javax.script package: https://docs.oracle.com/javase/8/docs/api/javax/script/package-frame.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1554) Implement the java scripting interfaces (old JSR 223) for the FEEL engine

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1554?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1554: ------------------------------------- Assignee: Alexandros Koufoudakis (was: Edson Tirelli) > Implement the java scripting interfaces (old JSR 223) for the FEEL engine > ------------------------------------------------------------------------- > > Key: DROOLS-1554 > URL: https://issues.jboss.org/browse/DROOLS-1554 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Affects Versions: 7.0.0.CR3 > Reporter: Edson Tirelli > Assignee: Alexandros Koufoudakis > Fix For: 7.1.0.Final > > > Implement the java scripting interfaces (old JSR 223) for the FEEL engine, allowing it to be embedded in any java scripting shell. > The interfaces are part of the javax.script package: > https://docs.oracle.com/javase/8/docs/api/javax/script/package-frame.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1553) Write documentation for the DMN and FEEL components

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1553?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1553: ---------------------------------- Issue Type: Task (was: Enhancement) > Write documentation for the DMN and FEEL components > --------------------------------------------------- > > Key: DROOLS-1553 > URL: https://issues.jboss.org/browse/DROOLS-1553 > Project: Drools > Issue Type: Task > Components: dmn engine > Affects Versions: 7.0.0.CR3 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.0.0.Final, 7.1.0.Final > > > Write the documentation for both FEEL and DMN engines. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1553) Write documentation for the DMN and FEEL components

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1553: ------------------------------------- Summary: Write documentation for the DMN and FEEL components Key: DROOLS-1553 URL: https://issues.jboss.org/browse/DROOLS-1553 Project: Drools Issue Type: Enhancement Components: dmn engine Affects Versions: 7.0.0.CR3 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.0.0.Final, 7.1.0.Final Write the documentation for both FEEL and DMN engines. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1552) Raise a warning during DMN Decision Table validation if the user uses expressions in the cell

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1552: ------------------------------------- Summary: Raise a warning during DMN Decision Table validation if the user uses expressions in the cell Key: DROOLS-1552 URL: https://issues.jboss.org/browse/DROOLS-1552 Project: Drools Issue Type: Enhancement Components: dmn engine Affects Versions: 7.0.0.CR3 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.1.0.Final KIE DMN engine implementation extends the specification to allow expressions to be used as end-points in unary tests. Since this is an extension to the specification, the DMN validation component should raise a warning to the user, letting him know this is an extension, whenever he uses expressions in DT cells. The warning should not be raised in case the expression is a simple use of the date/time/duration functions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1551) Implement FEEL/DMN value marshaller

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1551: ------------------------------------- Summary: Implement FEEL/DMN value marshaller Key: DROOLS-1551 URL: https://issues.jboss.org/browse/DROOLS-1551 Project: Drools Issue Type: Feature Request Components: dmn engine Affects Versions: 7.0.0.CR3 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.1.0.Final Some value types in FEEL/DMN require special formatting when marshalling/unmarshalling. For instance: {quote} So it seems that ISO 8601 does not define negative intervals. I.e., ISO 8601 only supports things like "PT1H". XPath extends that with a leading optional sign, like "+PT1H" and "-PT1H". Java extends that allowing the sign to be used in each of the units in the duration like, "PT+1H", "PT-1H", besides the leading sign "-PT1H". The FEEL spec on page 113 seems to follow the XPath lexical definition, so the leading sign "-PT1H" seems to be the correct format. {quote} Implement an object marshaller for DMN/FEEL that is capable of marshalling/unmarshalling objects. Most object types are straightforward, but a few of them (like durations) need special handling. In particular: * negative duration should use a leading - sign instead of having the sign in the unit numbers * durations need to be normalized before marshalled: {quote} A days and time duration in the semantic domain is a sequence of numbers for the days, hours, minutes, and seconds of duration, normalized such that the sum of these numbers is minimized. {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1546) Improve FEEL tests to check for errors to prevent regressions

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1546?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1546: ---------------------------------- Issue Type: Task (was: Bug) > Improve FEEL tests to check for errors to prevent regressions > ------------------------------------------------------------- > > Key: DROOLS-1546 > URL: https://issues.jboss.org/browse/DROOLS-1546 > Project: Drools > Issue Type: Task > Components: dmn engine > Affects Versions: 7.0.0.CR3 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Fix For: 7.1.0.Final > > > At the moment, FEEL tests ignore errors raised by the engine. We need to add proper checks for that to prevent future regressions. > This task should be mostly about fixing the current tests, but we may uncover bugs while going through it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 May 2017