June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2615) Executable model - tests from package "integrationtests.operators" fail when run with executable model

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2615: ----------------------------------- Summary: Executable model - tests from package "integrationtests.operators" fail when run with executable model Key: DROOLS-2615 URL: https://issues.jboss.org/browse/DROOLS-2615 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.7.0.Final Reporter: Tibor Zimányi Assignee: Luca Molteni When running tests from package org.drools.compiler.integrationtests.operators [1] with executable model, many of them fail (~120 out of ~520). To run the tests with the model, I moved the tests to a separate module in this PR [2], please check the PR description to see how to run them. [1] https://github.com/kiegroup/drools/tree/d7ad4fb31647b5295c3cbc0321f0d8f89... [2] https://github.com/kiegroup/drools/pull/1901 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2588) Kie maven plugin does not build kiebase on windows

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2588?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2588. --------------------------------- Resolution: Done Fixed by https://issues.jboss.org/browse/DROOLS-2339 > Kie maven plugin does not build kiebase on windows > -------------------------------------------------- > > Key: DROOLS-2588 > URL: https://issues.jboss.org/browse/DROOLS-2588 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 7.7.0.Final > Environment: Windows 10 > Reporter: Viacheslav Krot > Assignee: Mario Fusco > Attachments: net_tst.zip > > > Hi, > In drools 7.7.0.Final maven plugin suddenly stopped building kie base and thus verifying DRL files during packaging. It does not find the resources at all, during build I see warning: > {noformat} > [WARNING] No files found for KieBase defaultKieBase > {noformat} > I attach a simple project with error in DRL, it should not be built, but with 7.7.0.Final on Windows the build is successful. Though same project fails on macos or linux (as expected). And even 7.6.0 on Windows produces error > {noformat} > [ERROR] Unable to build KieBaseModel:defaultKieBase > Unable to resolve ObjectType 'List2' : [Rule name='all_import'] > {noformat} > Only windows is affected, builds on linux and macos work as expected - they fail (because there is an error in DRL file), only windows with 7.7.0 plugin pass because it does not see the resources. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2611) Drools7.7 workbench Import project from git error

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2611?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2611. --------------------------------- Resolution: Cannot Reproduce > Drools7.7 workbench Import project from git error > -------------------------------------------------- > > Key: DROOLS-2611 > URL: https://issues.jboss.org/browse/DROOLS-2611 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 7.7.0.Final > Reporter: jiahuiyun jiahuiyun > Assignee: Mario Fusco > Priority: Critical > Attachments: image-2018-06-05-15-41-28-768.png > > > the project is added on workbench,I delete it,then import it,but failed. > I import project from github，failed too. > need set ssh key?? > !image-2018-06-05-15-41-28-768.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3907) Rename wildfly-component-matrix-builder to wildfly-core-component-matrix-builder to be able to import it into Eclipse

by Peter Palaga (JIRA)

Peter Palaga created WFCORE-3907: ------------------------------------ Summary: Rename wildfly-component-matrix-builder to wildfly-core-component-matrix-builder to be able to import it into Eclipse Key: WFCORE-3907 URL: https://issues.jboss.org/browse/WFCORE-3907 Project: WildFly Core Issue Type: Task Reporter: Peter Palaga Assignee: Peter Palaga A Maven module with {{wildfly-component-matrix-builder}} name is currently available both in WF Core and in WF. Therefore it is not possible to import both into Eclipse (with default settings). We should use {{wildfly-core-component-matrix-builder}} in WF Core. A PR follows. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-41) Implement HOME and END keys

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFWIP-41?page=com.atlassian.jira.plugin.s... ] Jean-Francois Denise commented on WFWIP-41: ------------------------------------------- Thank-you, branch updated. > Implement HOME and END keys > --------------------------- > > Key: WFWIP-41 > URL: https://issues.jboss.org/browse/WFWIP-41 > Project: WildFly WIP > Issue Type: Task > Reporter: Erich Duda > Assignee: Jean-Francois Denise > > This is related to WFCORE-3568. Based on [proposal|https://github.com/wildfly/wildfly-proposals/pull/48/files] the scrolling feature should support also HOME and END keys. However they are not implemented yet so I've created this Jira as reminder. > In the analysis the keys don't have any one char alternatives which help at testing. Please introduce them as well. Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2556) Not possible to deploy kjar with rule including timer

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2556?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2556. --------------------------------- Resolution: Won't Fix > Not possible to deploy kjar with rule including timer > ----------------------------------------------------- > > Key: DROOLS-2556 > URL: https://issues.jboss.org/browse/DROOLS-2556 > Project: Drools > Issue Type: Bug > Affects Versions: 7.7.0.Final > Reporter: Anton Giertli > Assignee: Mario Fusco > Attachments: kjar.zip, reproducer.zip > > > When KJAR contains a rule with timer: > {code:java} > package com.sample; > > rule "Timer to stop long running rules" > timer (int: 150s) > ruleflow-group "whatever" > salience 99 > when > then > System.err.println("**** Exit rule engine ****"); > drools.halt(); > end > {code} > It's not possible to deploy it with KIE Services API > it fails with this error: > https://gist.github.com/agiertli/12fb71e3103dbf493308dc263fdc4607 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10513) Getting JTA Datasource (Wildfly 13)

by David Tierens (JIRA)

[ https://issues.jboss.org/browse/WFLY-10513?page=com.atlassian.jira.plugin... ] David Tierens updated WFLY-10513: --------------------------------- Description: In Wildfly 12 it ,was possible to get the DataSource via : {code:java} @ApplicationScoped public class ExamplePersistenceContextConfiguration { @PersistenceContext(unitName = "examplePersistenceUnit") @Produces private EntityManager entityManager; @Produces public DataSource getDataSource() { EntityManagerFactory entityManagerFactory = entityManager.getEntityManagerFactory(); Map<String, Object> properties = entityManagerFactory.getProperties(); return (DataSource) properties.get("javax.persistence.jtaDataSource"); } @Produces public SessionFactory getSessionFactory() { Session session = entityManager.unwrap(Session.class); return session.getSessionFactory(); } } {code} Currently it's returning null in Wildfly 13, however : {code:java} (DataSource) properties.get("hibernate.connection.datasource"); {code} does work (instead of : {code:java} (DataSource) properties.get("javax.persistence.jtaDataSource") {code} Persistence.XML : {code:xml} // Some comments here public String getFoo() { return foo; } <?xml version="1.0" encoding="UTF-8"?> <persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd" version="2.1">  <persistence-unit name="examplePersistenceUnit" transaction-type="JTA"> <provider>org.hibernate.jpa.HibernatePersistenceProvider</provider> <jta-data-source>jdbc/ExampleXADataSource</jta-data-source> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.Oracle10gDialect"/> <property name="hibernate.show_sql" value="true"/> <property name="hibernate.order_inserts" value="true"/> <property name="hibernate.jdbc.wrap_result_sets" value="true"/> <property name="hibernate.integration.envers.enabled" value="false"/> </properties> </persistence-unit> </persistence> {code} Is there any way to get it via the properties.get("javax.persistence.jtaDataSource") and not via Hibernate ? Thanks in advance, David was: In Wildfly 12 it ,was possible to get the DataSource via : {code:java} @ApplicationScoped public class ExamplePersistenceContextConfiguration { @PersistenceContext(unitName = "examplePersistenceUnit") @Produces private EntityManager entityManager; @Produces public DataSource getDataSource() { EntityManagerFactory entityManagerFactory = entityManager.getEntityManagerFactory(); Map<String, Object> properties = entityManagerFactory.getProperties(); return (DataSource) properties.get("javax.persistence.jtaDataSource"); } @Produces public SessionFactory getSessionFactory() { Session session = entityManager.unwrap(Session.class); return session.getSessionFactory(); } } {code} Currently it's returning null in Wildfly 13, however : (DataSource) properties.get("hibernate.connection.datasource"); does work (instead of (DataSource) properties.get("javax.persistence.jtaDataSource") Persistence.XML : {code:xml} // Some comments here public String getFoo() { return foo; } <?xml version="1.0" encoding="UTF-8"?> <persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd" version="2.1">  <persistence-unit name="examplePersistenceUnit" transaction-type="JTA"> <provider>org.hibernate.jpa.HibernatePersistenceProvider</provider> <jta-data-source>jdbc/ExampleXADataSource</jta-data-source> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.Oracle10gDialect"/> <property name="hibernate.show_sql" value="true"/> <property name="hibernate.order_inserts" value="true"/> <property name="hibernate.jdbc.wrap_result_sets" value="true"/> <property name="hibernate.integration.envers.enabled" value="false"/> </properties> </persistence-unit> </persistence> {code} Is there any way to get it via the properties.get("javax.persistence.jtaDataSource") and not via Hibernate ? Thanks in advance, David > Getting JTA Datasource (Wildfly 13) > ----------------------------------- > > Key: WFLY-10513 > URL: https://issues.jboss.org/browse/WFLY-10513 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JPA / Hibernate > Affects Versions: 13.0.0.Final > Reporter: David Tierens > Assignee: Martin Kouba > Priority: Minor > > In Wildfly 12 it ,was possible to get the DataSource via : > > {code:java} > @ApplicationScoped > public class ExamplePersistenceContextConfiguration { > > @PersistenceContext(unitName = "examplePersistenceUnit") > @Produces > private EntityManager entityManager; > > @Produces > public DataSource getDataSource() { > EntityManagerFactory entityManagerFactory = entityManager.getEntityManagerFactory(); > Map<String, Object> properties = entityManagerFactory.getProperties(); > return (DataSource) properties.get("javax.persistence.jtaDataSource"); > } > > @Produces > public SessionFactory getSessionFactory() { > Session session = entityManager.unwrap(Session.class); > return session.getSessionFactory(); > } > } > {code} > > Currently it's returning null in Wildfly 13, however : > {code:java} > (DataSource) properties.get("hibernate.connection.datasource"); > {code} > does work (instead of : > {code:java} > (DataSource) properties.get("javax.persistence.jtaDataSource") > {code} > > Persistence.XML : > {code:xml} > // Some comments here > public String getFoo() > { > return foo; > } > <?xml version="1.0" encoding="UTF-8"?> > <persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence > http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd" > version="2.1"> >  > <persistence-unit name="examplePersistenceUnit" transaction-type="JTA"> > <provider>org.hibernate.jpa.HibernatePersistenceProvider</provider> > <jta-data-source>jdbc/ExampleXADataSource</jta-data-source> > <properties> > <property name="hibernate.dialect" value="org.hibernate.dialect.Oracle10gDialect"/> > <property name="hibernate.show_sql" value="true"/> > <property name="hibernate.order_inserts" value="true"/> > <property name="hibernate.jdbc.wrap_result_sets" value="true"/> > <property name="hibernate.integration.envers.enabled" value="false"/> > </properties> > </persistence-unit> > </persistence> > {code} > > Is there any way to get it via the properties.get("javax.persistence.jtaDataSource") and not via Hibernate ? > > Thanks in advance, > David -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10513) Getting JTA Datasource (Wildfly 13)

by David Tierens (JIRA)

David Tierens created WFLY-10513: ------------------------------------ Summary: Getting JTA Datasource (Wildfly 13) Key: WFLY-10513 URL: https://issues.jboss.org/browse/WFLY-10513 Project: WildFly Issue Type: Bug Components: CDI / Weld, JPA / Hibernate Affects Versions: 13.0.0.Final Reporter: David Tierens Assignee: Martin Kouba Priority: Minor In Wildfly 12 it ,was possible to get the DataSource via : {code:java} @ApplicationScoped public class ExamplePersistenceContextConfiguration { @PersistenceContext(unitName = "examplePersistenceUnit") @Produces private EntityManager entityManager; @Produces public DataSource getDataSource() { EntityManagerFactory entityManagerFactory = entityManager.getEntityManagerFactory(); Map<String, Object> properties = entityManagerFactory.getProperties(); return (DataSource) properties.get("javax.persistence.jtaDataSource"); } @Produces public SessionFactory getSessionFactory() { Session session = entityManager.unwrap(Session.class); return session.getSessionFactory(); } } {code} Currently it's returning null in Wildfly 13, however : (DataSource) properties.get("hibernate.connection.datasource"); does work (instead of (DataSource) properties.get("javax.persistence.jtaDataSource") Persistence.XML : {code:xml} // Some comments here public String getFoo() { return foo; } <?xml version="1.0" encoding="UTF-8"?> <persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd" version="2.1">  <persistence-unit name="examplePersistenceUnit" transaction-type="JTA"> <provider>org.hibernate.jpa.HibernatePersistenceProvider</provider> <jta-data-source>jdbc/ExampleXADataSource</jta-data-source> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.Oracle10gDialect"/> <property name="hibernate.show_sql" value="true"/> <property name="hibernate.order_inserts" value="true"/> <property name="hibernate.jdbc.wrap_result_sets" value="true"/> <property name="hibernate.integration.envers.enabled" value="false"/> </properties> </persistence-unit> </persistence> {code} Is there any way to get it via the properties.get("javax.persistence.jtaDataSource") and not via Hibernate ? Thanks in advance, David -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2614) Remove SNAPSHOT versions from tests where possible

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2614: ------------------------------------- Summary: Remove SNAPSHOT versions from tests where possible Key: DROOLS-2614 URL: https://issues.jboss.org/browse/DROOLS-2614 Project: Drools Issue Type: Task Components: core engine Affects Versions: 7.7.0.Final Reporter: Tibor Zimányi Assignee: Tibor Zimányi Recent fix fixed SNAPSHOT artifact resolution [1], however this change slowed down some tests, because they use artifical ReleaseIds that contain SNAPSHOT version. These SNAPSHOTs should be changed to a non-SNAPSHOT ones where possible. [1] https://issues.jboss.org/browse/DROOLS-2591 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-277) New test case: invalid login test

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-277?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-277. ----------------------------------- Resolution: Done added in https://github.com/Kiali-QE/kiali-qe-python/pull/49 > New test case: invalid login test > --------------------------------- > > Key: SWSQE-277 > URL: https://issues.jboss.org/browse/SWSQE-277 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > add new test case to validate invalid login -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2018