March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-391) Support class literals with complex constraints and custom evaluators

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-391?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-391: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1063795|https://bugzilla.redhat.com/show_bug.cgi?id=1063795] from MODIFIED to ON_QA > Support class literals with complex constraints and custom evaluators > --------------------------------------------------------------------- > > Key: DROOLS-391 > URL: https://issues.jboss.org/browse/DROOLS-391 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.1.Final, 6.0.0.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 6.1.0.Beta1 > > > The following is supported, when A is a class name: > {code} Pattern( this op A ) {code} > But the following fails with a CCE > {code} Pattern( this op A || this op B ) {code} > when it tries to resolve A as a field of the class Pattern -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-430) Fails to parse DSL variable definition with single dot regex

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-430?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-430: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1065868|https://bugzilla.redhat.com/show_bug.cgi?id=1065868] from MODIFIED to ON_QA > Fails to parse DSL variable definition with single dot regex > ------------------------------------------------------------ > > Key: DROOLS-430 > URL: https://issues.jboss.org/browse/DROOLS-430 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.1.Final > Reporter: Toshiya Kobayashi > Assignee: Edson Tirelli > Fix For: 6.1.0.Beta1 > > > Drools fails to parse DSL variable definition with single dot regex, where I want one any character. > {noformat} > [then]Log {message:.}=list.add(\"{message}\"); > {noformat} > Error message: > {noformat} > [1,19]: DSL parser error > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-426) Globals can't be used with temporal operators

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-426?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-426: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1064224|https://bugzilla.redhat.com/show_bug.cgi?id=1064224] from MODIFIED to ON_QA > Globals can't be used with temporal operators > --------------------------------------------- > > Key: DROOLS-426 > URL: https://issues.jboss.org/browse/DROOLS-426 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > Fix For: 6.1.0.Beta1 > > > Assuming: > global Date now; > The pattern "Foo( this before now )" will generate various errors. > The reason is that the Global[X]Extractors (X = {"","Date","Number"} > are erroneously declared as self-referential extractors. > If Foo is not an @event, a CCE will arise since the operators will use > "this" rather than the global. Otherwise, the result will be inconsistent -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-364) ClasspathKieProject fails vfs: path for jar deployments and exploded ear

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-364?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-364: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1058254|https://bugzilla.redhat.com/show_bug.cgi?id=1058254] from MODIFIED to ON_QA > ClasspathKieProject fails vfs: path for jar deployments and exploded ear > ------------------------------------------------------------------------ > > Key: DROOLS-364 > URL: https://issues.jboss.org/browse/DROOLS-364 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Environment: JBoss AS 7.1.1 > Reporter: Nicolas-Xavier Vanderlinden > Assignee: Mario Fusco > Fix For: 6.1.0.Beta1 > > Attachments: jbossas-deploy-reproducer.zip, windows-jboss-as-deploy-server.log > > > Drools is not able to load kmodule.xml from an exploded ear. > 17:24:45,116 WARN Unable to load pom.properties tried recursing down from\Project\Geline\jboss-as-7.1.1.Final\standalone\deployments\geline.ear\service-impl-1.4.0-SNAPcontent > null > 17:24:45,116 ERROR Unable to build index of kmodule.xml url=vfs:/E:/Project/Geline/jboss-as-7.1.1.Final/standalone/deployments/geline.ear/service-impl-1.4.0-SNAPSHOT.jar/META-INF/kmodule.xml > null -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-416) Queries do not work with events

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-416?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-416: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1063805|https://bugzilla.redhat.com/show_bug.cgi?id=1063805] from MODIFIED to ON_QA > Queries do not work with events > ------------------------------- > > Key: DROOLS-416 > URL: https://issues.jboss.org/browse/DROOLS-416 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > Fix For: 6.1.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-393) Trait Hierarchy is not rebuilt correctly when merging packages

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-393?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-393: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1063803|https://bugzilla.redhat.com/show_bug.cgi?id=1063803] from MODIFIED to ON_QA > Trait Hierarchy is not rebuilt correctly when merging packages > -------------------------------------------------------------- > > Key: DROOLS-393 > URL: https://issues.jboss.org/browse/DROOLS-393 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.Final, 6.0.1.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > Fix For: 5.5.1.Final, 6.1.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-421) EvaluatorWrapper does not resolve the right handle correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-421?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-421: ------------------------------------------------ Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1063809|https://bugzilla.redhat.com/show_bug.cgi?id=1063809] from MODIFIED to ON_QA > EvaluatorWrapper does not resolve the right handle correctly > ------------------------------------------------------------ > > Key: DROOLS-421 > URL: https://issues.jboss.org/browse/DROOLS-421 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.1.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Beta1 > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > Fix For: 6.1.0.Beta1 > > > The EvaluatorWrapper tries to look up the right handle from the WM, but there may be cases (e.g. when the right input comes from a FROM node) > where the handle is not in the WM, causing a NPE. This causes the right handle to be null, or to be resolved incorrectly. Evaluations are then inconsistent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3042) There should be a warning logged if the default value of node identifier has not been changed.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-3042: ------------------------------------- What I meant, is that we _want_ to support different servers assuming the identity. There is a concept with Narayana that you can run the transaction manager on any machine and point it at an object store (e.g. jdbc one) and give it an identifier to take over from an old server. Narayana itself is pluggable, i.e. it exposes a setXaNodeName method that clients (e.g. subsystem) are free to pass in what they like. The subsystem itself is currently only pluggable in so much as it supports a single implementation that obtains the value to use from the standalone.xml. It would be possible to alter the subsystem to use the IP address etc but as I say, when it boots up on a different machine it will have a different node name so wouldn't take over from the old server. Happy to alter the subsystem but I am not really sure its a good idea to use the IP/port as the ID for the reason I mentioned above. In terms of the alternative (a uuid), I mentioned the reason I was worried to use something random is in case it is lost. Suggestions? > There should be a warning logged if the default value of node identifier has not been changed. > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3042 > URL: https://issues.jboss.org/browse/WFLY-3042 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 8.0.0.Final > Environment: JBoss EAP 6.x > Reporter: Tom Ross > Assignee: Gytis Trikleris > > JBoss EAP instance is using the value of node identifier to identify XA transactions that belong to it. By default this value is set to 1. Now days in most environments there will be multiple JBoss instances sharing XA resources there for it is necessary to set the value of node identifier to a unique value for each instance. This is something that most end users fail to perform. Therefor it would be helpful if a warning message was logged at startup telling the user to do it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3052) Upgrade Hibernate Validator to 5.1.0.Final

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/WFLY-3052?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik updated WFLY-3052: ------------------------------------ Description: Hibernate Validator 5.1.0.Final contains several performance improvements as well as a lower memory footprint. It also fixes a {{NullPointerException}} during server shutdown ([HV-865|https://hibernate.atlassian.net/browse/HV-865]). (was: Hibernate Validator 5.1.0.Final contains several performance improvements as well as a lower memory footprint. It also fixes a {{NullPointerException}} during server shutdown ([HV-865|https://hibernate.atlassian.net/browse/HV-865]) > Upgrade Hibernate Validator to 5.1.0.Final > ------------------------------------------ > > Key: WFLY-3052 > URL: https://issues.jboss.org/browse/WFLY-3052 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Hardy Ferentschik > Assignee: Hardy Ferentschik > Fix For: 8.0.1.Final > > > Hibernate Validator 5.1.0.Final contains several performance improvements as well as a lower memory footprint. It also fixes a {{NullPointerException}} during server shutdown ([HV-865|https://hibernate.atlassian.net/browse/HV-865]). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3052) Upgrade Hibernate Validator to 5.1.0.Final

by Hardy Ferentschik (JIRA)

Hardy Ferentschik created WFLY-3052: --------------------------------------- Summary: Upgrade Hibernate Validator to 5.1.0.Final Key: WFLY-3052 URL: https://issues.jboss.org/browse/WFLY-3052 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 8.0.1.Final Hibernate Validator 5.1.0.Final contains several performance improvements as well as a lower memory footprint. It also fixes a {{NullPointerException}} during server shutdown ([HV-865|https://hibernate.atlassian.net/browse/HV-865] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 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 March 2014