April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4342) AS7 should be able to build out of box

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4342: ----------------------------------- Summary: AS7 should be able to build out of box Key: AS7-4342 URL: https://issues.jboss.org/browse/AS7-4342 Project: Application Server 7 Issue Type: Feature Request Components: Build System Affects Versions: 7.1.0.Final, 7.0.0.Final Reporter: Radoslav Husar Assignee: Paul Gier Fix For: Open To Community It doesnt since you need https://community.jboss.org/wiki/MavenGettingStarted-Developers. Why not just use the correct settings.xml by default? -- 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

13 years, 8 months

4
11
0 / 0

[JBoss JIRA] (JBRULES-3366) When adding resources using both MVEL and Java dialects the JavaDialect constructor fails when dialectData is found and stored.

by Alan Zall (JIRA)

Alan Zall created JBRULES-3366: ---------------------------------- Summary: When adding resources using both MVEL and Java dialects the JavaDialect constructor fails when dialectData is found and stored. Key: JBRULES-3366 URL: https://issues.jboss.org/browse/JBRULES-3366 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.3.1.Final Environment: Linux Reporter: Alan Zall Assignee: Mark Proctor In the constructor of JavaDialect, if pkg.getDialectRuntimeRegistry().getDialectData( ID ) returns a non null value, then a null is passed into the PackageStore constructor. if ( pkg.getDialectRuntimeRegistry().getDialectData( ID ) == null ) { data = new JavaDialectRuntimeData(); this.pkg.getDialectRuntimeRegistry().setDialectData( ID, data ); data.onAdd( this.pkg.getDialectRuntimeRegistry(), this.packageBuilder.getRootClassLoader() ); } this.packageStoreWrapper = new PackageStore( data, this.results ); is fixed by: if (( data = (JavaDialectRuntimeData) pkg.getDialectRuntimeRegistry().getDialectData( ID )) == null ) { data = new JavaDialectRuntimeData(); this.pkg.getDialectRuntimeRegistry().setDialectData( ID, data ); data.onAdd( this.pkg.getDialectRuntimeRegistry(), this.packageBuilder.getRootClassLoader() ); } this.packageStoreWrapper = new PackageStore( data, this.results ); -- 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

13 years, 8 months

3
3
0 / 0

[JBoss JIRA] (AS7-3857) Eliminate redundant config of nullable and allowExpression in AttributeDefinition

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-3857: ------------------------------------- Summary: Eliminate redundant config of nullable and allowExpression in AttributeDefinition Key: AS7-3857 URL: https://issues.jboss.org/browse/AS7-3857 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.1.Final AttributeDefinition has configuration of "allowExpressions" and "nullable". It also takes a Validator. It's a common mistake that people configure the AD to allow expressions or null but forget to do the same with the validator. Make this easier. One possibility is to wrap the passed in validator with one that deals with expressions/nulls and delegates to the provided validator if not null and not an expression. -- 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

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] (JBRULES-3432) Error in error message for bad syntax in function

by Wolfgang Laun (JIRA)

Wolfgang Laun created JBRULES-3432: -------------------------------------- Summary: Error in error message for bad syntax in function Key: JBRULES-3432 URL: https://issues.jboss.org/browse/JBRULES-3432 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.4.0.Beta2 Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Minor Without dialect "mvel", this DRL function written in MVEL package mvel; function Integer englishToInt(String englishNumber){ return ["one":1, "two":2, "three":3, "four":4, "five":5].get(englishNumber.toLowerCase()); } causes this error message - NOTE THE NAME OF THE FUNCTION! Error importing : 'mvel.EnglishToInt.englishToInt' [ function englishToIntenglishToInt (line:12): Syntax error on tokens, Name expected instead ] -- 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

13 years, 8 months

3
3
0 / 0

[JBoss JIRA] (JBRULES-3433) DRL parser accepts function written in MVEL

by Wolfgang Laun (JIRA)

Wolfgang Laun created JBRULES-3433: -------------------------------------- Summary: DRL parser accepts function written in MVEL Key: JBRULES-3433 URL: https://issues.jboss.org/browse/JBRULES-3433 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.4.0.Beta2 Reporter: Wolfgang Laun Assignee: Mark Proctor A DRL function using MVEL syntax "compiles" without any error indication when dialect "mvel" is set at package lavel. import java.util.Map; dialect "mvel" function Integer x(String englishNumber){ Map m = ["one":1, "two":2, "three":3, "four":4, "five":5]; # not Java here! Object obj = m.get(englishNumber.toLowerCase()); return Integer.parseInt(obj.toString()); } -- 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

13 years, 8 months

3
3
0 / 0

[JBoss JIRA] (AS7-4303) domain/host.xml cannot be parsed when a <variable> is defined under <jvm><environment-variables>

by Michael Voegele (JIRA)

Michael Voegele created AS7-4303: ------------------------------------ Summary: domain/host.xml cannot be parsed when a <variable> is defined under <jvm><environment-variables> Key: AS7-4303 URL: https://issues.jboss.org/browse/AS7-4303 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.1.Final Environment: Win Reporter: Michael Voegele Assignee: Jason Greene Executing following dmr operation is successful: {code:xml} { "operation" => "add", "address" => [ ("host" => "master"), ("server-config" => "server-1"), ("jvm" => "default") ] "java-home" => "C:/eplatform/java/jdk1.7.0", "heap-size" => "128m", "max-heap-size" => "256m", "permgen-size" => "64m", "max-permgen-size" => "128m", "stack-size" => "512k", "environment-variables" => [{"foo" => "bar"}] } {code} and results in following xml: {code:xml} <jvm name="default" java-home="C:/eplatform/java/jdk1.7.0"> <heap size="128m" max-size="256m"/> <permgen size="64m" max-size="128m"/> <stack size="512k"/> <environment-variables> <variable name="foo" value="bar"/> </environment-variables> </jvm> {code} but the server (domain mode) cannot be (re)started anymore and results in following exception: {code} [Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[51,21] [Host Controller] Message: JBAS014789: Unexpected element '{urn:jboss:domain:1.2}variable' encountered {code} -- 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

13 years, 8 months

3
2
0 / 0

[JBoss JIRA] (AS7-4304) NullPointerException when trying to remove a system-property which does not exist

by Michael Voegele (JIRA)

Michael Voegele created AS7-4304: ------------------------------------ Summary: NullPointerException when trying to remove a system-property which does not exist Key: AS7-4304 URL: https://issues.jboss.org/browse/AS7-4304 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.1.Final Reporter: Michael Voegele Assignee: Jason Greene when trying to execute: {code:xml} { "operation" => "remove", "address" => [ ("host" => "master"), ("server-config" => "server-1"), ("system-property" => "foo") ] } {code} the answer is: {code:xml} { "outcome" => "failed", "failure-description" => {"host-failure-descriptions" => [("master" => "JBAS014749: Operation handler failed: null")]}, "rolled-back" => true } {code} a NullPointerException is thrown during execution: {code:xml} [Host Controller] 2012-03-27 15:41:04,870 [management-handler-thread - 30] ERROR org.jboss.as.controller.management-operation executeStep 418 - JBAS014612: Operation ("remove") failed - address: ([ [Host Controller] ("host" => "master"), [Host Controller] ("server-config" => "server-1"), [Host Controller] ("system-property" => "foo") [Host Controller] ]): java.lang.NullPointerException [Host Controller] at org.jboss.as.controller.operations.common.SystemPropertyRemoveHandler.execute(SystemPropertyRemoveHandler.java:67) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.domain.controller.operations.coordination.DomainFinalResultHandler.execute(DomainFinalResultHandler.java:74) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.executeTwoPhaseOperation(OperationCoordinatorStepHandler.java:225) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.execute(OperationCoordinatorStepHandler.java:118) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:85) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:287) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:487) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final] {code} this should not happen, the normal behaviour should be as follows (just a 'not found' message with no exception): {code:xml} { "operation" => "remove", "address" => [ ("host" => "master"), ("server-config" => "server-1"), ("jvm" => "default") ] } {code} {code:xml} { "outcome" => "failed", "failure-description" => {"host-failure-descriptions" => [("master" => "JBAS014807: Management resource '[ (\"host\" => \"master\"), (\"server-config\" => \"server-1\"), (\"jvm\" => \"default\") ]' not found")]}, "rolled-back" => true } {code} -- 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

13 years, 8 months

3
3
0 / 0

[JBoss JIRA] (AS7-4378) Welcome page ignores console-enabled setting

by Carlo de Wolf (JIRA)

Carlo de Wolf created AS7-4378: ---------------------------------- Summary: Welcome page ignores console-enabled setting Key: AS7-4378 URL: https://issues.jboss.org/browse/AS7-4378 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.1.Final Environment: Fedora 17 Reporter: Carlo de Wolf Assignee: Remy Maucherat The welcome web context is populated either with console links or without based on the existence of the http management port. This is wrong as it might just have the [HTTP Management API|https://docs.jboss.org/author/display/AS71/The+HTTP+management+API] enabled. Setting console-enabled to false also has no affect. See WelcomeContextConsoleServlet and WelcomeContextService. -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-776) quiet parameter

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-776: ------------------------------------- Summary: quiet parameter Key: JBJCA-776 URL: https://issues.jboss.org/browse/JBJCA-776 Project: IronJacamar Issue Type: Bug Components: Validator Affects Versions: 1.1.0.Alpha6, 1.0.9.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Minor Fix For: 1.0.10.Final, 1.1.0.Alpha7 The quiet parameter is done as "quite" -- 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

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1665) put offending rule name in exception messages

by Alex McCarrier (JIRA)

put offending rule name in exception messages --------------------------------------------- Key: JBRULES-1665 URL: http://jira.jboss.com/jira/browse/JBRULES-1665 Project: JBoss Drools Issue Type: Feature Request Components: Drl Parser/Builder Affects Versions: FUTURE Environment: all Reporter: Alex McCarrier Assigned To: Mark Proctor Priority: Minor It would be nice if drools compiler error messages would include the rule that caused the error. For instance, predicate eval errors, or "unable to resolve property" errors would state which rule was being evaluated when it encountered an error. Currently the developer has to go through the rules file looking for lines similar to the one reported in the error. Also, when it's this much work for a developer to find the offending rule, it is pretty much impossible for business users to figure out which rule they messed up. If it's at all possible to add the rule name to these error messages, please do so. It would make our lives a lot easier. :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2012