April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2883) Expose org.drools.runtime.rule StatefulRuleSession. fireAllRules(org.drools.runtime.rule. AgendaFilter agendaFilter, int fireLimit)

by Jian Zhi (JIRA)

Expose org.drools.runtime.rule StatefulRuleSession. fireAllRules(org.drools.runtime.rule. AgendaFilter agendaFilter, int fireLimit) ----------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2883 URL: https://issues.jboss.org/browse/JBRULES-2883 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.1.FINAL Reporter: Jian Zhi Assignee: Mark Proctor fireAllRules(AgendaFilter agendaFilter, int fireLimit) is exposed in org.drools. StatefulSession class. StatefulSession extends WorkingMemory which has the above API. We look for the same function in org.drools.runtime.StatefulKnowledgeSession class. StatefulKnowledgeSession extends org.drools.runtime.rule. StatefulRuleSession which doesn't have method fireAllRules(org.drools.runtime.rule. AgendaFilter agendaFilter, int fireLimit). We would like to have the API added so we can switch from the rule base to the knowledge base. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2838) fireAllRules does not accept AgendaFilter's provided with the distribution

by Wolfgang Laun (JIRA)

fireAllRules does not accept AgendaFilter's provided with the distribution -------------------------------------------------------------------------- Key: JBRULES-2838 URL: https://issues.jboss.org/browse/JBRULES-2838 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.1.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.0.M1 org.drools.runtime.rule.StatefulRuleSession defines these calls int fireAllRules( org.drools.runtime.AgendaFilter agendaFilter ); public void fireUntilHalt( final org.drools.runtime.AgendaFilter agendaFilter ); BUT org.drools.base.RuleNameEndsWithAgendaFilter implements org.drools.spi.AgendaFilter Same for RuleNameStartsWithAgendaFilter, ~Matches~, ~Equals~ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBRULES-2292) event feed class hangs when using fireUntilHalt

by Jeff DeLong (JIRA)

event feed class hangs when using fireUntilHalt ----------------------------------------------- Key: JBRULES-2292 URL: https://jira.jboss.org/jira/browse/JBRULES-2292 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (fusion) Environment: Eclipse 3.5 with JBoss Tools JBoss Drools Core 5.1.0.truck-N200908260601-H218 using Drools Runtime drools-5.1.0.SNAPSHOT-bin from Sept 10, 2009 Reporter: Jeff DeLong Assignee: Mark Proctor I added a new test to my project: KioskRulesTwoThreadsTest that calls another class InsertEvents in a separate thread, then calls fireUntilHalt. InsertEvents inserts three facts and then three events three times, then mysteriously stops. All I see in the AuditLog is the 12 Object inserted (well and a single Object removed). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-9364) Incorporate changes to the deployment API

by Heiko Braun (JIRA)

Incorporate changes to the deployment API ----------------------------------------- Key: JBAS-9364 URL: https://issues.jboss.org/browse/JBAS-9364 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Web Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-678) Provide selection of JDBC drivers when creating a datasource

by Heiko Braun (JIRA)

Provide selection of JDBC drivers when creating a datasource ------------------------------------------------------------ Key: AS7-678 URL: https://issues.jboss.org/browse/AS7-678 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9130) Create a unified server-config resource that includes the actual instance operations

by Heiko Braun (JIRA)

Create a unified server-config resource that includes the actual instance operations ------------------------------------------------------------------------------------ Key: JBAS-9130 URL: https://issues.jboss.org/browse/JBAS-9130 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Heiko Braun is the 'server' node the element that contains server instances? Yes; that's where you access the actual running server. The operations to actually start/stop/restart the server and check their status are under "server-config" which I'm not happy about. Not intuitive. It's that way because of a kind of chicken-and-egg problem. Emanuel, WDYT about a more sophisticated ProxyController for the servers? Installed by the ServerAddHandler. It handles the lifecycle and status ops directly; proxies the rest. Where it gets complicated is things like read-resource, read-resource-description, read-attribute, all of which would require custom handling. It also make a server resource an odd duck, since it's resource description varies depending on whether the server is started. Yes, we could think of doing something like that - maybe we should just create a ManagedServer for all configured servers and make it the proxy. It should be aware of the lifecyle/state of the server anyway and also holds the associated managed connection. Yes, that sounds like the right way to implement it. Heiko/Ike/Emanuel/anyone -- any concerns about the "resource description varies" issue? What I mean is, for all other resources, read-resource-description will return fixed content. For host=x,server=y it will vary depending on whether the server is actually started. If not running, it will just provide the operation to start the server and a "status" attribute, which will tell you it's stopped. Once you start the server, then read-resource-description will provide that, plus ops to stop and restart the server, plus all the normal attributes and operations exposed by the root resource of a server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-8892) Error during deployment of null while deploying JDBC data source

by Carl Roberts (JIRA)

Error during deployment of null while deploying JDBC data source ---------------------------------------------------------------- Key: JBAS-8892 URL: https://issues.jboss.org/browse/JBAS-8892 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: 7.0.0.Alpha1 Environment: Windows XP Reporter: Carl Roberts Assignee: Ales Justin Fix For: 7.0.0.Alpha2 When I try to define a JDBC data source in standalone.xml file I get this error: 15:53:48,484 ERROR [org.jboss.as.connector.deployer.dsdeployer] (pool-1-thread-1) Error during the deployment of null: java.lang.NullPointerException at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:157) at org.jboss.as.connector.deployers.processors.DsDeploymentProcessor$AS7Deployer.doDeploy(DsDeploymentProcessor.java:189) at org.jboss.as.connector.deployers.processors.DsDeploymentProcessor.processDeployment(DsDeploymentProcessor.java:116) at org.jboss.as.deployment.chain.DeploymentChainImpl.processDeployment(DeploymentChainImpl.java:60) at org.jboss.as.model.ServerDeploymentStartStopHandler.activate(ServerDeploymentStartStopHandler.java:201) at org.jboss.as.model.ServerDeploymentStartStopHandler.deploy(ServerDeploymentStartStopHandler.java:88) at org.jboss.as.model.ServerDeploymentStartStopHandler.deploy(ServerDeploymentStartStopHandler.java:72) at org.jboss.as.connector.subsystems.datasources.JDBCRARDeployService.start(JDBCRARDeployService.java:65) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:923) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_11] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_11] at java.lang.Thread.run(Thread.java:619) [:1.6.0_11] The data source is defined as follows: <subsystem xmlns="urn:jboss:domain:datasources:1.0"> <datasources> <datasource jndi-name="OracleDS" enabled="true" use-java-context="true" pool-name="OracleDS"> <connection-url>jdbc:oracle:thin:@127.0.0.1:1521:IDMAKER</connection-url> <driver-class>oracle.jdbc.driver.OracleDriver</driver-class> <module>com.database.oracle</module> <pool> <prefill>false</prefill> <use-strict-min>false</use-strict-min> </pool> <security> <user-name>dmkr_admin</user-name> <password>Admin12</password> </security> <validation> <validate-on-match>false</validate-on-match> <background-validation>false</background-validation> <useFastFail>false</useFastFail> </validation> <time-out> <set-tx-query-timeout>false</set-tx-query-timeout> </time-out> <statement> <share-prepared-statements>false</share-prepared-statements> </statement> </datasource> </datasources> </subsystem> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JGRP-1193) Simplify RspFilter interface

by Vladimir Blagojevic (JIRA)

Simplify RspFilter interface ---------------------------- Key: JGRP-1193 URL: https://jira.jboss.org/jira/browse/JGRP-1193 Project: JGroups Issue Type: Task Affects Versions: 2.9, 2.8, 2.7 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 3.0 RspFilter interface although having only two methods in its contract has been a source of some confusion regarding the semantics of response filtering. In order to simplify and make response filtering semantics easier to understand and implement a new RspFilter has been proposed for 3.0. RspFilterResult responseReceived(Object response, Address sender); RspFilterResult is an enum with four states where each state is essentially a combination of two boolean variables: validResponse and needMoreResponses. Original discussion reference: http://sourceforge.net/mailarchive/forum.php?thread_name=4BC8943F.2000101... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBRULES-2970) EmptyStackException due to typo "rom entry-point"

by Wolfgang Laun (JIRA)

EmptyStackException due to typo "rom entry-point" ------------------------------------------------- Key: JBRULES-2970 URL: https://issues.jboss.org/browse/JBRULES-2970 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 Note the 'f' missing from "from" rule addToken when $s: Sale( discount == null ) rom entry-point "cash" then end [5,37]: [ERR 102] Line 5:37 mismatched input 'entry' in rule "addToken" [0,0]: Line 13:0 unexpected exception at input 'function'. Exception: java.util.EmptyStackException. Stack trace: java.util.EmptyStackException at java.util.Stack.peek(Stack.java:102) at java.util.Stack.pop(Stack.java:84) at org.drools.lang.ParserHelper.popParaphrases(ParserHelper.java:409) at org.drools.lang.ParserHelper.end(ParserHelper.java:723) at org.drools.lang.DRLParser.function(DRLParser.java:621) at org.drools.lang.DRLParser.statement(DRLParser.java:254) at org.drools.lang.DRLParser.compilationUnit(DRLParser.java:143) at org.drools.compiler.DrlParser.compile(DrlParser.java:225) at org.drools.compiler.DrlParser.parse(DrlParser.java:136) at org.drools.compiler.DrlParser.parse(DrlParser.java:141) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:292) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:471) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:28) at rss.drools.setup.Application.setup(Application.java:47) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2120) Tx logic doesn't take method-intf type into acount

by Carlo de Wolf (JIRA)

Tx logic doesn't take method-intf type into acount -------------------------------------------------- Key: EJBTHREE-2120 URL: https://jira.jboss.org/browse/EJBTHREE-2120 Project: EJB 3.0 Issue Type: Bug Components: transactions Reporter: Carlo de Wolf Fix For: bom-as6-0.1.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
8
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 2011