[JBoss JIRA] Created: (JBRULES-3144) Experiment with "when rule becomes true execute a callback" feature in Drools Expert, benchmarked by Drools Planner
by Geoffrey De Smet (JIRA)
Experiment with "when rule becomes true execute a callback" feature in Drools Expert, benchmarked by Drools Planner
-------------------------------------------------------------------------------------------------------------------
Key: JBRULES-3144
URL: https://issues.jboss.org/browse/JBRULES-3144
Project: Drools
Issue Type: Task
Security Level: Public (Everyone can see)
Components: drools-core (expert), drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
<_conan_> ge0ffrey: can do unfalse situation
<ge0ffrey> conan: is there a way to get a "when the rule no longer applies, execture this code"?
<_conan_> ge0ffrey: i.e. when a ruel becomes untrue execute a callback
<ge0ffrey> conan: yes!
<_conan_> yes
<_conan_> it's trivial to do actually
<ge0ffrey> conan: what's the code name for that feature?
<_conan_> not related to TMS
<ge0ffrey> yep
<_conan_> you can potentially hack one for yourself
<_conan_> in about 10 minutes
<ge0ffrey> I 'd also need to have a value which was caclulated in hte the orginal RHS
<_conan_> but the feature over all will take a lot of thought, due to language design
<_conan_> but for your use case
<_conan_> it's trivial to do
<_conan_> in the rule you have the Activation
<_conan_> the impl is the AgendaItem
<ge0ffrey> conan: would love to do this (espeically if I get some appointed time for it :)
<_conan_> you can do kcontext.getActivation
<_conan_> it'll take you 15 minutes to do it
<_conan_> change AgendaItem to have new field reference Callable or what ever you want to use.
<ge0ffrey> k
<_conan_> in the consequnce just do agendaItem.addCallable( new Callable() {............ } );
<_conan_> i.e. use an anonymous class
<_conan_> the only thing you need to do now
<_conan_> is in RuleTerminalNode in retractLeftTuple is agendaItem.executeCallables()
<_conan_> that's it
<_conan_> it's that trivial
<ge0ffrey> (copy pasting htis in an issue to look at later, as my workspace is open on my fork today)
<_conan_> I just don't want to expose that as a generic feature
<_conan_> because the issue needs more thought
<ge0ffrey> of course
<_conan_> with regards to language design
<_conan_> but for your use case
<_conan_> and as you are an expert
<_conan_> it's fine
<_conan_> I'd suggest you just maintain a "patched" version of drools for that feature
<ge0ffrey> but if the exeperiment works well, we can look at language design
<_conan_> yes
<_conan_> I need this anyway
<_conan_> becausae rule engines need to tell peopl when things stop being true
<ge0ffrey> conan: not going to start using for released planner until it's in drools expert for real
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (AS7-1231) Horrible XML parsing error reports
by Bill Burke (JIRA)
Horrible XML parsing error reports
----------------------------------
Key: AS7-1231
URL: https://issues.jboss.org/browse/AS7-1231
Project: Application Server 7
Issue Type: Quality Risk
Reporter: Bill Burke
If I make a typo in jboss-web.xml (or any other descriptor for that matter) I get really obscure errors that don't help me debug the problem. (See below). Each project really needs to
09:39:14,132 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC00001: Failed to start service jboss.deployment.unit."basic.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."basic.war".PARSE: Failed to process phase PARSE of deployment "basic.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to parse "/content/basic.war/WEB-INF/jboss-web.xml"
at org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:66)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
Caused by: com.ctc.wstx.exc.WstxParsingException: Received non-all-whitespace CHARACTERS or CDATA event in nextTag().
at [row,col {unknown-source}]: [5,4]
at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:606)
at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:479)
at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:464)
at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1137)
at org.jboss.metadata.parser.jbossweb.ValveMetaDataParser.parse(ValveMetaDataParser.java:45)
at org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:155)
at org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:64)
... 6 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBWEB-72) html page and jsp are not display with in a Context defined in server.xml.
by Jean-Frederic Clere (JIRA)
html page and jsp are not display with in a Context defined in server.xml.
--------------------------------------------------------------------------
Key: JBWEB-72
URL: http://jira.jboss.com/jira/browse/JBWEB-72
Project: JBoss Web
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core
Affects Versions: JBoss Web Server 1.0.1 GA
Environment: any
Reporter: Jean-Frederic Clere
Assigned To: Jean-Frederic Clere
Priority: Minor
When using a Context definition in server.xml like:
<Context path="/test" docBase="/home/jfclere/TMP/MYAPP" />
The jsp and html pages of /home/jfclere/TMP/MYAPP are not displayed (404 is returned).
That is because the conf/web.xml is not used to set the defaults when the <Context/> is processed.
DefaultWebXml is set in TomcatDeployer and that is after the <Context/> needs it. The default value is used but it is set to "web.xml".
--
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
14 years
[JBoss JIRA] Created: (JBRULES-2934) CommandFactory newStartProcess doesn't set parameters
by Dan Seaver (JIRA)
CommandFactory newStartProcess doesn't set parameters
-----------------------------------------------------
Key: JBRULES-2934
URL: https://issues.jboss.org/browse/JBRULES-2934
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.2.0.M1
Reporter: Dan Seaver
Assignee: Mark Proctor
Should be able to set parameter values when starting a process. Current code:
public static Command newStartProcess(String processId,
Map<String, Object> parameters) {
return getCommandFactoryProvider().newStartProcess( processId );
}
proposed code:
public static Command newStartProcess(String processId,
Map<String, Object> parameters) {
StartProcessCommand cmd = new StartProcessCommand(processId);
cmd.setParameters(parameters);
return cmd;
}
Also, I think this issue would go under the droolsjbpm-knowledge component if the JIRA component list were updated.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBRULES-2533) Update Eclipse Compiler dependency
by Fabian Lange (JIRA)
Update Eclipse Compiler dependency
----------------------------------
Key: JBRULES-2533
URL: https://jira.jboss.org/browse/JBRULES-2533
Project: Drools
Issue Type: Task
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.1.0.M2
Reporter: Fabian Lange
Assignee: Mark Proctor
drools-compiler pom includes a reference to eclipse JDT. in 5.0.1 this was a 4 MB core_whatever.jar
Because I wanted to improve compiler performance I tried out a never eclipse compiler package. Finding it was not very easy, because eclipse seems to change group and artifact ids every day.
I found a module which only contains the compiler part from eclipse 3.5.1, which works in all my tests ok.
Another nice benefit was that the size of my war shrunk by 3 Megabytes, as this module is only 1.7 megs.
It even helped for performance of compilation process by the way. Not that this is a main bottleneck, but we have files that take seconds to compile.
My tests on my windows box with java 6 gave 5-10% improvement using the 3.5.1 jdt compiler.
Here the part for the pom:
{code}
<dependency>
<groupId>org.eclipse.jdt.core.compiler</groupId>
<artifactId>ecj</artifactId>
<version>3.5.1</version>
</dependency>
{code}
--
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
14 years
[JBoss JIRA] Created: (AS7-1219) Add jboss-dmr documentation to the Admin Guide
by Brian Stansberry (JIRA)
Add jboss-dmr documentation to the Admin Guide
----------------------------------------------
Key: AS7-1219
URL: https://issues.jboss.org/browse/AS7-1219
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
Basic documentation on DMR:
1) Purpose
2) Source location and maven coordinates
3) Description of the 2 public classes, ModelNode and ModelType, link to 1.0.0.Final code for each on github
4) Some simple examples
5) Fully document the string format, so people know how to read DMR output and how to write DMR input
6) Links to 5) above in the CLI docs, both in a place that describes how to read output and in a place that describes the format for parameter values in low-level operation requests
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years