April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3894) Decision Nodes not correctly anchored in Decision Service when using keyboard arrows to move nodes

by Duncan Doyle (Jira)

Duncan Doyle created DROOLS-3894: ------------------------------------ Summary: Decision Nodes not correctly anchored in Decision Service when using keyboard arrows to move nodes Key: DROOLS-3894 URL: https://issues.jboss.org/browse/DROOLS-3894 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.20.0.Final, 7.18.0.Final Environment: RHPAM 7.3.0.GA Reporter: Duncan Doyle Assignee: Michael Anstis If you use a Decision Service, and put Decision Nodes in the service box, the anchoring of the nodes in that service is messed up when you start moving around the nodes using the arrow keys on your keyboard. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11997) A singleton can not add a init-method via ejb-jar.xml descriptor because it fail with Parser Exception

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created WFLY-11997: --------------------------------------- Summary: A singleton can not add a init-method via ejb-jar.xml descriptor because it fail with Parser Exception Key: WFLY-11997 URL: https://issues.jboss.org/browse/WFLY-11997 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 17.0.0.Beta1 Reporter: Wolf-Dieter Fink Assignee: Cheng Fang If a Singelton EJB should be created without annotation and use ejb-jar.xml to declare it this will work for mostly all but not for init-method element. The class is a POJO without annotations, the ejb-jar.xml looks like followed ------ <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_2.xsd" version="3.2"> <enterprise-beans> <session> <ejb-name>StartupSingletonBean</ejb-name> <display-name>JBossInit</display-name> <description>JBoss startup class</description> <ejb-class>org.jboss.wfink.ejb31.singleton.StartupSingletonBean</ejb-class> <session-type>Singleton</session-type> <init-on-startup>true</init-on-startup> <init-method>test23</init-method> --- > this is where the Exception row/col point to <env-entry> <description>an example for a environment value</description> <env-entry-name>myString</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>MyString from the ejb-jar.xml :)</env-entry-value> </env-entry> </session> </enterprise-beans> ..... -------- The Exception is this: 15:27:29,450 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.subunit."simpleEJB31.ear"."ejb.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."simpleEJB31.ear"."ejb.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "ejb.jar" of deployment "simpleEJB31.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748) Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0085: Exception while parsing ejb-jar.xml: /content/simpleEJB31.ear/ejb.jar/META-INF/ejb-jar.xml at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.parseEjbJarXml(EjbJarParsingDeploymentUnitProcessor.java:275) at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:126) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176) ... 8 more Caused by: com.ctc.wstx.exc.WstxParsingException: Received non-all-whitespace CHARACTERS or CDATA event in nextTag(). at [row,col {unknown-source}]: [18,25] at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:621) at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:491) at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:475) at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1224) at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:64) at org.jboss.metadata.ejb.parser.spec.InitMethodMetaDataParser.parse(InitMethodMetaDataParser.java:55) at org.jboss.metadata.ejb.parser.spec.SessionBean30MetaDataParser.processElement(SessionBean30MetaDataParser.java:104) at org.jboss.metadata.ejb.parser.spec.SessionBean31MetaDataParser.processElement(SessionBean31MetaDataParser.java:143) at org.jboss.metadata.ejb.parser.spec.SessionBean32MetaDataParser.processElement(SessionBean32MetaDataParser.java:54) at org.jboss.metadata.ejb.parser.spec.SessionBean32MetaDataParser.processElement(SessionBean32MetaDataParser.java:36) at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:65) at org.jboss.metadata.ejb.parser.spec.SessionBeanMetaDataParser.parse(SessionBeanMetaDataParser.java:81) at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(EnterpriseBeansMetaDataParser.java:87) at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(EnterpriseBeansMetaDataParser.java:39) at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:65) at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(EnterpriseBeansMetaDataParser.java:72) at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(EnterpriseBeansMetaDataParser.java:65) at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(AbstractEjbJarMetaDataParser.java:98) at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(AbstractEjbJarMetaDataParser.java:43) at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:65) at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parseDocument(EjbJarMetaDataParser.java:101) at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parse(EjbJarMetaDataParser.java:51) at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.parseEjbJarXml(EjbJarParsingDeploymentUnitProcessor.java:272) ... 10 more -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11996) A singleton can not add a init-method via ejb-jar.xml descriptor because it fail with Parser Exception

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created WFLY-11996: --------------------------------------- Summary: A singleton can not add a init-method via ejb-jar.xml descriptor because it fail with Parser Exception Key: WFLY-11996 URL: https://issues.jboss.org/browse/WFLY-11996 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 17.0.0.Beta1 Reporter: Wolf-Dieter Fink Assignee: Cheng Fang If a Singelton EJB should be created without annotation and use ejb-jar.xml to declare it this will work for mostly all but not for init-method element. The class is a POJO without annotations, the ejb-jar.xml looks like followed ------ <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_2.xsd" version="3.2"> <enterprise-beans> <session> <ejb-name>StartupSingletonBean</ejb-name> <display-name>JBossInit</display-name> <description>JBoss startup class</description> <ejb-class>org.jboss.wfink.ejb31.singleton.StartupSingletonBean</ejb-class> <session-type>Singleton</session-type> <init-on-startup>true</init-on-startup> <init-method>test23</init-method> --- > this is where the Exception row/col point to <env-entry> <description>an example for a environment value</description> <env-entry-name>myString</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>MyString from the ejb-jar.xml :)</env-entry-value> </env-entry> </session> </enterprise-beans> ..... -------- The Exception is this: 15:27:29,450 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.subunit."simpleEJB31.ear"."ejb.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."simpleEJB31.ear"."ejb.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "ejb.jar" of deployment "simpleEJB31.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748) Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0085: Exception while parsing ejb-jar.xml: /content/simpleEJB31.ear/ejb.jar/META-INF/ejb-jar.xml at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.parseEjbJarXml(EjbJarParsingDeploymentUnitProcessor.java:275) at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:126) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176) ... 8 more Caused by: com.ctc.wstx.exc.WstxParsingException: Received non-all-whitespace CHARACTERS or CDATA event in nextTag(). at [row,col {unknown-source}]: [18,25] at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:621) at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:491) at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:475) at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1224) at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:64) at org.jboss.metadata.ejb.parser.spec.InitMethodMetaDataParser.parse(InitMethodMetaDataParser.java:55) at org.jboss.metadata.ejb.parser.spec.SessionBean30MetaDataParser.processElement(SessionBean30MetaDataParser.java:104) at org.jboss.metadata.ejb.parser.spec.SessionBean31MetaDataParser.processElement(SessionBean31MetaDataParser.java:143) at org.jboss.metadata.ejb.parser.spec.SessionBean32MetaDataParser.processElement(SessionBean32MetaDataParser.java:54) at org.jboss.metadata.ejb.parser.spec.SessionBean32MetaDataParser.processElement(SessionBean32MetaDataParser.java:36) at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:65) at org.jboss.metadata.ejb.parser.spec.SessionBeanMetaDataParser.parse(SessionBeanMetaDataParser.java:81) at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(EnterpriseBeansMetaDataParser.java:87) at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(EnterpriseBeansMetaDataParser.java:39) at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:65) at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(EnterpriseBeansMetaDataParser.java:72) at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(EnterpriseBeansMetaDataParser.java:65) at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(AbstractEjbJarMetaDataParser.java:98) at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(AbstractEjbJarMetaDataParser.java:43) at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:65) at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parseDocument(EjbJarMetaDataParser.java:101) at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parse(EjbJarMetaDataParser.java:51) at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.parseEjbJarXml(EjbJarParsingDeploymentUnitProcessor.java:272) ... 10 more -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3439) Prevent selection of specific cells in Scenario Simulation

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3439?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3439: --------------------------------- Story Points: 5 (was: 3) > Prevent selection of specific cells in Scenario Simulation > ---------------------------------------------------------- > > Key: DROOLS-3439 > URL: https://issues.jboss.org/browse/DROOLS-3439 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.16.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Optional > Labels: drools-tools > Attachments: table.png > > > It would improve the user experience if some of the cells could not be selected at all; specifically cells #, Scenario description, GIVEN, EXPECT, and row numbers, as it should not be possible to change them anyway. > This follows up keyboard shortcuts implemented as part of DROOLS-2932. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3439) Prevent selection of specific cells in Scenario Simulation

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3439?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3439: --------------------------------- Sprint: (was: 2019 Week 14-16) > Prevent selection of specific cells in Scenario Simulation > ---------------------------------------------------------- > > Key: DROOLS-3439 > URL: https://issues.jboss.org/browse/DROOLS-3439 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.16.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Optional > Labels: drools-tools > Attachments: table.png > > > It would improve the user experience if some of the cells could not be selected at all; specifically cells #, Scenario description, GIVEN, EXPECT, and row numbers, as it should not be possible to change them anyway. > This follows up keyboard shortcuts implemented as part of DROOLS-2932. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3893) [Guided Decision Table] Call method on is not generated

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-3893?page=com.atlassian.jira.plugi... ] Toni Rikkola moved RHPAM-2057 to DROOLS-3893: --------------------------------------------- Project: Drools (was: Red Hat Process Automation Manager) Key: DROOLS-3893 (was: RHPAM-2057) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: Guided Decision Table Editor (was: Business Central) Affects Build: (was: CR1) Affects Version/s: (was: 7.3.1.GA) QE Status: NEW > [Guided Decision Table] Call method on is not generated > ------------------------------------------------------- > > Key: DROOLS-3893 > URL: https://issues.jboss.org/browse/DROOLS-3893 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: Regression, drools-tools > > The guided decision tables does not generate the code of *call method on* brl action. User is able to select a method of bound data object, however in the generated source, the *call method on* action is missing. > h4. Reproducer tests > https://github.com/jboss-integration/bxms-qe-tests/pull/2442 > https://github.com/jboss-integration/bxms-qe-tests/pull/2443 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11991) Add Hibernate ORM transformer option to transform any method parameter of type org.hibernate.engine.spi.SessionImplementor

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11991?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-11991: -------------------------------- Fix Version/s: 17.0.0.Beta1 > Add Hibernate ORM transformer option to transform any method parameter of type org.hibernate.engine.spi.SessionImplementor > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11991 > URL: https://issues.jboss.org/browse/WFLY-11991 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 17.0.0.Beta1 > > Attachments: afterchange.zip, beforechange.zip > > > The idea is to transform any class method parameter of type org.hibernate.engine.spi.SessionImplementor, in user application, to instead use type org.hibernate.engine.spi.SharedSessionContractImplementor. > The test case (change) is for this enhancement is [https://github.com/simkam/wildfly/compare/hibernate_transformer]. > The test case change is adding an internalNullSafeGet method that should also be transformed to use the SharedSessionContractImplementor type but was not, which led to an application failure with code: > {code} > public Object nullSafeGet(ResultSet rs, String[] names, SessionImplementor session, Object owner) throws HibernateException, SQLException { > return internalNullSafeGet(rs, names, session, owner); > } > private Object internalNullSafeGet(ResultSet rs, String[] names, SessionImplementor session, Object owner) throws HibernateException, SQLException { > internalSessionImplementorUsingMethod(session); > session.isTransactionInProgress(); > int result = rs.getInt( names[0] ); > if ( rs.wasNull() ) return null; > return State.values()[result]; > } > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3389) Create a "runtime" module for scenario with only the code required by Junit runner

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3389?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3389: --------------------------------- Sprint: (was: 2019 Week 14-16) > Create a "runtime" module for scenario with only the code required by Junit runner > ---------------------------------------------------------------------------------- > > Key: DROOLS-3389 > URL: https://issues.jboss.org/browse/DROOLS-3389 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > Create a module with the "runtime" code required by the junit runner to be able to remove workbench dependent code from user project dependencies. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3730) Add support to DMN constraints on inputs (report input validation errors)

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3730?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3730: --------------------------------- Sprint: 2019 Week 11-13 (was: 2019 Week 11-13, 2019 Week 14-16) > Add support to DMN constraints on inputs (report input validation errors) > ------------------------------------------------------------------------- > > Key: DROOLS-3730 > URL: https://issues.jboss.org/browse/DROOLS-3730 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > See this example https://github.com/kiegroup/drools/compare/master...tarilabs:tarilabs-201... > and try with a value out of the domain ranga [0..100]. > when a Decision or any evaluation which depends on such InputData is triggered, an error message like the following is reported > ```Error while evaluating node 'my decision' for dependency 'my input': the dependency value '999' is not allowed by the declared type (DMNType{ http://www.trisotech.com/definitions/_7ab67159-21c7-4985-91fc-f0d0174898db : tNumber0100 })``` -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-674) Identify produckey and product line for Istio

by Prachi Yadav (Jira)

[ https://issues.jboss.org/browse/SWSQE-674?page=com.atlassian.jira.plugin.... ] Prachi Yadav resolved SWSQE-674. -------------------------------- Resolution: Done > Identify produckey and product line for Istio > --------------------------------------------- > > Key: SWSQE-674 > URL: https://issues.jboss.org/browse/SWSQE-674 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Prachi Yadav > Priority: Major > Labels: pqi > > the produckey for Istio > also which product line its map to? what is product hierarchy for these two products? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 April 2019