July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBRULES-343) Refactor support in Eclipse

by Kris Verlaenen (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-343?page=all ] Kris Verlaenen updated JBRULES-343: ----------------------------------- Component/s: Eclipse IDE > Refactor support in Eclipse > --------------------------- > > Key: JBRULES-343 > URL: http://jira.jboss.com/jira/browse/JBRULES-343 > Project: JBoss Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Eclipse IDE > Reporter: Mark Proctor > Assigned To: Kris Verlaenen > Fix For: FUTURE > > > We should be able to refactor a drl, which should also be refactored on project wide changes. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1403) Control-Flow Statement into "action nodes" (RULEFLOW)

by Massimiliano Magistri (JIRA)

Control-Flow Statement into "action nodes" (RULEFLOW) ----------------------------------------------------- Key: JBRULES-1403 URL: http://jira.jboss.com/jira/browse/JBRULES-1403 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.3 Environment: Eclipse Europa 3.3.1.1 Reporter: Massimiliano Magistri I tried to add the following (stupid) statement into the action node "textual editor": if (true) int i=0; and I got back an exception as follows: org.mvel.PropertyAccessException: unable to resolve property: if ( true ) at org.mvel.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:291) at org.mvel.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:107) at org.mvel.ASTNode.getReducedValueAccelerated(ASTNode.java:185) at org.mvel.MVELRuntime.execute(MVELRuntime.java:88) at org.mvel.CompiledExpression.getValue(CompiledExpression.java:108) at org.mvel.MVEL.executeExpression(MVEL.java:230) at org.drools.ruleflow.instance.impl.ActionNodeInstanceImpl.trigger(ActionNodeInstanceImpl.java:93) at org.drools.ruleflow.instance.impl.StartNodeInstanceImpl.triggerCompleted(StartNodeInstanceImpl.java:38) at org.drools.ruleflow.instance.impl.StartNodeInstanceImpl.trigger(StartNodeInstanceImpl.java:30) at org.drools.ruleflow.instance.impl.RuleFlowProcessInstanceImpl.start(RuleFlowProcessInstanceImpl.java:172) at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1409) at mytest.TestRF.testScritturaContractRF(TestRF.java:95) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.lang.NullPointerException at org.mvel.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:519) at org.mvel.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:257) ... 29 more -- 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

16 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1610) Binary serialization for processes

by Kris Verlaenen (JIRA)

Binary serialization for processes ---------------------------------- Key: JBRULES-1610 URL: http://jira.jboss.com/jira/browse/JBRULES-1610 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Flow Reporter: Kris Verlaenen Assigned To: Kris Verlaenen Fix For: 5.0.0-M1 -- 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

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1497) Email GUI for email work item

by Mark Proctor (JIRA)

Email GUI for email work item ----------------------------- Key: JBRULES-1497 URL: http://jira.jboss.com/jira/browse/JBRULES-1497 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Flow Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 4.0.5 A GUI, with working backend, is needed for emails. -- 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

16 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1384) JDBCCacheLoader.put(fqn, map) not overridding values

by Mircea Markus (JIRA)

JDBCCacheLoader.put(fqn,map) not overridding values --------------------------------------------------- Key: JBCACHE-1384 URL: http://jira.jboss.com/jira/browse/JBCACHE-1384 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.1.SP9 Reporter: Mircea Markus Assigned To: Mircea Markus Fix For: 1.4.X JDBCCacheLoader.put(Fqn name, Map attributes) does not work as expected. It does not overwrite the existing attribute map with values from the old one, as expected. Contract defined in the interface is: " * Puts all entries of the map into the existing map of the given node, * overwriting existing keys, but not clearing the existing map before * insertion. " -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1383) ConcurrentHashSet should allow for setting a "concurrency level"

by Manik Surtani (JIRA)

ConcurrentHashSet should allow for setting a "concurrency level" ---------------------------------------------------------------- Key: JBCACHE-1383 URL: http://jira.jboss.com/jira/browse/JBCACHE-1383 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.2.0.GA, 3.0.0 o.j.c.util.concurrent.ConcurrentHashSet wraps a CHM and provides threadsafe Set semantics. Currently this only has a single, empty ctor which invokes the CHM's empty ctor. Should allow for taking in a concurrency level, which can be passed in to the CHM to reduce the number of segments created as this can be a memory hog in some cases. -- 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

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-608) Util.methodExistsInSuperClassOrInterface does not take into account exactSuper value

by Flavia Rainone (JIRA)

Util.methodExistsInSuperClassOrInterface does not take into account exactSuper value ------------------------------------------------------------------------------------ Key: JBAOP-608 URL: http://jira.jboss.com/jira/browse/JBAOP-608 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR14 Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.0.0.GA The mentioned method keeps on checking the whole hierarchy, without ever making a stop to check if it must ignore the super class (exactSuper). -- 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

16 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-5702) Add JDBC4 support for DataSourceInterceptor

by Jesper Pedersen (JIRA)

Add JDBC4 support for DataSourceInterceptor ------------------------------------------- Key: JBAS-5702 URL: http://jira.jboss.com/jira/browse/JBAS-5702 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-5.0.0.CR1 Reporter: Jesper Pedersen Assigned To: Jesper Pedersen Fix For: JBossAS-5.0.0.CR2 Add support for JDBC4 to org.jboss.varia.stats.DataSourceInterceptor in the AS/varia module. -- 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

16 years, 9 months

1
6
0 / 0

[JBoss JIRA] Created: (JBAS-5717) jboss-ds_1_5.dtd has syntax error

by Juergen Zimmermann (JIRA)

jboss-ds_1_5.dtd has syntax error --------------------------------- Key: JBAS-5717 URL: http://jira.jboss.com/jira/browse/JBAS-5717 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR1 Reporter: Juergen Zimmermann In examples/dtd/jboss-ds_1_5.dtd a comma is missing at the end of line 44: Inside <!ELEMENT local-tx-datasource ...: line 44: validate-on-match?, idle-timeout-minutes? line 45: no-tx-separate-pools? , new-connection-sql? , check-valid-connection-sql? , -- 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

16 years, 9 months

3
2
0 / 0

[JBoss JIRA] Updated: (JBAS-1436) Improved management

by Vicky Kak (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1436?page=all ] Vicky Kak updated JBAS-1436: ---------------------------- Fix Version/s: (was: JBossAS-4.2.3.GA) > Improved management > ------------------- > > Key: JBAS-1436 > URL: http://jira.jboss.com/jira/browse/JBAS-1436 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Adrian Brock > Assigned To: Vicky Kak > Priority: Minor > Fix For: JBossAS-5.1.0.CR1 > > > Forum Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48682 > **This is a holder issue. Each section should be raised as a new issue as it is > developed with a link from this issue.** > There are a number of areas in JCA that need better management capabilities. > Some of these stats may also reveal the need for new configuration/tuning parameters. > In core JCA: > 1) Better visibility on the ManagedConnectionFactory. > This is currently a DynamicMBean that provides basic config parameters, but we could also > provide a proxy/wrapper to provide statistics of operations on the factory and its > ManagedConnections. > a) createManagedConnections > b) matchManagedConnections > c) events on from the listeners > 2) Better visibility of the Pool(s) > Only top level statistics are provided (you cannot see the subpools). > The statistics are also not synchronized with the pool (for performance reasons > and also the fact that each stat is retrieved on individual MBean getAttribute requests) > Additional statistics could include wait times when requests are waiting on an empty pool, > idle time of unused connections, etc. > 3) Better visibility of the ConnectionManager > Currently this has no visibility for management. > Its main responsibilties are transactions enlistment and security. > e.g. This could show how long is wasted because <track-connection-by-tx/> does not > return the connection the pool until transaction completion. > 4) JDBC resource adapter > PreparedStatementCache stats > Query time stats > etc. > 5) JMS resource adapter > Message send/receive stats > 6) Inbound messaging > Stats for message delivery > 7) Transaction inflow > Stats for transaction inflow and also display a list of current inbound transactions > 8) Work management > Stats for the work management pools and timers -- 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

16 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008