February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-617) DSL completion processor enhancements

by Michael Neale (JIRA)

DSL completion processor enhancements ------------------------------------- Key: JBRULES-617 URL: http://jira.jboss.com/jira/browse/JBRULES-617 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.5 Reporter: Michael Neale Assigned To: Kris Verlaenen Fix For: 3.1-m3 Peter lin has contributed some possible enhancements for DSL completion proposals. It works by breaking down the DSL in to a tree of sentence fragments, which can be given to used to limit the selections in the content assistance. This would work best for a dedicated DSL editor, where the content assistance can be active, always, when typing (not ctrl-space, but as soon as the cursor enters the LHS). -- 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

19 years, 1 month

5
11
0 / 0

[JBoss JIRA] Created: (JBRULES-703) Class cast inside function calls triggers org.drools.RuntimeDroolsException: unable to find the function

by Juergen none (JIRA)

Class cast inside function calls triggers org.drools.RuntimeDroolsException: unable to find the function -------------------------------------------------------------------------------------------------------- Key: JBRULES-703 URL: http://jira.jboss.com/jira/browse/JBRULES-703 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.1-m1 Reporter: Juergen none Assigned To: Mark Proctor Parsing an 3.0.5 drools file .drl yields, e.g.: Caused by: org.drools.RuntimeDroolsException: unable to find the function ',' at org.drools.semantics.java.StaticMethodFunctionResolver.resolveFunction(StaticMethodFunctionResolver.java:79) at org.drools.semantics.java.FunctionFixer.fix(FunctionFixer.java:130) at org.drools.semantics.java.FunctionFixer.fix(FunctionFixer.java:66) at org.drools.semantics.java.builder.EvalBuilder.build(EvalBuilder.java:78) at org.drools.semantics.java.builder.GroupElementBuilder.build(GroupElementBuilder.java:63) at org.drools.semantics.java.RuleBuilder.build(RuleBuilder.java:178) at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:381) at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:219) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:148) at org.drools.jsr94.rules.admin.LocalRuleExecutionSetProviderImpl.createRuleExecutionSet(LocalRuleExecutionSetProviderImpl.java:120) at org.drools.jsr94.rules.admin.LocalRuleExecutionSetProviderImpl.createRuleExecutionSet(LocalRuleExecutionSetProviderImpl.java:77) for a class cast inside a function call (in condition or consequence block): eval( globalVar.f((java.util.Collection)a, (java.util.Collection)b) >= c.floatValue() ) -- 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

19 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-672) Manual doesn't build

by Dirk Bergstrom (JIRA)

Manual doesn't build -------------------- Key: JBRULES-672 URL: http://jira.jboss.com/jira/browse/JBRULES-672 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.1-m1 Environment: Linux foo 2.6.18-gentoo-r6 #1 SMP PREEMPT Fri Jan 5 12:04:48 PST 2007 i686 Intel(R) Pentium(R) 4 CPU 1.70GHz GenuineIntel GNU/Linux Reporter: Dirk Bergstrom Assigned To: Mark Proctor Attempting to build the manual via "ant manual" doesn't work. There are a large number of errors like "No template matches xi:include in chapter.". Here's a snippet of the ant output: lang.dochtml: [mkdir] Created dir: /homes/dbergstr/local.src/jbossrules/documentation/manual/build/en/html [copy] Copying 1 file to /homes/dbergstr/local.src/jbossrules/documentation/manual/build/en/html [java] Writing bk01-toc.html for book [java] Writing pr01.html for preface(preface) [java] No template matches xi:include in chapter. [java] No template matches xi:include in chapter. The manual that's generated looks like this: Chapter 1. The Rule Engine <xi:include></xi:include><xi:include></xi:include><xi:include></xi:include><xi:include></xi:include><xi:include></xi:include><xi:include></xi:include> Chapter 2. Installation and Setup <xi:include></xi:include><xi:include></xi:include><xi:include></xi:include><xi:include></xi:include><xi:include></xi:include> -- 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

19 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-545) Add a framework for dynamic bean generation

by Edson Tirelli (JIRA)

Add a framework for dynamic bean generation ------------------------------------------- Key: JBRULES-545 URL: http://jira.jboss.com/jira/browse/JBRULES-545 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Edson Tirelli Assigned To: Edson Tirelli Add a framework to allow dynamic bean generation. -- 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

19 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAOP-368) TransformerCommon.toClass calls need to the aspect CodeSource

by Scott M Stark (JIRA)

TransformerCommon.toClass calls need to the aspect CodeSource ------------------------------------------------------------- Key: JBAOP-368 URL: http://jira.jboss.com/jira/browse/JBAOP-368 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Components: Aspect Library Affects Versions: 2.0.0.alpha3 Reporter: Scott M Stark Calls like PerVmAdvice.generateInterceptor(Joinpoint joinpoint, Object aspect, String adviceName) are not passing in a CodeSource to the TransformerCommon.toClass and it does not accept one. The Interceptor classes need to be using the CodeSource of the aspect class so that there is a consistent security view of the aspect interceptors. -- 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

19 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-300) SecurityActions$PrincipalInfoAction missing from client jar

by Thomas Diesler (JIRA)

SecurityActions$PrincipalInfoAction missing from client jar ----------------------------------------------------------- Key: JBAOP-300 URL: http://jira.jboss.com/jira/browse/JBAOP-300 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler java.lang.NoClassDefFoundError: org/jboss/aspects/security/SecurityActions$PrincipalInfoAction at org.jboss.aspects.security.SecurityActions.getPrincipal(SecurityActions.java:363) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102) -- 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

19 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JGRP-387) Reduce heavily contented locks

by Bela Ban (JIRA)

Reduce heavily contented locks ------------------------------ Key: JGRP-387 URL: http://jira.jboss.com/jira/browse/JGRP-387 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Identify and reduce/eliminate heavily contended locks, e.g. NakReceiverWindow: N threads will messages from the same receiver will hit the NRW (synchronization on NRW for inserts and removes). We can possibly replace the sorted hashmaps in NRW with their java.util.concurrent equivalents, so access is distributed across bucket (lock striping), reducing heavily contended locks. Also, replace ReentrantLock (e.g. used in add() and remove()) with the j.u.c.lock equivalent. NAKACK: Same as above: replace received_msgs with ConcurrentHashMap. Use equivalents from j.u.c.lock to replace the locks used. Another big source of contention is that multiple threads with messsages from the *same* receiver will all add their message to the *same* NRW, then *only one* thread will remove them all and pass them up, causing the other threads to block (incurring context switches and possible processor cache flushes). When the delivery thread returns, all other threads wake up and all of them return after NRW.remove() returns null ! -- 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

19 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4155) run.conf used from other scripts than run.sh

by Tobias Frech (JIRA)

run.conf used from other scripts than run.sh -------------------------------------------- Key: JBAS-4155 URL: http://jira.jboss.com/jira/browse/JBAS-4155 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.5.GA Environment: Linux/Unix Reporter: Tobias Frech Priority: Minor Configuration in run.conf is used from other scripts than run.sh. For example shutdown.sh or twiddle.sh include it. They should not because that leads to undesireable or even dangeous effects. Details: Editing run.conf an including JAVA_OPTS="$JAVA_OPTS -Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y" to enable remote debugging Starting the server: sh run.sh -c minimal Stopping the server produces: sh shutdown.sh -S ERROR: transport error 202: bind failed: Address already in use ["transport.c",L41] ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L497] JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initializedFATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113) This may get worse if someone uses a -Xms3000m setting on a server that only has 4GB of memory. Potentially leading to a swap out of a production system to disk. -- 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

19 years, 1 month

4
9
0 / 0

[JBoss JIRA] Created: (JBRULES-435) Large integer values in decision tables are converted to scientific notation in DRL which cannot be parsed

by Volker Augustin (JIRA)

Large integer values in decision tables are converted to scientific notation in DRL which cannot be parsed ---------------------------------------------------------------------------------------------------------- Key: JBRULES-435 URL: http://jira.jboss.com/jira/browse/JBRULES-435 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Decision tables, Drl Parser/Builder Reporter: Volker Augustin Assigned To: Mark Proctor When a condition column in a decision table contains values like 25000000, this is compiled using the SpreadsheetCompiler into 2.5E7 in the DRL. However, the DRL parser/compiler cannot cope with this notation and exists with a unexpected token "E7" error message. -- 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

19 years, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-434) Cannot enter more than one parameter in one column on German computers

by Volker Augustin (JIRA)

Cannot enter more than one parameter in one column on German computers ---------------------------------------------------------------------- Key: JBRULES-434 URL: http://jira.jboss.com/jira/browse/JBRULES-434 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Decision tables Environment: Windows XP, standard GERMAN settings Reporter: Volker Augustin Assigned To: Mark Proctor Section 4.1.4.1 of the JBoss Rules documentation states: The "$para" place holder is used in templates to indicate where data form the cell will be interpolated. You can also use "$1" to the same effect. If the cell contains a comma seperated list of values, $1 and $2 etc. may be used to indicate which positional parameter from the list of values in the cell will be used. As the German decimal separator is ',' and not '.' as in the English locale, no list of this form can be entered on a German computer system if there are e.g. only two values and they happen to be integers. E.g. if you try to create the list containing the two values 10 and 20, according to the documentation you must enter '10,20'. This will be interpreted as 10.20 by a German computer and result in a single decimal value instead of a list of two integers. The separator ',' is hardcoded somewhere (in SnippedBuilder (?) I think). Maybe this can be made configurable. E.g. a "Configuration" section in the Excel spreadsheet would do. -- 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

19 years, 1 month

5
4
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 2007