November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-258) Galleon Maven repo in builder image contains redundant artifacts

by Nikoleta Ziakova (Jira)

Nikoleta Ziakova created WFWIP-258: -------------------------------------- Summary: Galleon Maven repo in builder image contains redundant artifacts Key: WFWIP-258 URL: https://issues.jboss.org/browse/WFWIP-258 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Nikoleta Ziakova Assignee: Jean Francois Denise The maven repo located at {{/opt/jboss/container/wildfly/s2i/galleon/galleon-m2-repository/}} contains artifacts that are not available in jboss-eap-7.3.0.CD18-CR1-image-builder-maven-repository.zip located at http://download-ipv4.eng.brq.redhat.com/devel/candidates/middleware/eap/J... The redundant artifacts are: http://pastebin.test.redhat.com/813263 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4711) [DMN Designer] User is able to drag single data type entry horizontally

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4711?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4711: ------------------------------------ Story Points: 1 Sprint: 2019 Week 44-46 (from Okt 28) > [DMN Designer] User is able to drag single data type entry horizontally > ----------------------------------------------------------------------- > > Key: DROOLS-4711 > URL: https://issues.jboss.org/browse/DROOLS-4711 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Optional > Labels: drools-tools > Attachments: horizontally.webm > > > This issue is caused by DROOLS-4484 > If there is single data type entry user is able to drag in horizontally. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4698) Adding "expression" type handling for Collection type propereties

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4698?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4698: ------------------------------- Sprint: (was: 2019 Week 44-46 (from Okt 28)) > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4698 > URL: https://issues.jboss.org/browse/DROOLS-4698 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Fix For: 7.30.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1672) "not" in variable name doesn't work

by Tibor Zimanyi (Jira)

[ https://issues.jboss.org/browse/DROOLS-1672?page=com.atlassian.jira.plugi... ] Tibor Zimanyi closed DROOLS-1672. --------------------------------- Fix Version/s: 7.30.0.Final Resolution: Done > "not" in variable name doesn't work > ----------------------------------- > > Key: DROOLS-1672 > URL: https://issues.jboss.org/browse/DROOLS-1672 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimanyi > Assignee: Edson Tirelli > Priority: Major > Labels: reported-by-qe > Fix For: 7.30.0.Final > > > When trying this test case: > {code}{ is not exactly 18 : != 18, bob is not exactly 18 : is not exactly 18(16) }.bob is not exactly 18"{code} > the parser fails like this [1] > [1] https://gist.github.com/baldimir/7c13b9c76087d44f95802ded8b72877f > Will provide a PR with a reproducer. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1672) "not" in variable name doesn't work

by Tibor Zimanyi (Jira)

[ https://issues.jboss.org/browse/DROOLS-1672?page=com.atlassian.jira.plugi... ] Tibor Zimanyi updated DROOLS-1672: ---------------------------------- Comment: was deleted (was: A comment with security level 'Red Hat Employee' was removed.) > "not" in variable name doesn't work > ----------------------------------- > > Key: DROOLS-1672 > URL: https://issues.jboss.org/browse/DROOLS-1672 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimanyi > Assignee: Edson Tirelli > Priority: Major > Labels: reported-by-qe > > When trying this test case: > {code}{ is not exactly 18 : != 18, bob is not exactly 18 : is not exactly 18(16) }.bob is not exactly 18"{code} > the parser fails like this [1] > [1] https://gist.github.com/baldimir/7c13b9c76087d44f95802ded8b72877f > Will provide a PR with a reproducer. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1476) Decision Tables (CSV) - Treat empty cells right from ObjectType declaration as merged

by Tibor Zimanyi (Jira)

[ https://issues.jboss.org/browse/DROOLS-1476?page=com.atlassian.jira.plugi... ] Tibor Zimanyi commented on DROOLS-1476: --------------------------------------- Closing this as outdated. Also the cloned issue was closed. > Decision Tables (CSV) - Treat empty cells right from ObjectType declaration as merged > ------------------------------------------------------------------------------------- > > Key: DROOLS-1476 > URL: https://issues.jboss.org/browse/DROOLS-1476 > Project: Drools > Issue Type: Enhancement > Components: decision tables > Affects Versions: 7.0.0.Beta7 > Reporter: Martin Cimbalek > Assignee: Mario Fusco > Priority: Minor > > Because of CSV doesn't support merging cells like in .xls or .xlsx, saving decision table as .csv currently requires additional binding and matching instead of merging cells, which causes the merged columns are merged into one set of constraints. > Proposing that empty cells right from ObjectType definition in CSV would be treated as the merged ones in .xls. This approach may be applicable also for .xls -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1476) Decision Tables (CSV) - Treat empty cells right from ObjectType declaration as merged

by Tibor Zimanyi (Jira)

[ https://issues.jboss.org/browse/DROOLS-1476?page=com.atlassian.jira.plugi... ] Tibor Zimanyi closed DROOLS-1476. --------------------------------- Resolution: Won't Do > Decision Tables (CSV) - Treat empty cells right from ObjectType declaration as merged > ------------------------------------------------------------------------------------- > > Key: DROOLS-1476 > URL: https://issues.jboss.org/browse/DROOLS-1476 > Project: Drools > Issue Type: Enhancement > Components: decision tables > Affects Versions: 7.0.0.Beta7 > Reporter: Martin Cimbalek > Assignee: Mario Fusco > Priority: Minor > > Because of CSV doesn't support merging cells like in .xls or .xlsx, saving decision table as .csv currently requires additional binding and matching instead of merging cells, which causes the merged columns are merged into one set of constraints. > Proposing that empty cells right from ObjectType definition in CSV would be treated as the merged ones in .xls. This approach may be applicable also for .xls -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12777) Stateful bean with @StatefulTimeout value -1 should not timeout or removed

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-12777?page=com.atlassian.jira.plugin... ] Cheng Fang updated WFLY-12777: ------------------------------ Description: Stateful bean with @StatefulTimeout value -1 should not timeout or removed. A value of -1 means the bean will never be removed due to timeout. When running with the latest WildFly snapshot (2019-11-11), such a stateful bean was unexpectedly timed out and removed. {code:java} @Stateful @StatefulTimeout(value = -1, unit=TimeUnit.DAYS) @AccessTimeout(value=StatefulTimeoutIF.TIMEOUT_DAYS, unit=TimeUnit.DAYS) @Local(StatefulTimeoutIF.class) public class Minus1TimeoutBean { ... } {code} Or the stateful bean timeout can be configured with ejb-jar.xml: {code:xml} <session> <ejb-name>xx</ejb-name> <business-local>xx</business-local> <ejb-class>xx</ejb-class> <session-type>Stateful</session-type> <stateful-timeout> <timeout>-1</timeout> <unit>Days</unit> </stateful-timeout> <concurrency-management-type>Container</concurrency-management-type> </session> {code} was: Stateful bean with @StatefulTimeout value -1 should not timeout or removed. A value of -1 means the bean will never be removed due to timeout. When running with the latest WildFly snapshot (2019-11-11), such a stateful bean was unexpectedly timed out and removed. {code:java} @Stateful @StatefulTimeout(value = -1, unit=TimeUnit.DAYS) @AccessTimeout(value=StatefulTimeoutIF.TIMEOUT_DAYS, unit=TimeUnit.DAYS) @Local(StatefulTimeoutIF.class) public class Minus1TimeoutBean { ... } {code} Or the stateful bean timeout can be configured with ejb-jar.xml: {code:xml} <session> <ejb-name>xx</ejb-name> <business-local>xx</business-local> <ejb-class>xx</ejb-class> <session-type>Stateful</session-type> <stateful-timeout> <timeout>-1</timeout> <unit>Days</unit> </stateful-timeout> <concurrency-management-type>Container</concurrency-management-type> </session> {code} > Stateful bean with @StatefulTimeout value -1 should not timeout or removed > -------------------------------------------------------------------------- > > Key: WFLY-12777 > URL: https://issues.jboss.org/browse/WFLY-12777 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 19.0.0.Beta1 > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > Fix For: 19.0.0.Beta1 > > > Stateful bean with @StatefulTimeout value -1 should not timeout or removed. > A value of -1 means the bean will never be removed due to timeout. When running with the latest WildFly snapshot (2019-11-11), such a stateful bean was unexpectedly timed out and removed. > {code:java} > @Stateful > @StatefulTimeout(value = -1, unit=TimeUnit.DAYS) > @AccessTimeout(value=StatefulTimeoutIF.TIMEOUT_DAYS, unit=TimeUnit.DAYS) > @Local(StatefulTimeoutIF.class) > public class Minus1TimeoutBean { > ... > } > {code} > Or the stateful bean timeout can be configured with ejb-jar.xml: > {code:xml} > <session> > <ejb-name>xx</ejb-name> > <business-local>xx</business-local> > <ejb-class>xx</ejb-class> > <session-type>Stateful</session-type> > <stateful-timeout> > <timeout>-1</timeout> > <unit>Days</unit> > </stateful-timeout> > <concurrency-management-type>Container</concurrency-management-type> > </session> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12777) Stateful bean with @StatefulTimeout value -1 should not timeout or removed

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-12777?page=com.atlassian.jira.plugin... ] Cheng Fang updated WFLY-12777: ------------------------------ Description: Stateful bean with @StatefulTimeout value -1 should not timeout or removed. A value of -1 means the bean will never be removed due to timeout. When running with the latest WildFly snapshot (2019-11-11), such a stateful bean was unexpectedly timed out and removed. {code:java} @Stateful @StatefulTimeout(value = -1, unit=TimeUnit.DAYS) @AccessTimeout(value=StatefulTimeoutIF.TIMEOUT_DAYS, unit=TimeUnit.DAYS) @Local(StatefulTimeoutIF.class) public class Minus1TimeoutBean { ... } {code} Or the stateful bean timeout can be configured with ejb-jar.xml: {code:xml} <session> <ejb-name>xx</ejb-name> <business-local>xx</business-local> <ejb-class>xx</ejb-class> <session-type>Stateful</session-type> <stateful-timeout> <timeout>-1</timeout> <unit>Days</unit> </stateful-timeout> <concurrency-management-type>Container</concurrency-management-type> </session> {code} was: Stateful bean with @StatefulTimeout value -1 should not timeout or removed. A value of -1 means the bean will never be removed due to timeout. When running with the latest WildFly snapshot (2019-11-11), such a stateful bean was unexpectedly timed out and removed. {code:java} @Stateful @StatefulTimeout(value = -1, unit=TimeUnit.DAYS) @AccessTimeout(value=StatefulTimeoutIF.TIMEOUT_DAYS, unit=TimeUnit.DAYS) @Local(StatefulTimeoutIF.class) public class Minus1TimeoutBean { ... } {code} > Stateful bean with @StatefulTimeout value -1 should not timeout or removed > -------------------------------------------------------------------------- > > Key: WFLY-12777 > URL: https://issues.jboss.org/browse/WFLY-12777 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 19.0.0.Beta1 > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > Fix For: 19.0.0.Beta1 > > > Stateful bean with @StatefulTimeout value -1 should not timeout or removed. > A value of -1 means the bean will never be removed due to timeout. When running with the latest WildFly snapshot (2019-11-11), such a stateful bean was unexpectedly timed out and removed. > {code:java} > @Stateful > @StatefulTimeout(value = -1, unit=TimeUnit.DAYS) > @AccessTimeout(value=StatefulTimeoutIF.TIMEOUT_DAYS, unit=TimeUnit.DAYS) > @Local(StatefulTimeoutIF.class) > public class Minus1TimeoutBean { > ... > } > {code} > Or the stateful bean timeout can be configured with ejb-jar.xml: > {code:xml} > <session> > <ejb-name>xx</ejb-name> > <business-local>xx</business-local> > <ejb-class>xx</ejb-class> > <session-type>Stateful</session-type> > <stateful-timeout> > <timeout>-1</timeout> > <unit>Days</unit> > </stateful-timeout> > <concurrency-management-type>Container</concurrency-management-type> > </session> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12650) EL does not handle identifiers as JavaBeans

by Ricardo Martin Camarero (Jira)

[ https://issues.jboss.org/browse/WFLY-12650?page=com.atlassian.jira.plugin... ] Ricardo Martin Camarero commented on WFLY-12650: ------------------------------------------------ Finally it was decided to not delete the ImportedClassELResolver but adding a system property that allows disable it: {noformat} -Dorg.wildfly.extension.undertow.deployment.disableImportedClassELResolver=true {noformat} So the issue will be in wildfly but you can add that property to completely follow the spec. Note that this issue is a corner case when a variable matches a class name (you can always change the property name, using "testMBean" in the example JSP of teh description). The reason for this is to avoid a [performance penalty problem in the ScopedAttributeELResolver implementation|https://github.com/eclipse-ee4j/jsp-api/issues/57] that was also fixed previously in our own ImportedClassELResolver. > EL does not handle identifiers as JavaBeans > ------------------------------------------- > > Key: WFLY-12650 > URL: https://issues.jboss.org/browse/WFLY-12650 > Project: WildFly > Issue Type: Bug > Components: EE, Web (Undertow) > Affects Versions: 18.0.0.Final > Reporter: Ricardo Martin Camarero > Assignee: Ricardo Martin Camarero > Priority: Major > Attachments: ELTest.war > > > Even if defined JavaBeans using <jsp:useBean> in jsp, the EL expression is handled as java Class if that class is already imported in jsp. > {code:title=EX)test1.jsp|borderStyle=solid} > <%@ page language="java" contentType="text/html; charset=UTF-8" pageEncoding="UTF-8"%> > <%@page import="test.TestMBean"%> > <html> > <head> > <title>Test1</title> > </head> > <body> > <jsp:useBean id="TestMBean" class="test.TestMBean"/> > TestMBean.test : ${TestMBean.test} <br/> > </body> > </html> > {code} > Therefore, the following exceptions may occur: > {noformat} > Caused by: javax.el.PropertyNotFoundException: Either 'test' is not a public static field of the class 'test.TestMBean' or field is inacessable > at javax.el.StaticFieldELResolver.getValue(StaticFieldELResolver.java:107) > at org.apache.jasper.el.JasperELResolver.getValue(JasperELResolver.java:110) > at com.sun.el.parser.AstValue.getValue(AstValue.java:139) > at com.sun.el.parser.AstValue.getValue(AstValue.java:203) > at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:226) > at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:917) > at org.apache.jsp.test1_jsp._jspService(test1_jsp.java:107) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:791) > at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:433) > ... 46 more > {noformat} > According [EL spec|https://download.oracle.com/otn-pub/jcp/el-3_0-fr-eval-spec/EL3.0.FR...], Evaluating of the imported static field should be the last. > {quote} > 1.5.1 Evaluating Identifiers > The steps are used for evaluating an identifier. > ■ If the identifier is a lambda argument passed to a lambda expression invocation, its value is returned. > ■ Else if the identifier is a variable, the associated expression is evaluated and returned. > ■ Else if the identifier is resolved by the ELResolvers, the value returned from the ELResolvers is returned. > ■ Else if the identifier is an imported static field, its value is returned. > ■ Else return not resolved. > One implication of the explicit search order of the identifiers is that an identifier hides other identifiers (of the same name) that come after it in the list. > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

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