November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2850) Create a Verifier client side adapter for DMN tables

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-2850?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2850: ----------------------------------- Sprint: 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47, 2018 Week 48-50 (was: 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47) > Create a Verifier client side adapter for DMN tables > ---------------------------------------------------- > > Key: DROOLS-2850 > URL: https://issues.jboss.org/browse/DROOLS-2850 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor, verifier > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2989) Avoid refire of rules with synthetic Fact Handles

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-2989?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2989: ----------------------------------- Sprint: 2018 Week 36-38, 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47, 2018 Week 48-50 (was: 2018 Week 36-38, 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47) > Avoid refire of rules with synthetic Fact Handles > ------------------------------------------------- > > Key: DROOLS-2989 > URL: https://issues.jboss.org/browse/DROOLS-2989 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > Currently the FromNode and the AccumulateNode create "synthetic" fact handles, that means they're not serialized and they're recreated in memory each time we need the access. > There's already a way to avoid the refiring of the rules but involves serializing and deserializing these synthetic Fact Handles without the objects. > We now want a better way to do it by serializing the objects without their FactHandles and at the same time keep the same behaviour as before (same number of rules should fire) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2373) BRL "is contained in the (comma separated) list" does not produce multiselect dropdown

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-2373?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2373: ----------------------------------- Sprint: 2018 Week 45-47, 2018 Week 48-50 (was: 2018 Week 45-47) > BRL "is contained in the (comma separated) list" does not produce multiselect dropdown > -------------------------------------------------------------------------------------- > > Key: DROOLS-2373 > URL: https://issues.jboss.org/browse/DROOLS-2373 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Affects Versions: 7.6.0.Final > Environment: Tomcat 8.5 / RHEL 7 > Reporter: Yannick Geerts > Assignee: Toni Rikkola > Priority: Major > > Google groups link: https://groups.google.com/forum/#!topic/drools-usage/VElZ3KAZMIs > *Edited* > The problem is that in the piece of code below the expression {{column.getOperator()}} returns null. > {{BRLConditionVariableColumnConverter#convertColumn}} > {code:java} > if (OperatorsOracle.operatorRequiresList(column.getOperator())) { > return newMultipleSelectEnumColumn(factType, > factField, > column, > access, > gridWidget); > } else { > return newSingleSelectionEnumColumn(factType, > factField, > dataType, > column, > access, > gridWidget); > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3003) Enhance performance of PMML using decision trees

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3003?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3003: ----------------------------------- Sprint: 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47, 2018 Week 48-50 (was: 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47) > Enhance performance of PMML using decision trees > ------------------------------------------------ > > Key: DROOLS-3003 > URL: https://issues.jboss.org/browse/DROOLS-3003 > Project: Drools > Issue Type: Enhancement > Affects Versions: 7.12.0.Final > Reporter: Lance Leverich > Assignee: Lance Leverich > Priority: Major > > Refactor the generation of rules and classes by the PMMLCompiler, for PMML resources containing Tree models. > # Replace any remaining instances of types declared in rules files with POJOs > # Reduce and/or remove the usage of rules in the process of generating rules and classes > # Expose/make available the POJO that is generated from the MiningSchema, so that it can be used as input, instead of PMMLRequestData type > # Update rules to make direct use of the input POJO -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3002) Enhance performance of PMML using scorecards

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3002?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3002: ----------------------------------- Sprint: 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47, 2018 Week 48-50 (was: 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47) > Enhance performance of PMML using scorecards > -------------------------------------------- > > Key: DROOLS-3002 > URL: https://issues.jboss.org/browse/DROOLS-3002 > Project: Drools > Issue Type: Enhancement > Components: PMML > Affects Versions: 7.12.0.Final > Reporter: Lance Leverich > Assignee: Lance Leverich > Priority: Major > Labels: drools-core > > Re-factoring of the classes and mechanisms that generate rules and classes from a PMML resource that contains a Scorecard model. > # Make further usage of POJOs to replace any types declared within the rule file > # Make the generation of rules and classes be more direct (i.e. reduce/remove the rules engine use in generating rules and classes) > # Reduce the rules generated so that the number of steps required to apply a model is minimized -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11374) Master Artemis in Wildfly 10.1.0.Final is not announcing backup when restarted

by Srinivas ev (Jira)

[ https://issues.jboss.org/browse/WFLY-11374?page=com.atlassian.jira.plugin... ] Srinivas ev commented on WFLY-11374: ------------------------------------ Hi [~jmesnil], can you check this issue. > Master Artemis in Wildfly 10.1.0.Final is not announcing backup when restarted > ------------------------------------------------------------------------------ > > Key: WFLY-11374 > URL: https://issues.jboss.org/browse/WFLY-11374 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: active standalone full ha.xml, master and slave log samples on startup.txt, master restart.txt, master shutdown.txt, master-server-linux.log, master-server-windows.log, master.xml, rotateserver_active.log, rotateserver_active.log, rotateserver_backup.log, rotateserver_slave.log, slave standalone full ha.xml, slave-server-linux.log, slave-server-windows.log, slave.xml > > > I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work. > This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine. > master in standalone-full-ha.xml - refer master.xml > slave in standalone-full-ha.xml - refer slave.xml > In the startup script, I am passing all the values for placeholders of my server host ip's accordingly. > Test scenario - > 1. Bring master up. > 2. Bring slave up. > 3. slave will announce the backup. (AMQ221031: backup announced). > 4. Make master down. > 5. Replication is success. > 6. Slave is acting as master/live. > 7. Make master up. > Issue - master is unable to announce the backup and starts normally as a standalone wildfly. > This backup announcement works fine in windows and failover also works as expected. > Please let me know if anything specific required along with this details. > Artemis jar version - artemis-*****-1.1.0.wildfly-017.jar > in path - /opt/aor/${my project}/wildfly/modules/system/layers/base/org/apache/activemq/artemis/main > Few logs I found which may be impacting and I am not clear - > 1.2018-11-21 14:28:07,238 TRACE [org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge] (Thread-18 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@38e819b6-2112524495)) Setting up bridge between TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEnabled=true&httpPpgradeEndpoint=http-acceptor&port=12080&host=135-250-139-30 and ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEnabled=true&httpPpgradeEndpoint=http-acceptor&port=12080&host=135-250-139-41], discoveryGroupConfiguration=null]: java.lang.Exception: trace > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge.<init>(ClusterConnectionBridge.java:129) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl.createNewRecord(ClusterConnectionImpl.java:778) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl.nodeUP(ClusterConnectionImpl.java:698) > at org.apache.activemq.artemis.core.client.impl.Topology$1.run(Topology.java:264) > at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:103) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > 2. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3334) [DMN Designer] Data Types - "Structure" Data Types are being set as "Undefined"

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3334?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3334: -------------------------------- Fix Version/s: 7.15.0.Final > [DMN Designer] Data Types - "Structure" Data Types are being set as "Undefined" > ------------------------------------------------------------------------------- > > Key: DROOLS-3334 > URL: https://issues.jboss.org/browse/DROOLS-3334 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.15.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Fix For: 7.15.0.Final > > Attachments: bug.png > > > Structure Data Types are being set as Undefined: > !bug.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3334) [DMN Designer] Data Types - "Structure" Data Types are being set as "Undefined"

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3334?page=com.atlassian.jira.plugi... ] Guilherme Carreiro commented on DROOLS-3334: -------------------------------------------- [~jomarko] Yes. > [DMN Designer] Data Types - "Structure" Data Types are being set as "Undefined" > ------------------------------------------------------------------------------- > > Key: DROOLS-3334 > URL: https://issues.jboss.org/browse/DROOLS-3334 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.15.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: bug.png > > > Structure Data Types are being set as Undefined: > !bug.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3354) [GDST] Not able to edit empty cell

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3354?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-3354. ------------------------------- > [GDST] Not able to edit empty cell > ---------------------------------- > > Key: DROOLS-3354 > URL: https://issues.jboss.org/browse/DROOLS-3354 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Fix For: 7.15.0.Final > > Attachments: Screenshot from 2018-11-26 09-52-42.png > > > User is unable to edit empty cell of a guided decision table by double click. Always appears the unexpected error dialog containing an error: > {code} > Uncaught exception: Exception caught: Exception caught: (TypeError) : Cannot read property 'g7' of null Caused by: Exception caught: (TypeError) : Cannot read property 'g7' of null Caused by: (TypeError) : Cannot read property 'g7' of null > {code} > Edit action for non-empty cell works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11411) ModuleClassLoader fails with ClassNotFoundException when class in a jar file

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-11411?page=com.atlassian.jira.plugin... ] Yeray Borges commented on WFLY-11411: ------------------------------------- Wildlfly treats war deployments as single module with isolate class loading. If you want to access to classes in a .jar file from a war project, you have to package the war deployment including the jar file in the WEB-INF/lib folder. Doing so, you should be able to share the classes. I've just verified that this packaging is working fine in Wildfly 14. [~karlnicholas] are you including your jar file in the war deployment?, if so, please, attach your complete project structure to take a look > ModuleClassLoader fails with ClassNotFoundException when class in a jar file > ---------------------------------------------------------------------------- > > Key: WFLY-11411 > URL: https://issues.jboss.org/browse/WFLY-11411 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 11.0.0.Final, 14.0.0.Final > Environment: Wildfly 11, 14, Java 1.8, Windows 10 > Reporter: Karl Nicholas > Assignee: Yeray Borges > Priority: Major > Attachments: JaxRsActivator.java, RestSever.java > > > Simple REST service with Application activator in project and Rest Server in another project with jar file fails to load. > Works okay with EAR project structure but not with simpler WAR project structure. > Caused by: java.lang.ClassNotFoundException: rest.service.server.RestSever from [Module "deployment.restserver7.war" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 2018