October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-685) JBoss Logging Generator 1.0.0.CR3

by Jesper Pedersen (Created) (JIRA)

JBoss Logging Generator 1.0.0.CR3 --------------------------------- Key: JBJCA-685 URL: https://issues.jboss.org/browse/JBJCA-685 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-2200) Ability to edit (xa)datasource property and subresources when (xa)datasource is disabled

by Stefano Maestri (Created) (JIRA)

Ability to edit (xa)datasource property and subresources when (xa)datasource is disabled ---------------------------------------------------------------------------------------- Key: AS7-2200 URL: https://issues.jboss.org/browse/AS7-2200 Project: Application Server 7 Issue Type: Feature Request Components: JCA Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.1.0.Beta1 Anything that goes into <connection-property/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (AS7-2194) Failed to start server instance

by Heiko Braun (Created) (JIRA)

Failed to start server instance ------------------------------- Key: AS7-2194 URL: https://issues.jboss.org/browse/AS7-2194 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Priority: Blocker I've deleted all server configurations and did start over with a new one. However when I try to start the newly created instances, I get this: {noformat} [Host Controller] ("host" => "master"), [Host Controller] ("server-config" => "staging-server") [Host Controller] ]): java.lang.IllegalStateException: Cannot access a remote file repository from the master domain controller [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService.getRemoteFileRepository(DomainModelControllerService.java:258) [jboss-as-host-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] [Host Controller] at org.jboss.as.host.controller.ModelCombiner.addDeployments(ModelCombiner.java:455) [jboss-as-host-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] [Host Controller] at org.jboss.as.host.controller.ModelCombiner.getBootUpdates(ModelCombiner.java:182) [jboss-as-host-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] [Host Controller] at org.jboss.as.host.controller.ManagedServer.startServerProcess(ManagedServer.java:173) [jboss-as-host-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] [Host Controller] at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:173) [jboss-as-host-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2951) regression: cannot compile return value "(java.lang.Object.class)"

by Wolfgang Laun (JIRA)

regression: cannot compile return value "(java.lang.Object.class)" ------------------------------------------------------------------ Key: JBRULES-2951 URL: https://issues.jboss.org/browse/JBRULES-2951 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.2.0.M2 Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Critical The rule below compiled with a version build from HEAD on February 10, 2011. But now: Unable to Analyse Expression target == source || target == (java.lang.Object.class): [Error: Failed to compile: 2 compilation error(s): - (1,32) unable to resolve method using strict-mode: ex10.Assignment.java() - (1,32) unqualified type in strict mode for: java] [Near : {... target == source || target == (java.lang.Object.class) ....}] ^ [Line: 1, Column: 32] : [Rule name='SameOrObjectIsAssignable'] ALSO please note that the line number is way off. rule SameOrObjectIsAssignable when $a: Assignment( $t: target, target == source || target == (java.lang.Object.class) ) then System.out.println( $a.toString() + " is OK. " ); retract( $a.getOriginal() ); end -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

7
7
0 / 0

[JBoss JIRA] Created: (JBRULES-3147) Regression: all uppercase field reference results in compile error

by Wolfgang Laun (JIRA)

Regression: all uppercase field reference results in compile error ------------------------------------------------------------------ Key: JBRULES-3147 URL: https://issues.jboss.org/browse/JBRULES-3147 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.Final Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.1.Final Consider the following ways of writing getters, setters and pattern field names element xetter field 5.1.1 5.3.0 ============================================= state xetstate state OK OK state xetState state OK OK staTe xetStaTe staTe OK OK state xetSTATE STATE OK ERR The last variation is a regression from 5.1.1. It is not so absurd - if the field is designated with an acronym (XML,...) this would be the natural way to write xetters and the pattern field. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
8
0 / 0

[JBoss JIRA] Created: (JBRULES-3134) Parenthesized class name causes NPE in RuleBuilder (MVEL)

by Wolfgang Laun (JIRA)

Parenthesized class name causes NPE in RuleBuilder (MVEL) --------------------------------------------------------- Key: JBRULES-3134 URL: https://issues.jboss.org/browse/JBRULES-3134 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.Final Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.1.Final declare Foo clazz : Class end rule testFoo when Foo( clazz == (java.lang.Object) ) then System.out.println( "Foo is Object" ); end causes Exception in thread "main" [Error: not a statement, or badly formed structure] [Near : {... (java.lang.Object) ....}] ^ [Line: 1, Column: 19] at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:307) at org.mvel2.compiler.ExpressionCompiler.compile(ExpressionCompiler.java:69) at org.mvel2.MVEL.analysisCompile(MVEL.java:668) at org.mvel2.MVEL.analysisCompile(MVEL.java:672) at org.drools.rule.builder.PatternBuilder.setInputs(PatternBuilder.java:779) at org.drools.rule.builder.PatternBuilder.build(PatternBuilder.java:540) at org.drools.rule.builder.PatternBuilder.processConstraintsAndBinds(PatternBuilder.java:349) at org.drools.rule.builder.PatternBuilder.build(PatternBuilder.java:264) at org.drools.rule.builder.PatternBuilder.build(PatternBuilder.java:122) at org.drools.rule.builder.GroupElementBuilder.build(GroupElementBuilder.java:65) at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:81) at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:1889) at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:755) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:365) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:543) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:28) at listofthree.Main.setup(Main.java:55) at listofthree.Main.main(Main.java:107) Caused by: java.lang.NullPointerException at java.lang.Class.isAssignableFrom(Native Method) at org.mvel2.DataConversion.canConvert(DataConversion.java:104) at org.mvel2.ast.TypeCast.<init>(TypeCast.java:47) at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:1034) at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:135) ... 17 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
5
0 / 0

[JBoss JIRA] Created: (AS7-1795) Fix the ModCluster description providers for the improved validation in jboss-as-subsystem-test

by Kabir Khan (JIRA)

Fix the ModCluster description providers for the improved validation in jboss-as-subsystem-test ----------------------------------------------------------------------------------------------- Key: AS7-1795 URL: https://issues.jboss.org/browse/AS7-1795 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Kabir Khan Assignee: Jean-Frederic Clere Fix For: 7.1.0.Alpha1 I added a test called ModClusterSubsystemTestCase, which uses our subsystem testing framework which attempts to validate the description providers, this will be committed to upstream in the next few days. To make the tests pass I had to override AdditionalInitialization.getModelValidationConfiguration() and isValidateOperations() as follows: {code} @Override protected ValidationConfiguration getModelValidationConfiguration() { return null; } @Override protected boolean isValidateOperations() { //TODO fix providers https://issues.jboss.org/browse/AS7-1789 return false; } {code} Returning null basically turns off validation of the providers, and the isValidateOperations() override turns off validation of the contents of the actual operations. What I have added is a minimum of what is required for subsystem testing, the test framework allows you to do a lot of other stuff, see the jmx subsystem test for some examples. The wip lives at https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes The above is standard text as I'm going through and creating tests. The test has been @Ignored due to a further failure once validation 'passes' (i.e. the validation is not run due to the flags set) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3196) Infinite loop instead of NPE

by Wolfgang Laun (JIRA)

Infinite loop instead of NPE ---------------------------- Key: JBRULES-3196 URL: https://issues.jboss.org/browse/JBRULES-3196 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.3.0.Beta1 Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Critical Fix For: 5.3.0.CR1 The marked statement results in an infinite loop if the HashMap gradeMap is not initialized. Expected behaviour is to throw an exception, e.g. NPE. import java.util.HashMap; declare Student name : String @key gradeMap : HashMap end rule KickOff when then Student s = new Student( "Joe" ); insert( s ); end rule "Subject grade points" dialect "mvel" when $u : Student() then System.out.println("Adding marks for " + $u.getName() ); $u.gradeMap["CompSc"] += 100; ###<<<<<<<<<<<<<<<<<<<<<<<<<<<<< LOOP System.out.println("Marks added"); end -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

8
7
0 / 0

[JBoss JIRA] (JBRULES-2269) Virtual Service Manager

by Geoffrey De Smet (Updated) (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2269?page=com.atlassian.jira.plug... ] Geoffrey De Smet updated JBRULES-2269: -------------------------------------- Fix Version/s: 5.4.0.Beta1 (was: 5.3.0.Final) > Virtual Service Manager > ----------------------- > > Key: JBRULES-2269 > URL: https://issues.jboss.org/browse/JBRULES-2269 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 5.4.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2936) Importing decision table from Excel: Non Ascii chars should not be corrupted

by Geoffrey De Smet (Updated) (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2936?page=com.atlassian.jira.plug... ] Geoffrey De Smet updated JBRULES-2936: -------------------------------------- Fix Version/s: 5.4.0.Beta1 (was: 5.3.0.Final) > Importing decision table from Excel: Non Ascii chars should not be corrupted > ---------------------------------------------------------------------------- > > Key: JBRULES-2936 > URL: https://issues.jboss.org/browse/JBRULES-2936 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Geoffrey De Smet > Fix For: 5.4.0.Beta1 > > > see > http://stackoverflow.com/questions/5298748/guvnor-rules-encoding > Excel (like windows) probably has crappy encoding standardization (as in none at all), so I suspect that we 'll need to ask the excel document what encoding (or even what locale) it is and read the data in that encoding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 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 October 2011