April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-816) Refactor Column to be Pattern

by Mark Proctor (JIRA)

Refactor Column to be Pattern ----------------------------- Key: JBRULES-816 URL: http://jira.jboss.com/jira/browse/JBRULES-816 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: All Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m2 all Column references should eb called a Pattern, so refactor all methods, classes, local variables, comments, resource files, documentation etc. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-744) New elements added to a Shadow Fact's List do not trigger activations on rules using contains

by Michael Anstis (JIRA)

New elements added to a Shadow Fact's List do not trigger activations on rules using contains --------------------------------------------------------------------------------------------- Key: JBRULES-744 URL: http://jira.jboss.com/jira/browse/JBRULES-744 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1-m1, 3.0.5 Environment: Windows XP SP2, Java 1.5 Reporter: Michael Anstis Assigned To: Mark Proctor Attachments: drools-jira.jar Example scenario: A Fact X has a property C which is a collection. Rule 1 operates on Fact X and adds (and asserts) a new element Y to collection C. Another Rule 2 which has a pattern "X ( C contains Y) does not get activated. Rules which have a pattern "Y" do activate. See attached example code to replicate. -- 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, 2 months

2
3
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, 2 months

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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-18) Caching and BlackListing

by Adrian Brock (JIRA)

Caching and BlackListing ------------------------ Key: JBOSGI-18 URL: http://jira.jboss.com/jira/browse/JBOSGI-18 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Adrian Brock Assigned To: Adrian Brock Add ClassLoaderPolicy items for caching and blacklisting and implementation in the Domain/ClassLoader. See the forum thread for why this is not just a global cache. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-21) ClassLoader tests

by Adrian Brock (JIRA)

ClassLoader tests ----------------- Key: JBOSGI-21 URL: http://jira.jboss.com/jira/browse/JBOSGI-21 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Adrian Brock Assigned To: Adrian Brock Complete the tests in the new ClassLoader -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-20) TODO and REVIEWS

by Adrian Brock (JIRA)

TODO and REVIEWS ---------------- Key: JBOSGI-20 URL: http://jira.jboss.com/jira/browse/JBOSGI-20 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Adrian Brock Assigned To: Adrian Brock Go through the TODOs and REVIEWS in the new classloader and either resolve them all or create JIRA issues. -- 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, 2 months

1
1
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, 2 months

3
3
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, 2 months

2
4
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, 2 months

2
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 April 2007