February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2589) ReadTransformedResourceOperation should set include-defaults=false when calling read-resource

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2589?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-2589: ---------------------------------------- I'm looking at making this a configurable item. In a case where a new attribute is added, with a default, but it can be discarded if undefined *by the user*, the current test infrastructure can't cope. The fact the user wasn't the one who set the default values ends up being lost and tests fail. > ReadTransformedResourceOperation should set include-defaults=false when calling read-resource > --------------------------------------------------------------------------------------------- > > Key: WFLY-2589 > URL: https://issues.jboss.org/browse/WFLY-2589 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Kabir Khan > > This needs further investigation, but it seems to mean that we have a lot of ModelFixers used in the wrong situation. i.e. the when transforming resources, attributes that should be undefined reach the transformers as defined with the default value set instead. > This needs a bit of thinking about [~jmesnil] mentioned this a few weeks ago as well. I'd like to see if he remembers before fixing -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2589) ReadTransformedResourceOperation should set include-defaults=false when calling read-resource

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2589?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-2589: -------------------------------------- Assignee: Brian Stansberry (was: Kabir Khan) > ReadTransformedResourceOperation should set include-defaults=false when calling read-resource > --------------------------------------------------------------------------------------------- > > Key: WFLY-2589 > URL: https://issues.jboss.org/browse/WFLY-2589 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Brian Stansberry > > This needs further investigation, but it seems to mean that we have a lot of ModelFixers used in the wrong situation. i.e. the when transforming resources, attributes that should be undefined reach the transformers as defined with the default value set instead. > This needs a bit of thinking about [~jmesnil] mentioned this a few weeks ago as well. I'd like to see if he remembers before fixing -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-89) Spurious server dirs created when directory-grouping="by-type" is set

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-89?page=com.atlassian.jira.plugin.sy... ] James Perkins updated WFLY-89: ------------------------------ Fix Version/s: (was: 8.0.0.CR1) (was: 8.0.0.Final) > Spurious server dirs created when directory-grouping="by-type" is set > --------------------------------------------------------------------- > > Key: WFLY-89 > URL: https://issues.jboss.org/browse/WFLY-89 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: James Perkins > Priority: Minor > > Add directory-grouping="by-type" to the <host><servers> element in the stock host.xml and run domain.sh. The following empty directories are created: > $JBOSS_HOME/domain/servers/server-one > $JBOSS_HOME/domain/servers/server-two > The content that would normally be in those dirs if directory-grouping="by-type" wasn't set appears to all be going where it should (e.g. under domain/data, domain/log etc) so the only issue here is the empty directories. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2187) Make module and class writable attributes

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2187?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-2187: -------------------------------- Fix Version/s: 8.0.1.Final > Make module and class writable attributes > ----------------------------------------- > > Key: WFLY-2187 > URL: https://issues.jboss.org/browse/WFLY-2187 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 8.0.1.Final > > > The {{class}} and {{module}} attributes on a {{custom-handler}} should be made writable. If changed the logmanager config API will just need to remove the original handler and add a new one. This may also need to check whether the handler is attached to a logger or other handlers. > If the add/remove won't work from the logmanager, then a {{reload}} should be required. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2187) Make module and class writable attributes

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2187?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-2187: -------------------------------- Fix Version/s: (was: 8.0.0.Final) > Make module and class writable attributes > ----------------------------------------- > > Key: WFLY-2187 > URL: https://issues.jboss.org/browse/WFLY-2187 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > The {{class}} and {{module}} attributes on a {{custom-handler}} should be made writable. If changed the logmanager config API will just need to remove the original handler and add a new one. This may also need to check whether the handler is attached to a logger or other handlers. > If the add/remove won't work from the logmanager, then a {{reload}} should be required. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-230) Add @ValidIdRange annotation to message loggers and message bundles

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-230?page=com.atlassian.jira.plugin.s... ] James Perkins updated WFLY-230: ------------------------------- Fix Version/s: (was: 8.0.0.CR1) (was: 8.0.0.Final) > Add @ValidIdRange annotation to message loggers and message bundles > ------------------------------------------------------------------- > > Key: WFLY-230 > URL: https://issues.jboss.org/browse/WFLY-230 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > > A new release of the logging tooling will include a {{@ValidIdRange}} annotation. This will help document which id ranges allowed as well as provide compile time validation. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2309) Fix description resolvers for logging extension

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2309?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-2309: -------------------------------- Fix Version/s: (was: 8.0.0.Final) > Fix description resolvers for logging extension > ----------------------------------------------- > > Key: WFLY-2309 > URL: https://issues.jboss.org/browse/WFLY-2309 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > The logging extensions description resolver is a mess. In some cases doesn't allow the same attribute name to be used resources and get a different description. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2264) Property expressions resolved before the PatternFormatter can resolve them

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2264?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-2264: -------------------------------- Fix Version/s: (was: 8.0.0.Final) > Property expressions resolved before the PatternFormatter can resolve them > -------------------------------------------------------------------------- > > Key: WFLY-2264 > URL: https://issues.jboss.org/browse/WFLY-2264 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > System property expressions defined in {{pattern-formatter}} or {{formatter}} attributes are processed by the {{AttributeDefinition}} rather than left and processed by the {{PatternFormatter}}. This results in invalid pattern values being used and stops the server from logging. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-388) Inconsistent behavior of "contains" operator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-388?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-388: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1060033|https://bugzilla.redhat.com/show_bug.cgi?id=1060033] from ASSIGNED to MODIFIED > Inconsistent behavior of "contains" operator > -------------------------------------------- > > Key: DROOLS-388 > URL: https://issues.jboss.org/browse/DROOLS-388 > 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 > Priority: Minor > Fix For: 6.1.0.Beta1 > > > The compiler accepts constraints such as > {code} > Person( fullName contains 'Jr' ) // should be fullName.contains('Jr') > {code} > Interestingly, MVEL evaluates it as the string operation "contains", but > once the constraint is jitted it is again evaluated as a collection operator. > That is, a rule such as: > {code} > when > $s : String( this contains "foo" ) > then > {code} > with inputs "foo1" .. "fooN" effectively fires an unpredictable number of times before starting to fail silently -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-404) NoClassDefFoundError happens when using "function"s in drl

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-404?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-404: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1060218|https://bugzilla.redhat.com/show_bug.cgi?id=1060218] from ASSIGNED to MODIFIED > NoClassDefFoundError happens when using "function"s in drl > ---------------------------------------------------------- > > Key: DROOLS-404 > URL: https://issues.jboss.org/browse/DROOLS-404 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final, 6.0.1.Final > Environment: The base environment is the same as DefaultKieSessionExample. > See attached maven project for details. > Reporter: Nandor Galambosi > Assignee: Mario Fusco > Fix For: 6.1.0.Beta1 > > Attachments: noclassdeffound.zip > > > If I reuse a KieSession for multiple times, it seems to forget about the function defined in the DRL file. > DRL: > {noformat} > package org.drools.example.api.defaultkiesession.Hal1 > import org.drools.example.api.defaultkiesession.Message > function boolean alwaysTrue() { > return true; > } > rule "rule 1" when > m : Message( ) > then > retract(m); > end > rule "rule 2" when > Message( alwaysTrue(), text == "Hello, HAL. Do you read me, HAL?" ) > then > insert( new Message("HAL", "Dave. I read you." ) ); > end > {noformat} > Java code: > {noformat} > package org.drools.example.api.defaultkiesession; > import org.kie.api.KieServices; > import org.kie.api.runtime.KieContainer; > import org.kie.api.runtime.KieSession; > public class DefaultKieSessionExample > { > static int counter = 0; > public void failCase1() > { > KieServices ks = KieServices.Factory.get(); > KieContainer kContainer = ks.getKieClasspathContainer(); > KieSession kSession = kContainer.newKieSession(); > for( counter = 0; counter < 10000; ++counter) { > kSession.insert(new Message("Dave", "Hello, HAL. Do you read me, HAL?")); > kSession.fireAllRules(); > if (kSession.getFactCount() != 0) { > System.err.println("error"); > } > } > } > public static void main(String[] args) > { > try { > DefaultKieSessionExample defaultKieSessionExample = new DefaultKieSessionExample(); > defaultKieSessionExample.failCase1(); > } catch (NoClassDefFoundError error) { > System.err.println("Failed after "+counter+" testcases"); > error.printStackTrace(); > } > } > } > {noformat} > Runs fine for some iterations, and after a while an exception happens: > {noformat} > java.lang.NoClassDefFoundError: org/drools/example/api/defaultkiesession/Hal1/AlwaysTrue > at ConditionEvaluator19fe4e382c304060b0046f5cdc6a59fa.evaluate(Unknown Source) > at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:217) > at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:174) > at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:134) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:502) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:387) > at org.drools.core.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:288) > at org.drools.core.reteoo.EntryPointNode.assertObject(EntryPointNode.java:260) > at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:360) > at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:279) > at org.drools.core.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:1148) > at org.drools.core.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:1092) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:308) > at org.drools.example.api.defaultkiesession.DefaultKieSessionExample.failCase1(DefaultKieSessionExample.java:17) > at org.drools.example.api.defaultkiesession.DefaultKieSessionExample.main(DefaultKieSessionExample.java:29) > Caused by: java.lang.ClassNotFoundException: org.drools.example.api.defaultkiesession.Hal1.AlwaysTrue > at org.drools.core.common.ProjectClassLoader.tryDefineType(ProjectClassLoader.java:123) > at org.drools.core.common.ProjectClassLoader.loadType(ProjectClassLoader.java:114) > at org.drools.core.common.ProjectClassLoader.loadClass(ProjectClassLoader.java:84) > at java.lang.ClassLoader.loadClass(ClassLoader.java:247) > ... 15 more > {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

12 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 February 2014