January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2248) Disable validation and verification for a specific decision table

by Ivo Bek (JIRA)

Ivo Bek created DROOLS-2248: ------------------------------- Summary: Disable validation and verification for a specific decision table Key: DROOLS-2248 URL: https://issues.jboss.org/browse/DROOLS-2248 Project: Drools Issue Type: Enhancement Components: decision tables Reporter: Ivo Bek Assignee: Mario Fusco Currently it seems it's not possible to disable verification and validation for specific decision table. Administrator can only enable/disable verification and validation globally for the whole workbench but usually business admins need to disable verification and validation for decision tables which are complex / contain huge amount of rows and similarly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2207) Validation and Verification panel is missing

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2207?page=com.atlassian.jira.plugi... ] Toni Rikkola resolved DROOLS-2207. ---------------------------------- Resolution: Out of Date > Validation and Verification panel is missing > -------------------------------------------- > > Key: DROOLS-2207 > URL: https://issues.jboss.org/browse/DROOLS-2207 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.5.0.Final, 7.6.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Critical > > The Validation and Verification panel is missing. The server log contains error [1], however looking into the workbench war, all v&v jars seems to be present. > [1] > ERROR [org.drools.workbench.services.verifier.plugin.backend.VerifierWebWorkerServlet] (default task-119) Failed to load verifier web worker. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2207) Validation and Verification panel is missing

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2207?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-2207: -------------------------------------- [~jomarko] Great.. > Validation and Verification panel is missing > -------------------------------------------- > > Key: DROOLS-2207 > URL: https://issues.jboss.org/browse/DROOLS-2207 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.5.0.Final, 7.6.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Critical > > The Validation and Verification panel is missing. The server log contains error [1], however looking into the workbench war, all v&v jars seems to be present. > [1] > ERROR [org.drools.workbench.services.verifier.plugin.backend.VerifierWebWorkerServlet] (default task-119) Failed to load verifier web worker. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2207) Validation and Verification panel is missing

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2207?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2207: ------------------------------------- [~Rikkola] During verification of the 7.5.x PR for RHDM-224 I saw the verification panel on the place, so I believe we can close this one. > Validation and Verification panel is missing > -------------------------------------------- > > Key: DROOLS-2207 > URL: https://issues.jboss.org/browse/DROOLS-2207 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.5.0.Final, 7.6.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Critical > > The Validation and Verification panel is missing. The server log contains error [1], however looking into the workbench war, all v&v jars seems to be present. > [1] > ERROR [org.drools.workbench.services.verifier.plugin.backend.VerifierWebWorkerServlet] (default task-119) Failed to load verifier web worker. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2083) [Guided Decision Table] DSL can not contain $ in the definition

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2083?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-2083. ------------------------------- Resolution: Explained > [Guided Decision Table] DSL can not contain $ in the definition > --------------------------------------------------------------- > > Key: DROOLS-2083 > URL: https://issues.jboss.org/browse/DROOLS-2083 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Fix For: 7.6.0.Final > > > The DSL sentences are defined like: > - [when] *definition* = real rule > If the *definition* contains *$* character, then the DSL sentence can not be used properly in the guided decision table. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8488) Usage of JGroups JDBC_PING attempts to delete row too late

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8488?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-8488. -------------------------------- Resolution: Rejected [~meetoblivion] Reclosing the issue, but just to note, this is an issue tracker, for questions & answers best use the community forums (https://developer.jboss.org/en/wildfly). > Usage of JGroups JDBC_PING attempts to delete row too late > ---------------------------------------------------------- > > Key: WFLY-8488 > URL: https://issues.jboss.org/browse/WFLY-8488 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: John Ament > Assignee: Paul Ferraro > > I was recently working on spinning up a Keycloak cluster. We're deployed to AWS, can't leverage UDP and wanted to have a discovery mechanism that was easy to use, so tried out JDBC_PING. While I got the cluster running, when shutting down a node I would receive an exception on the console when attempting to remove the node from the cluster. It attempts to do a delete on the row in the database after the DataSource has been shut down. > In my setup, I'm pointing JGroups at the same DataSource as Keycloak, I'm not using the properties approach. I can switch to the properties approach, but I would prefer a single pool rather than multiple connections. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9681) Deleting ExampleDS Leaves Remnants in standalone.xml

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-9681?page=com.atlassian.jira.plugin.... ] jaikiran pai commented on WFLY-9681: ------------------------------------ [~cgiddings], does that war (the one in the error message) use JPA (Java Persistence API)? > Deleting ExampleDS Leaves Remnants in standalone.xml > ---------------------------------------------------- > > Key: WFLY-9681 > URL: https://issues.jboss.org/browse/WFLY-9681 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 11.0.0.Final > Reporter: Chris Giddings > Assignee: Stefano Maestri > Priority: Minor > Labels: JDBC > > h2. SUMMARY > When initially installing Wildfly 11.0.0 Final, the installation comes pre-configured with a datasource labeled "Example DS". > When this datasource is deleted, some configuration for it remains in the standalone.xml file for the standalone server mode. > h2. WORKAROUND > Removing this configuration manually and restarting Wildfly in standalone mode resolves the issue. (I tested by searching for "ExampleDS" as a string match in vi and deleting the one line the match found) > h2. BUG JUSTIFICATION > # I would expect anything labeled as "Example" to be deleted by an administrator in most environments > # I would expect deleted items to be fully removed upon deletion so remnant configuration couldn't cause issues with unrelated deployments (i.e. deployments which don't specifically require the deleted item) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8913) It is not possible to add cache store in infinispan subsystem

by Maxim Karavaev (JIRA)

[ https://issues.jboss.org/browse/WFLY-8913?page=com.atlassian.jira.plugin.... ] Maxim Karavaev commented on WFLY-8913: -------------------------------------- Thank you guys! I could add additional workaround - using an offline configuration {noformat} embed-host-controller embed-server {noformat} But in any case, the error message is absolutely confusing and disappointing. > It is not possible to add cache store in infinispan subsystem > ------------------------------------------------------------- > > Key: WFLY-8913 > URL: https://issues.jboss.org/browse/WFLY-8913 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Beta1 > > > Adding cache store to already created cache ends by failure even if it should succeed: > {code} > [standalone@localhost:9990 /] /subsystem=infinispan/cache-container=hibernate/invalidation-cache=foobar/store=STORE:add(class="org.infinispan.configuration.cache.SingleFileStoreConfigurationBuilder") > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.infinispan.cache.store.hibernate.foobar is already registered", > "rolled-back" => true > } > {code} > This is a regression against 7.1.0.DR18. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3512) ClassReflectionIndexUtil does not return default methods from findMethod

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3512?page=com.atlassian.jira.plugi... ] Stuart Douglas updated WFCORE-3512: ----------------------------------- Summary: ClassReflectionIndexUtil does not return default methods from findMethod (was: EJBs can't inherit a JDK8 default method when default implementation is in a third interface) > ClassReflectionIndexUtil does not return default methods from findMethod > ------------------------------------------------------------------------ > > Key: WFCORE-3512 > URL: https://issues.jboss.org/browse/WFCORE-3512 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Daniel Bildhauer > Assignee: Stuart Douglas > Attachments: ejb-in-ear.zip, wildfly-ejb-in-ear-ear.ear > > > Given the following class/interface inheritance structure, the interface method doMagic could not be called from a remote view, even if there is a default implementation as given in the mixin interface. A local call works, but the remote call fails with a message like > {code} > org.jboss.invocation.CannotProceedException: INV000002: Invocation cannot proceed (end of interceptor chain has been hit) > {code} > Example code: > {code} > @Remote > interface MyEJBInterface { > void doMagic(); > } > interface MyEJBMixin extends MyEJBInterface { > default void doMagic() { .... } > } > @Stateless > class MyEJBBean extends MyEJBMixin { > } > {code} > The problem is inside the fix for WFLY-4354 bug, which checks only for the default method implementation in the interface declaring the method the first time but not in other interfaces. > A example is attached and I will submitt a pull request with a fix. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3512) ClassReflectionIndexUtil does not return default methods from findMethod

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3512?page=com.atlassian.jira.plugi... ] Stuart Douglas updated WFCORE-3512: ----------------------------------- Description: This problem is in Wildfly Core, but manifests as an issue with EJB's in WildFly full. Given the following class/interface inheritance structure, the interface method doMagic could not be called from a remote view, even if there is a default implementation as given in the mixin interface. A local call works, but the remote call fails with a message like {code} org.jboss.invocation.CannotProceedException: INV000002: Invocation cannot proceed (end of interceptor chain has been hit) {code} Example code: {code} @Remote interface MyEJBInterface { void doMagic(); } interface MyEJBMixin extends MyEJBInterface { default void doMagic() { .... } } @Stateless class MyEJBBean extends MyEJBMixin { } {code} The problem is inside the fix for WFLY-4354 bug, which checks only for the default method implementation in the interface declaring the method the first time but not in other interfaces. A example is attached and I will submitt a pull request with a fix. was: Given the following class/interface inheritance structure, the interface method doMagic could not be called from a remote view, even if there is a default implementation as given in the mixin interface. A local call works, but the remote call fails with a message like {code} org.jboss.invocation.CannotProceedException: INV000002: Invocation cannot proceed (end of interceptor chain has been hit) {code} Example code: {code} @Remote interface MyEJBInterface { void doMagic(); } interface MyEJBMixin extends MyEJBInterface { default void doMagic() { .... } } @Stateless class MyEJBBean extends MyEJBMixin { } {code} The problem is inside the fix for WFLY-4354 bug, which checks only for the default method implementation in the interface declaring the method the first time but not in other interfaces. A example is attached and I will submitt a pull request with a fix. > ClassReflectionIndexUtil does not return default methods from findMethod > ------------------------------------------------------------------------ > > Key: WFCORE-3512 > URL: https://issues.jboss.org/browse/WFCORE-3512 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Daniel Bildhauer > Assignee: Stuart Douglas > Attachments: ejb-in-ear.zip, wildfly-ejb-in-ear-ear.ear > > > This problem is in Wildfly Core, but manifests as an issue with EJB's in WildFly full. > Given the following class/interface inheritance structure, the interface method doMagic could not be called from a remote view, even if there is a default implementation as given in the mixin interface. A local call works, but the remote call fails with a message like > {code} > org.jboss.invocation.CannotProceedException: INV000002: Invocation cannot proceed (end of interceptor chain has been hit) > {code} > Example code: > {code} > @Remote > interface MyEJBInterface { > void doMagic(); > } > interface MyEJBMixin extends MyEJBInterface { > default void doMagic() { .... } > } > @Stateless > class MyEJBBean extends MyEJBMixin { > } > {code} > The problem is inside the fix for WFLY-4354 bug, which checks only for the default method implementation in the interface declaring the method the first time but not in other interfaces. > A example is attached and I will submitt a pull request with a fix. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 January 2018