July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2733) Support MVEL Dialect using custom inline accumulate code with external declarations in the executable model

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-2733?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-2733: --------------------------------- Integrating the MVEL compiler in Drools legacy generation of MVEL classes is so no easy task, and it's probably better to drop the support for inline accumulate altogether > Support MVEL Dialect using custom inline accumulate code with external declarations in the executable model > ----------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2733 > URL: https://issues.jboss.org/browse/DROOLS-2733 > Project: Drools > Issue Type: Feature Request > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Optional > > The executable model doesn't support custom inline accumulate code that uses external declarations such as > {code:java} > String str = "import " + Person.class.getCanonicalName() + ";\n" + > "rule R dialect \"mvel\" when\n" + > " String( $l : length )" + > " $sum : Integer() from accumulate (\n" + > " Person( age > 18, $age : age ), init( int sum = 0 * $l; ), action( sum += $age; ), reverse( sum -= $age; ), result( sum )\n" + > " )" + > "then\n" + > " insert($sum);\n" + > "end"; > {code} > (Notice that in the init we multiply the sum value with the length of string) > But it can support such style using the "classic" generation of accumulate classes which gets compiled among the executable model and instantiate during the execution of the DSL. > This mechanism is broken with the MVEL dialect, as we don't have such generated classes. > Probably what we should do instead is putting MVEL expressions in the DSL directly such as > {code:java} > accumulateScript("initCode", "accCode", "reverseCode"); > {code} > and then during interpretation create a new MVEL context and execute the accumulate in memory > See > AccumulateUnsupportedTest.testMVELAccumulate > AccumulateUnsupportedTest.testMVELAccumulate2WM -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12085) java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties

by Emmanuel Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-12085?page=com.atlassian.jira.plugin... ] Emmanuel Hugonnet commented on WFLY-12085: ------------------------------------------ This has been fixed in Apache Artemis 2.9.0 commit 4fffc0277835815699f2a740910175683155df78 Author: James Perkins <jperkins(a)redhat.com> Date: Thu May 16 14:07:25 2019 -0700 ARTEMIS-2342 Use a URL instead of a URI for the logging.configuration property The property the log manager itself expects is a URL which could result in an invalid URI missing the // prefix after file:. > java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties > ------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12085 > URL: https://issues.jboss.org/browse/WFLY-12085 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 17.0.0.Alpha1, 17.0.0.Final > Environment: Red Hat JBoss Enterprise Application Platform > 7.2.1 > Microsoft Windows 10 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > Labels: downstream_dependency > > There seems to be a regression in JBoss EAP 7.2.1 patch. After applying it the following exception can be seen in the server log file during the startup: > {noformat} > 2019-05-13 11:45:11,419 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ222277: Problem initializing automatic logging configuration reload for file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties: java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties > at java.net.URI$Parser.fail(URI.java:2848) > at java.net.URI$Parser.checkChars(URI.java:3021) > at java.net.URI$Parser.parse(URI.java:3058) > at java.net.URI.<init>(URI.java:588) > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:2369) > at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:64) > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:544) > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:481) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:376) > at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:206) > at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:65) > at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:100) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {noformat} > This issue only affects Microsoft Windows platform. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-416) Make JBoss Medata available in Maven Central

by David Hladky (Jira)

[ https://issues.jboss.org/browse/JBMETA-416?page=com.atlassian.jira.plugin... ] David Hladky closed JBMETA-416. ------------------------------- > Make JBoss Medata available in Maven Central > -------------------------------------------- > > Key: JBMETA-416 > URL: https://issues.jboss.org/browse/JBMETA-416 > Project: JBoss Metadata > Issue Type: Task > Reporter: Sanne GRINOVERO > Assignee: David Hladky > Priority: Major > > Hello, > we're using {{jboss-metadata-web}} in Quarkus, and we'd really appreciate if our users could build applications without having to setup their Maven configuration to find dependencies in JBoss Nexus. > Could someone please take care that releases get synched to Maven Central ? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12042) EE Concurrency SetupContextHandle and ResetContextHandle impls do not declare serialVersionUID

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12042?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12042: ----------------------------------- Summary: EE Concurrency SetupContextHandle and ResetContextHandle impls do not declare serialVersionUID (was: EE Concurrency SetupContextHandle impls do not declare serialVersionUID) > EE Concurrency SetupContextHandle and ResetContextHandle impls do not declare serialVersionUID > ---------------------------------------------------------------------------------------------- > > Key: WFLY-12042 > URL: https://issues.jboss.org/browse/WFLY-12042 > Project: WildFly > Issue Type: Bug > Components: Concurrency Utilities > Affects Versions: 16.0.0.Final > Reporter: Brian Stansberry > Assignee: Eduardo Martins > Priority: Minor > > The org.glassfish.enterprise.concurrent.spi.ContextHandle interface extends Serializable but the various impls in WildFly are not declaring a serialVersionUID. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12283) Upgrade IronJacamar from 1.4.16.Final to 1.4.17.Final

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/WFLY-12283?page=com.atlassian.jira.plugin... ] Martin Stefanko updated WFLY-12283: ----------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/12227) > Upgrade IronJacamar from 1.4.16.Final to 1.4.17.Final > ----------------------------------------------------- > > Key: WFLY-12283 > URL: https://issues.jboss.org/browse/WFLY-12283 > Project: WildFly > Issue Type: Component Upgrade > Components: JCA > Affects Versions: 17.0.1.Final > Reporter: Martin Stefanko > Assignee: Stefano Maestri > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12283) Upgrade IronJacamar from 1.4.16.Final to 1.4.17.Final

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/WFLY-12283?page=com.atlassian.jira.plugin... ] Martin Stefanko updated WFLY-12283: ----------------------------------- Affects Version/s: 17.0.1.Final (was: 16.0.0.Final) > Upgrade IronJacamar from 1.4.16.Final to 1.4.17.Final > ----------------------------------------------------- > > Key: WFLY-12283 > URL: https://issues.jboss.org/browse/WFLY-12283 > Project: WildFly > Issue Type: Component Upgrade > Components: JCA > Affects Versions: 17.0.1.Final > Reporter: Martin Stefanko > Assignee: Stefano Maestri > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12283) Upgrade IronJacamar from 1.4.16.Final to 1.4.17.Final

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/WFLY-12283?page=com.atlassian.jira.plugin... ] Martin Stefanko updated WFLY-12283: ----------------------------------- Fix Version/s: (was: 17.0.0.Alpha1) (was: 17.0.0.Final) > Upgrade IronJacamar from 1.4.16.Final to 1.4.17.Final > ----------------------------------------------------- > > Key: WFLY-12283 > URL: https://issues.jboss.org/browse/WFLY-12283 > Project: WildFly > Issue Type: Component Upgrade > Components: JCA > Affects Versions: 17.0.1.Final > Reporter: Martin Stefanko > Assignee: Stefano Maestri > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12283) Upgrade IronJacamar from 1.4.16.Final to 1.4.17.Final

by Martin Stefanko (Jira)

Martin Stefanko created WFLY-12283: -------------------------------------- Summary: Upgrade IronJacamar from 1.4.16.Final to 1.4.17.Final Key: WFLY-12283 URL: https://issues.jboss.org/browse/WFLY-12283 Project: WildFly Issue Type: Component Upgrade Components: JCA Affects Versions: 16.0.0.Final Reporter: Martin Stefanko Assignee: Stefano Maestri Fix For: 17.0.0.Alpha1, 17.0.0.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-821) Allow to specify which psi project to use for ocp 4 provisioning

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-821?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-821. --------------------------------- Resolution: Done Will use istioci account for both projects. https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-utils/commit/e10f9f... https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-utils/commit/ef83d3... > Allow to specify which psi project to use for ocp 4 provisioning > ---------------------------------------------------------------- > > Key: SWSQE-821 > URL: https://issues.jboss.org/browse/SWSQE-821 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > We have job https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/infra/job/inst... for provisioning of ocp4 but it's not possible to specify which PSI project should be used. > We need to update the job to allow use both istio-dev and kiali-qe projects. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11841) EE concurrency resources should use capability wiring

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11841?page=com.atlassian.jira.plugin... ] Eduardo Martins commented on WFLY-11841: ---------------------------------------- ??There's probably missing capability wiring within the concurrency resources as well; e.g. for dependency by executors on thread factories.?? EE Concurrency uses its own thread factories. > EE concurrency resources should use capability wiring > ----------------------------------------------------- > > Key: WFLY-11841 > URL: https://issues.jboss.org/browse/WFLY-11841 > Project: WildFly > Issue Type: Bug > Components: Concurrency Utilities > Affects Versions: 16.0.0.Final > Reporter: Brian Stansberry > Assignee: Eduardo Martins > Priority: Major > > This kind of thing is a bug: > https://github.com/wildfly/wildfly/blob/master/ee/src/main/java/org/jboss... > The subsystem exposes a capability so consumers of its services should use the capabilities API to handle requiring it and accessing its services. > There's probably missing capability wiring within the concurrency resources as well; e.g. for dependency by executors on thread factories. -- This message was sent by Atlassian Jira (v7.12.1#712002)

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