August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9221) Apache Avro version not compatible with Hibernate Search requirements

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-9221?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on WFLY-9221: --------------------------------------- {quote}Or is 1.8.1 known to fail with Search?{quote} Avro 1.8.1 is known to fail with Search. > Apache Avro version not compatible with Hibernate Search requirements > --------------------------------------------------------------------- > > Key: WFLY-9221 > URL: https://issues.jboss.org/browse/WFLY-9221 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Sanne Grinovero > Assignee: Scott Marlow > Priority: Blocker > Fix For: 11.0.0.CR1 > > > The version of {{Apache Avro}} was updated and is now no longer compatible with {{Hibernate Search}}, which is as far as I know the only user for it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9221) Apache Avro version not compatible with Hibernate Search requirements

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-9221?page=com.atlassian.jira.plugin.... ] Sanne Grinovero reassigned WFLY-9221: ------------------------------------- Assignee: Sanne Grinovero (was: Scott Marlow) > Apache Avro version not compatible with Hibernate Search requirements > --------------------------------------------------------------------- > > Key: WFLY-9221 > URL: https://issues.jboss.org/browse/WFLY-9221 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Blocker > Fix For: 11.0.0.CR1 > > > The version of {{Apache Avro}} was updated and is now no longer compatible with {{Hibernate Search}}, which is as far as I know the only user for it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9221) Apache Avro version not compatible with Hibernate Search requirements

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9221?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-9221: ------------------------------------ Is Avro 1.8.1 just not tested with Search? Or is 1.8.1 known to fail with Search? > Apache Avro version not compatible with Hibernate Search requirements > --------------------------------------------------------------------- > > Key: WFLY-9221 > URL: https://issues.jboss.org/browse/WFLY-9221 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Sanne Grinovero > Assignee: Scott Marlow > Priority: Blocker > Fix For: 11.0.0.CR1 > > > The version of {{Apache Avro}} was updated and is now no longer compatible with {{Hibernate Search}}, which is as far as I know the only user for it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9221) Apache Avro version not compatible with Hibernate Search requirements

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9221?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-9221: ------------------------------------ [WFLY-7908] upgraded from 1.7.6 to 1.8.1 back in January. > Apache Avro version not compatible with Hibernate Search requirements > --------------------------------------------------------------------- > > Key: WFLY-9221 > URL: https://issues.jboss.org/browse/WFLY-9221 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Sanne Grinovero > Assignee: Scott Marlow > Priority: Blocker > Fix For: 11.0.0.CR1 > > > The version of {{Apache Avro}} was updated and is now no longer compatible with {{Hibernate Search}}, which is as far as I know the only user for it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9221) Apache Avro version not compatible with Hibernate Search requirements

by Sanne Grinovero (JIRA)

Sanne Grinovero created WFLY-9221: ------------------------------------- Summary: Apache Avro version not compatible with Hibernate Search requirements Key: WFLY-9221 URL: https://issues.jboss.org/browse/WFLY-9221 Project: WildFly Issue Type: Bug Components: JPA / Hibernate Reporter: Sanne Grinovero Assignee: Scott Marlow Priority: Blocker Fix For: 11.0.0.CR1 The version of {{Apache Avro}} was updated and is now no longer compatible with {{Hibernate Search}}, which is as far as I know the only user for it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1695) When unmarshalling, the reader returns attributePrefix as null on IBM JDK

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1695?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-1695: --------------------------------------- Merged on both master and 7.3.x. > When unmarshalling, the reader returns attributePrefix as null on IBM JDK > ------------------------------------------------------------------------- > > Key: DROOLS-1695 > URL: https://issues.jboss.org/browse/DROOLS-1695 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Matteo Mortari > Fix For: 7.3.0.Final > > > When running test UnmarshalMarshalTest, a lot of tests fail with similar output [1]. It looks like it is related to getting nulls here when reading attribute prefixes [2]. > [1] https://gist.github.com/baldimir/bbb58fb1dfb3df41b74c012d54895ce9 > [2] https://github.com/kiegroup/drools/blob/b007d9d50d5fa9f7eb4c645f298765dab... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1577) Support FIFO queue for agenda group focus

by Russell Morrisey (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1577?page=com.atlassian.jira.plugi... ] Russell Morrisey commented on DROOLS-1577: ------------------------------------------ Edson, I am having a hard time understanding the usage of the ruleflow-group feature. From the docs, it looks like this feature is deprecated? https://docs.jboss.org/drools/release/6.5.0.Final/drools-docs/html_single... In the Workbench, there is no option to create a rule flow file, and in KIE Server, it seems like there is no longer a command to activate a ruleflow group. > Support FIFO queue for agenda group focus > ----------------------------------------- > > Key: DROOLS-1577 > URL: https://issues.jboss.org/browse/DROOLS-1577 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.5.0.Final > Reporter: Russell Morrisey > Assignee: Mario Fusco > > When setting up the ordering of agenda groups, the framework should support adding them in the order they are supposed to be executed. > Ex: > agenda.getAgendaGroup( "calculation" ).setQueue(); > agenda.getAgendaGroup( "report" ).setQueue(); > Or, even better: > agenda.addAgendaGroupsToQueue("calculation", "report"); > And: > agenda.addAgendaGroupsToQueue(agenda.getAgendaGroup( "calculation" ), agenda.getAgendaGroup( "report" )) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1672) "not" in variable name doesn't work

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1672?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-1672: --------------------------------------- I investigated this problem. It happens on the last reference to the variable name: {code}.bob is not exactly 18{code} The problem is that today the parser uses dynamic resolution to parse this variable name, and we can't allow keywords in name parts for dynamic resolution. There is no easy fix for this until we get some kind of alternative for the dynamic resolution. I will postpone this ticket until either DMN 1.2 defines a context free grammar or we have an alternative for the dynamic resolution. > "not" in variable name doesn't work > ----------------------------------- > > Key: DROOLS-1672 > URL: https://issues.jboss.org/browse/DROOLS-1672 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Edson Tirelli > Labels: reported-by-qe > Fix For: 7.3.0.Final > > > When trying this test case: > {code}{ is not exactly 18 : != 18, bob is not exactly 18 : is not exactly 18(16) }.bob is not exactly 18"{code} > the parser fails like this [1] > [1] https://gist.github.com/baldimir/7c13b9c76087d44f95802ded8b72877f > Will provide a PR with a reproducer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1672) "not" in variable name doesn't work

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1672?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1672: ---------------------------------- Description: When trying this test case: {code}{ is not exactly 18 : != 18, bob is not exactly 18 : is not exactly 18(16) }.bob is not exactly 18"{code} the parser fails like this [1] [1] https://gist.github.com/baldimir/7c13b9c76087d44f95802ded8b72877f Will provide a PR with a reproducer. was: When trying this test case: { is not exactly 18 : != 18, bob is not exactly 18 : is not exactly 18(16) }.bob is not exactly 18" the parser fails like this [1] [1] https://gist.github.com/baldimir/7c13b9c76087d44f95802ded8b72877f Will provide a PR with a reproducer. > "not" in variable name doesn't work > ----------------------------------- > > Key: DROOLS-1672 > URL: https://issues.jboss.org/browse/DROOLS-1672 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Edson Tirelli > Labels: reported-by-qe > Fix For: 7.3.0.Final > > > When trying this test case: > {code}{ is not exactly 18 : != 18, bob is not exactly 18 : is not exactly 18(16) }.bob is not exactly 18"{code} > the parser fails like this [1] > [1] https://gist.github.com/baldimir/7c13b9c76087d44f95802ded8b72877f > Will provide a PR with a reproducer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-845) @KSession throws exception when using kmodule in separate jar

by José Filipe Neis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-845?page=com.atlassian.jira.plugin... ] José Filipe Neis commented on DROOLS-845: ----------------------------------------- Checked the source code and the problem is happening because AnnotationsPostProcessor assumes there is always a ReleaseId specified. Just created a [pull request|AnnotationsPostProcessor] for 7.2.x. > @KSession throws exception when using kmodule in separate jar > ------------------------------------------------------------- > > Key: DROOLS-845 > URL: https://issues.jboss.org/browse/DROOLS-845 > Project: Drools > Issue Type: Bug > Components: core engine, decision tables, kie server > Affects Versions: 6.2.0.Final > Environment: windows 7 > Reporter: lucio piccoli > Assignee: Mario Fusco > Attachments: drools-bug.zip > > > i am using drools with a kmodules.xml and decisiontable inside a separate jar file. when i attempt to bind the @KSession to the spring application context it throws an nullpointer exception deep inside the annotation. > org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'oft.onlineservice.business.FeeRulesEngineTest': Injection of kie dependencies failed; nested exception is java.lang.NullPointerException > at org.kie.spring.annotations.AnnotationsPostProcessor.postProcessPropertyValues(AnnotationsPostProcessor.java:109) > using a simple junittest shows the problem. > public class FeeRulesEngineTest { > @KSession( "ksession1") > private StatelessKieSession ksession; > @KBase("feeDecisionTable") > private KieBase kbase; > the kmodule.xml > <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule"> > <kbase name="feeDecisionTable" packages="oft.rulesengine" default="true"> > <ksession name="ksession1" type="stateless" default="true" > > </ksession> > </kbase> > </kmodule> > the spring config is using the annonation postprocessor. > <kie:import /> > <bean id="kiePostProcessor" > class="org.kie.spring.annotations.KModuleAnnotationPostProcessor"/> > > my curent work around to is to use @Autowire for the KSession and KBase. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 August 2017