Cell() PropertySpecific Behaviour
by Mark Proctor
We are just fine tuning PropertySpecific behahviour.
Initially a pattern without any properties' mask was set to
LONG.MAX_VALUE so that it responded to any field changes.
However we've now changed it to 0, so Cell() will respond to the initial
insertion, but it will not respond to any modifies.
Should you want it to respond to modifies you must add @watch(*).
The other aspect is that we are adding a kbuillder configration to set
the default behaviour. Currently it is off. With it defaulting to off
using PropertySpecific as an annotation makes sense. If we default it to
on you then need to use PropertySpecific(true). i.e. the reversing of
the logic means for the common case we now need an argument. Considering
this common case will become default at some point in the future, i.e.
you want the parameterless version to be the common use case.
NonPropertySpecific is a bit long :)
Mark
12 years, 10 months
Bug mvel /* parsed incorrectly 5.3.0.CR1:d63c9c5efe49e
by Benjamin Bennett
Just wanted to pass it on was trying to track down what was causing parse
error .
Here is test case . I tried to bisect but couldn't get it to compile on
every revision. Most likely my set up .
But here is test case that is broken sometime after 5.3.0.CR1 . Please
don't flame me if this is the wrong channel to send this too.
public void testParseSlashStarInString() {
String str = "";
str += "package org.drools \n";
str += "import org.drools.Cheese \n";
str += "dialect \"mvel\"\n";
str += "rule rule1 \n";
str += " when \n";
str += " $c : Cheese() \n";
str += " \n";
str += " then \n";
str += " Cheese hold= new Cheese(\"/*\",5);\n";
str += "end\n";
final KnowledgeBuilder kbuilder =
KnowledgeBuilderFactory.newKnowledgeBuilder();
kbuilder.add(ResourceFactory.newByteArrayResource(str.getBytes()),
ResourceType.DRL);
StringBuffer stringBuffer = new StringBuffer();
for (KnowledgeBuilderError e : kbuilder.getErrors()) {
stringBuffer.append(e.toString());
}
Assert.assertEquals(stringBuffer.toString(), 0,
kbuilder.getErrors().size());
)
--
Sincerely,
Benjamin Bennett
314.246.0645
benbennett(a)gmail.com
"For a successful technology, reality must take precedence over public
relations, for Nature cannot be fooled."
Richard Feynman
12 years, 10 months
FAO: Jervis Liu: Disabling editors configuration
by Mariano De Maio
Sorry to bother. Needed to add a configuration point to enable/disable
external editors (for the Form Builder inclusion in Guvnor. Might also
be useful for the Process Designer). This should be a configuration on
server side, non dependent on gwt compilation. I would like to see
your input on where would be the best place to keep such a
configuration, if none is planned already.
Thanks in advance,
Mariano
12 years, 10 months
Fwd: [JBoss JIRA] (JBRULES-2020) illegible code snippets in PDF
by Wolfgang Laun
Look at 5.3.0. Final Expert page 133.
-W
---------- Forwarded message ----------
From: "Geoffrey De Smet (JIRA)" <jira-events(a)lists.jboss.org>
Date: Thu, 23 Feb 2012 09:34:38 -0500 (EST)
Subject: [JBoss JIRA] (JBRULES-2020) illegible code snippets in PDF
To: wolfgang.laun(a)gmail.com
[ https://issues.jboss.org/browse/JBRULES-2020?page=com.atlassian.jira.plug...
]
Geoffrey De Smet commented on JBRULES-2020:
-------------------------------------------
The screenshot looks good? What's the problem?
I am working on the styles and about to release them. Either we fix it
now or much later :)
> illegible code snippets in PDF
> ------------------------------
>
> Key: JBRULES-2020
> URL: https://issues.jboss.org/browse/JBRULES-2020
> Project: Drools
> Issue Type: Quality Risk
> Security Level: Public(Everyone can see)
> Components: drools-docs
> Affects Versions: 5.0.0.CR1
> Environment: n/a
> Reporter: Wolfgang Laun
> Assignee: Michael Anstis
> Priority: Critical
> Fix For: 5.4.0.CR1
>
> Attachments: example.png
>
>
> In the PDF version of the docs, code snippets appear in red print on black backround.
> Headache tablets cost money.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
ACM DEBS 2012- Second Call for Papers
by Adrian Paschke
=====================================================================
DEBS2012
6th ACM International Conference on Distributed Event-Based Systems
July 16-20, 2012
Freie Universitaet Berlin, Berlin, Germany
http://www.csw.inf.fu-berlin.de/debs2012
=====================================================================
The objectives of the 6th ACM International Conference on Distributed
Event-Based Systems (DEBS) are to provide a forum dedicated to the
dissemination of original research, the discussion of practical insights,
and the reporting of relevant experience relating to event-based computing
that was previously scattered across several scientific and professional
communities. The conference also aims at providing a forum for academia and
industry to exchange ideas, for example, through industry papers and demo
papers.
DEBS 2012 Tracks
================
The conference will consist of the following tracks:
- Research track featuring high quality research paper on relevant topics.
- Industry track with two sub-tracks: industry full papers and industry
experience reports.
- Tutorials geared towards either the research or the industrial
communities.
- Demos and posters.
- The DEBS 2012 Grand Challenge is a problem solving competition for
commercial and research event-based systems.
- Gong show: The gong show will consist of short presentations about
visionary and outrageous ideas towards the next generation of event-based
systems. The audience will vote for the best idea.
- Doctoral workshop
Important Dates
=======================
- Abstract submission for research and Industry papers and Industry
experience reports: February 27, 2012
- Grand Challenge participation intent (non-binding): February 27, 2012
- Research, Industry and Tutorial papers submission, and (optional) Industry
experience report submission: March 5, 2012
- Grand Challenge problem description: March 7, 2012
- Author notification for tutorials, research and Industry papers, and
Industry experience reports: April 30, 2012
- Poster and demo submission: May 2, 2012
- Grand Challenge Solutions including 4 page papers: May 2, 2012
- Doctoral Workshop submission: May 2, 2012
- Grand Challenge abstracts: May 2, 2012
- Author notification for poster, demo, Challenge, PhD papers: May 16, 2012
- Conference: July 16-20, 2012
Paper Submission
=======================
Submissions will be accepted in the following tracks:
Research track;
Industry track;
Tutorials Track;
Demos& Posters;
Grand Challenge;
Doctoral Workshop.
All submissions must be original and unpublished. Accepted papers will be
published by ACM and disseminated through the ACM Digital Library.
More information about the tracks and submission information can be found on
the DEBS 2012 website:
http://www.csw.inf.fu-berlin.de/debs2012/calls.html
Scope of the Conference
=======================
The topics addressed by the conference include (but are not
limited to):
Models, Architectures and Paradigms
- Event-driven architectures
- Basic interaction models
- Event algebras, event schemas and type systems
- Languages for event correlation and patterns, streaming and continuous
queries, data fusion
- Models for static and dynamic environments
- Complex event processing
- Design and programming methodologies
- Event-based business process management and modeling
- Experimental methodologies
- Performance modeling and prediction based on analytic approaches
- Functional Reactive Programming
Middleware Infrastructures for Event-Based Computing
- Federated event-based systems
- Middleware for actuator and sensor networks
- Algorithms and protocols
- Optimization techniques for event-based (or streaming) systems
- Event dissemination based on p2p systems
- Context and location awareness
- Fault-tolerance, reliability, availability, and recovery
- Security issues
- (Self-)Management
- Mobility and resource constrained device support
- Streaming queries, transformations, or correlation engines
- Logic-based event processing
- Semantic event processing
- Business Process Management with events
Applications, Experiences, and Requirements
- Use cases and applications of event-based systems
- Real-world application deployments using event-based middleware
- Domain-specific deployments of event-based systems
- Real-world data characterizing event-based applications
- Benchmarks, performance evaluations, and testbeds
- Application requirements for next-generation event-based solutions
- Relation to other architectures
- Enterprise application integration
- Event-driven business process management
- Information logistics
- Seamless integration of event-based mechanisms into middleware platforms
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
12 years, 10 months
Re: [rules-dev] [rules-users] Need Camel + drools (OSGI) integration help
by Alexander Filipchik
Hello!
I finally managed to get it working, but it required some changes in the
existent stuff...
Here is a diff:
git://github.com/droolsjbpm/drools.git
diff --git a/drools-compiler/pom.xml b/drools-compiler/pom.xml
index 708a5b2..4b1dc98 100644
--- a/drools-compiler/pom.xml
+++ b/drools-compiler/pom.xml
@@ -244,7 +244,7 @@
<_removeheaders>Ignore-Package</_removeheaders>
<Bundle-SymbolicName>org.drools.compiler;singleton:=true</Bundle-SymbolicName>
<Require-Bundle>org.drools.core;visibility:=reexport;bundle-version="${drools.osgi.version}"</Require-Bundle>
- <Import-Package>!org.drools.*,
+ <Import-Package>org.antlr.*;version="3.4",!org.drools.*,
<!-- java compilers are optional: only need one at most -->
org.codehaus.janino.*;resolution:=optional,org.eclipse.jdt.*;resolution:=optional,
*</Import-Package>
git://github.com/droolsjbpm/droolsjbpm-integration.git
diff --git a/drools-camel/pom.xml b/drools-camel/pom.xml
index a5a6b3d..273bfaa 100644
--- a/drools-camel/pom.xml
+++ b/drools-camel/pom.xml
@@ -23,7 +23,7 @@
<dependency>
<groupId>org.drools</groupId>
<artifactId>knowledge-internal-api</artifactId>
- </dependency>
+ </dependency>
<dependency>
<groupId>org.drools</groupId>
<artifactId>drools-core</artifactId>
@@ -186,5 +186,44 @@
<scope>provided</scope>
</dependency>
</dependencies>
-
+ <build>
+ <plugins>
+ <plugin>
+ <artifactId>maven-jar-plugin</artifactId>
+ <configuration>
+ <archive>
+ <manifestFile>META-INF/MANIFEST.MF</manifestFile>
+ </archive>
+ </configuration>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.felix</groupId>
+ <artifactId>maven-bundle-plugin</artifactId>
+ <extensions>true</extensions>
+ <executions>
+ <execution>
+ <id>manifest</id>
+ <phase>process-classes</phase>
+ <goals>
+ <goal>manifest</goal>
+ </goals>
+ </execution>
+ </executions>
+ <configuration>
+ <manifestLocation>META-INF</manifestLocation>
+ <instructions>
+
<Bundle-SymbolicName>org.drools.camel;singleton:=true</Bundle-SymbolicName>
+ <_removeheaders>Ignore-Package</_removeheaders>
+ <Require-Bundle>
+ org.drools.core;bundle-version="${drools.osgi.version}",
+ org.drools.spring;bundle-version="${drools.osgi.version}"
+ </Require-Bundle>
+ <Import-Package>!org.drools.*, *</Import-Package>
+ <Export-Package>!org.drools.grid, org.drools.camel.*,
org.drools.camel.jax</Export-Package>
+ <DynamicImport-Package>org.drools.*</DynamicImport-Package>
+ </instructions>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
</project>
diff --git a/drools-container/drools-spring/pom.xml
b/drools-container/drools-spring/pom.xml
index b6be52c..f83a457 100644
--- a/drools-container/drools-spring/pom.xml
+++ b/drools-container/drools-spring/pom.xml
@@ -126,7 +126,45 @@
<groupId>org.antlr</groupId>
<artifactId>antlr-runtime</artifactId>
<scope>test</scope>
- </dependency>
+ </dependency>
</dependencies>
-
+ <build>
+ <plugins>
+ <plugin>
+ <artifactId>maven-jar-plugin</artifactId>
+ <configuration>
+ <archive>
+ <manifestFile>META-INF/MANIFEST.MF</manifestFile>
+ </archive>
+ </configuration>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.felix</groupId>
+ <artifactId>maven-bundle-plugin</artifactId>
+ <extensions>true</extensions>
+ <executions>
+ <execution>
+ <id>manifest</id>
+ <phase>process-classes</phase>
+ <goals>
+ <goal>manifest</goal>
+ </goals>
+ </execution>
+ </executions>
+ <configuration>
+ <manifestLocation>META-INF</manifestLocation>
+ <instructions>
+
<Bundle-SymbolicName>org.drools.spring;singleton:=true</Bundle-SymbolicName>
+ <_removeheaders>Ignore-Package</_removeheaders>
+
<Require-Bundle>org.drools.core;bundle-version="${drools.osgi.version}"</Require-Bundle>
+ <Import-Package>!org.drools.*, *</Import-Package>
+ <Export-Package>
+
org.drools.grid,org.drools.grid.impl,org.drools.container.spring
+ </Export-Package>
+ <DynamicImport-Package>org.drools.*</DynamicImport-Package>
+ </instructions>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
</project>
Alex
On Tue, Feb 7, 2012 at 6:01 PM, Alexander Filipchik <afilipchik(a)gmail.com>wrote:
> Thank you! But didn't help.
> Actually I see some weird behavior. I decided to try referring drools-core
> using Require-Bundle from my bundle, so I added
> <Bundle-SymbolicName>org.drools.core</Bundle-SymbolicName> to a
> drools-core package, recompiled it and got
> NullPointerException (still without stacktrace) when I tried to deploy new
> core bundle to a karaf container.
>
> I was able to deploy it after I removed Bundle-SymbolicName and recompiled
> again.
>
> Thanks,
> Alex
>
> On Tue, Feb 7, 2012 at 4:42 PM, Mauricio Salatino <salaboy(a)gmail.com>wrote:
>
>> I've already answer a similar question here.. try including inside the
>> application that is using the bundles the file called:
>> drools.packagebuilder.conf
>>
>> which contains:
>> drools.dialect.default = java
>> drools.dialect.java =
>> org.drools.rule.builder.dialect.java.JavaDialectConfiguration
>> drools.dialect.java.compiler = ECLIPSE
>>
>> drools.dialect.mvel =
>> org.drools.rule.builder.dialect.mvel.MVELDialectConfiguration
>> drools.dialect.mvel.strict = true
>> drools.dialect.mvel.langLevel = 4
>>
>> drools.accumulate.function.average =
>> org.drools.base.accumulators.AverageAccumulateFunction
>> drools.accumulate.function.max =
>> org.drools.base.accumulators.MaxAccumulateFunction
>> drools.accumulate.function.min =
>> org.drools.base.accumulators.MinAccumulateFunction
>> drools.accumulate.function.count =
>> org.drools.base.accumulators.CountAccumulateFunction
>> drools.accumulate.function.sum =
>> org.drools.base.accumulators.SumAccumulateFunction
>> drools.accumulate.function.collectList =
>> org.drools.base.accumulators.CollectListAccumulateFunction
>> drools.accumulate.function.collectSet =
>> org.drools.base.accumulators.CollectSetAccumulateFunction
>>
>> drools.evaluator.coincides =
>> org.drools.base.evaluators.CoincidesEvaluatorDefinition
>> drools.evaluator.before =
>> org.drools.base.evaluators.BeforeEvaluatorDefinition
>> drools.evaluator.after =
>> org.drools.base.evaluators.AfterEvaluatorDefinition
>> drools.evaluator.meets =
>> org.drools.base.evaluators.MeetsEvaluatorDefinition
>> drools.evaluator.metby =
>> org.drools.base.evaluators.MetByEvaluatorDefinition
>> drools.evaluator.overlaps =
>> org.drools.base.evaluators.OverlapsEvaluatorDefinition
>> drools.evaluator.overlappedby =
>> org.drools.base.evaluators.OverlappedByEvaluatorDefinition
>> drools.evaluator.during =
>> org.drools.base.evaluators.DuringEvaluatorDefinition
>> drools.evaluator.includes =
>> org.drools.base.evaluators.IncludesEvaluatorDefinition
>> drools.evaluator.starts =
>> org.drools.base.evaluators.StartsEvaluatorDefinition
>> drools.evaluator.startedby =
>> org.drools.base.evaluators.StartedByEvaluatorDefinition
>> drools.evaluator.finishes =
>> org.drools.base.evaluators.FinishesEvaluatorDefinition
>> drools.evaluator.finishedby =
>> org.drools.base.evaluators.FinishedByEvaluatorDefinition
>> drools.evaluator.equality =
>> org.drools.base.evaluators.EqualityEvaluatorsDefinition
>> drools.evaluator.comparable =
>> org.drools.base.evaluators.ComparableEvaluatorsDefinition
>> drools.evaluator.set = org.drools.base.evaluators.SetEvaluatorsDefinition
>> drools.evaluator.matches =
>> org.drools.base.evaluators.MatchesEvaluatorsDefinition
>> drools.evaluator.soundslike =
>> org.drools.base.evaluators.SoundslikeEvaluatorsDefinition
>>
>> Cheers
>>
>>
>> On Tue, Feb 7, 2012 at 9:03 PM, Alexander Filipchik
>> <afilipchik(a)gmail.com> wrote:
>> > It's not an obvious how to OSGI-fy something :)
>> >
>> > I did some homework - now I have OSGi-ified versions of drools-spring
>> and
>> > drools-camel.
>> > Also I created own bundle and tried to import
>> KnowledgeBaseFactoryService,
>> > ServiceRegistry and KnowledgeBaseFactoryService as described in
>> > http://docs.jboss.org/jbpm/v5.2/userguide/ch18.html#d0e4308.
>> > All what I got - NullPointerException from karaf core (haven't gotten
>> full
>> > staketrace yet. For some reason it is just:
>> > 15:11:34,484 | INFO | l Console Thread | Console
>> |
>> > ? ? | 34 -
>> org.apache.karaf.shell.console
>> > - 2.2.2.fuse-02-13 | Exception caught while executing command
>> > java.lang.NullPointerException
>> > )
>> >
>> > So, I spent some time randomly adding and removing configuration params
>> and
>> > I found - NPE occurs when I'm trying to import
>> > org.drools.KnowledgeBaseFactoryService.
>> > I guess (i'm not OSGI expert) it could be because org.drools package is
>> > exported in 2! bundles. It is in drools-core and knowledge-api bundles.
>> And
>> > I guess, karaf container just can't link my bundle with both core and
>> api,
>> > only first bundle which contains requested package (org.drools) wins.
>> >
>> > Any ideas on how to make it work?
>> > I actually have one - every bundle should export own package. For
>> > knowledge-api it should be org.drools.api, and org.drools.core for
>> > drools-core.
>> >
>> > Here is full log of similar packages:
>> > WARNING: multiple bundles are exporting package org.drools.command
>> > - org.drools.core [218]
>> > - org.drools.api [216]
>> > - org.drools.internalapi [217]
>> >
>> > WARNING: multiple bundles are exporting package
>> org.drools.runtime.process
>> > - org.drools.core [218]
>> > - org.drools.api [216]
>> >
>> > WARNING: multiple bundles are exporting package org.drools.time
>> > - org.drools.core [218]
>> > - org.drools.api [216]
>> >
>> > WARNING: multiple bundles are exporting package
>> > org.apache.geronimo.transaction
>> > - org.apache.aries.transaction.manager [123]
>> > - org.apache.aries.transaction.manager [51]
>> >
>> > WARNING: multiple bundles are exporting package org.drools
>> > - org.drools.core [218]
>> > - org.drools.api [216]
>> >
>> > WARNING: multiple bundles are exporting package
>> > org.apache.geronimo.transaction.manager
>> > - org.apache.aries.transaction.manager [123]
>> > - org.apache.aries.transaction.manager [51]
>> >
>> > WARNING: multiple bundles are exporting package org.drools.grid
>> > - org.drools.core [218]
>> > - org.drools.spring [220]
>> >
>> > WARNING: multiple bundles are exporting package jline
>> > - org.apache.servicemix.bundles.jruby [210]
>> > - org.apache.karaf.shell.console [34]
>> >
>> > WARNING: multiple bundles are exporting package
>> > org.apache.geronimo.transaction.log
>> > - org.apache.aries.transaction.manager [123]
>> > - org.apache.aries.transaction.manager [51]
>> >
>> > WARNING: multiple bundles are exporting package org.drools.management
>> > - org.drools.core [218]
>> > - org.drools.api [216]
>> >
>> > WARNING: multiple bundles are exporting package org.drools.agent
>> > - org.drools.core [218]
>> > - org.drools.api [216]
>> >
>> > WARNING: multiple bundles are exporting package org.drools.event
>> > - org.drools.core [218]
>> > - org.drools.api [216]
>> >
>> > 2012/2/3 Mark Proctor <mproctor(a)codehaus.org>
>> >>
>> >> neither spring or camel have been OSGi-ified. only api, core, compiler,
>> >> templates, decision-tables and flow have.
>> >>
>> >> If someone wants to OSGi-ify those and contribute back they are very
>> >> welcome:
>> >> 1) update the pom.xml to use the osgi bundle plugin, see other existing
>> >> poms.
>> >>
>> >>
>> https://github.com/droolsjbpm/drools/blob/master/drools-decisiontables/po...
>> >> 2) create an Activator to register the module, again see Activator's
>> for
>> >> core, compiler etc.
>> >>
>> >>
>> https://github.com/droolsjbpm/drools/blob/master/drools-decisiontables/sr...
>> >> 3) update the osgi bundle's pom with new dependencies, make sure to
>> pull
>> >> in the spring ones, unless the actual project provides osgi ready jars.
>> >>
>> >>
>> https://github.com/droolsjbpm/droolsjbpm-build-distribution/tree/master/d...
>> >> 4) Update the boot-bundles.properties so that Spring DM loads the OSGi
>> >> dependencies
>> >>
>> >>
>> https://github.com/droolsjbpm/droolsjbpm-build-distribution/blob/master/d...
>> >> 5) write unit tests for spring and camel.
>> >>
>> >> Mark
>> >> On 03/02/2012 03:47, Alexander Filipchik wrote:
>> >>
>> >> Hello all!
>> >>
>> >> Don't know if it is right list to ask, but I'm trying to make drools +
>> >> camel running on Fuse (ServiceMix container).
>> >> I couldn't even install OSGI drools artifacts for 5.3.1 version
>> (because
>> >> of weird dependency on drools.core Snapshot),
>> >> but did it with v5.2.1. I used:
>> >>
>> >> mvel2/2.1.0,
>> >>
>> org.drools/drools-core/5.2.1.Final, org.drools/drools-compiler/5.2.1.Final,
>> >> org.drools/knowledge-api/5.2.1.Final
>> >> and org.drools/drools-camel/5.2.1.Final.
>> >>
>> >> All are installed and active. Part of log:
>> >>
>> >> [ 162] [Active ] [ ] [ ] [ 60] Drools ::
>> Compiler
>> >> (5.2.1.Final)
>> >>
>> >> [ 163] [Active ] [ ] [ ] [ 60] mvel2
>> >> (2.1.0.drools4)
>> >>
>> >> [ 164] [Active ] [ ] [ ] [ 60] Drools :: Core
>> >> (5.2.1.Final)
>> >>
>> >> [ 165] [Active ] [ ] [ ] [ 60] Knowledge API
>> >> (5.2.1.Final)
>> >>
>> >> [ 172] [Active ] [ ] [ ] [ 60]
>> >> mvn:org.drools/drools-camel/5.2.1.Final
>> >>
>> >> Then I tried to add my own camel-drools router (I created OSGI bundle
>> for
>> >> it). It depends on:
>> >>
>> >> Import-Package:
>> >>
>> org.apache.activemq,org.apache.activemq.camel.component,org.apache.activemq.pool,org.apache.camel;version="[2.8,3)",org.apache.camel.builder;version="[2.8,3)",org.apache.camel.component.jms;version="[2.8,3)",org.apache.camel.model;version="[2.8,3)",org.drools.camel.component,org.osgi.service.blueprint;version="[1.0.0,2.0.0)",org.springframework.transaction;version="[3,4)"
>> >>
>> >> It tried to install it to a container but all I got -
>> >>
>> >> Error executing command: Unresolved constraint in bundle
>> >> com.betfair.drools [170]: Unable to resolve 170.0: missing requirement
>> >> [170.0] package; (package=org.drools.camel.component)
>> >>
>> >> I even tried to put drools-camel.jar with org.drools.camel.component
>> in a
>> >> lib folder and add package to
>> org.osgi.framework.system.packages.extra, but
>> >> got same result.
>> >>
>> >> Do you have any idea, blog posts, samples which could help me?
>> >> I'm completely stuck.
>> >>
>> >> Thanks,
>> >> Alex
>> >>
>> >>
>> >> _______________________________________________
>> >> rules-users mailing list
>> >> rules-users(a)lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/rules-users
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> rules-users mailing list
>> >> rules-users(a)lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/rules-users
>> >>
>> >
>> >
>> > _______________________________________________
>> > rules-dev mailing list
>> > rules-dev(a)lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/rules-dev
>> >
>>
>>
>>
>> --
>> - CTO @ http://www.plugtree.com
>> - MyJourney @ http://salaboy.wordpress.com
>> - Co-Founder @ http://www.jugargentina.org
>> - Co-Founder @ http://www.jbug.com.ar
>>
>> - Salatino "Salaboy" Mauricio -
>>
>> _______________________________________________
>> rules-users mailing list
>> rules-users(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/rules-users
>>
>
>
12 years, 10 months
Once more: why, why, why is this user-provided information hidden?
by Wolfgang Laun
A recent post asks (*again, for the umpteenth time*) for a way to retrieve
declared fact types from a knowledge package or knowledge base.
There is a way to retrieve org.drools.definition.type.FactType by package
and type name, so it ought to be possible to retrieve a Collection of all
FactTypes.
-W
12 years, 10 months
salience alternative with before/after
by Mark Proctor
Davide has suggested a good idea.
Now that rules support annotations, and annotations with values. We
should add a before/after keyword to each rule. before/after would then
take a list of annotations. The idea is to use this to generate salience
under the covers.
rule resetBalance before( @cashflow ) when then end
rule debit @cashflow when then end
rule credit @cashflow when then end
rule printBalance after(@cashflow ) when then end.
Salience gives one rule priority over another, thus it's declaring an
implicit relationship between rules. Yet it's a magic number that
doesn't easily show this relation, and as the rulebase grows it can be
very hard to determine those relationships as specified by salience from
reading the rules. before/after allows you to specify declarative the
relationships betwen rules in a more maintainable and readable way, even
if under the covers it's just generating:
rule resetBalance salience 100 when then end
rule debit salience 0 when then end
rule credit salience 0 when then end
rule printBalance saliance -100 when then end.
Yes there are agenda-groups and ruleflow-groups, but they can be a bit
cumbersome compared to the simplicity of using salience. This way we get
the simplicity of using salience, without the downfalls of it being a
magic number.
What do people think? Any ideas on how we can improve this? At build
time it would have to report impossible to resolve relationships and barf.
Mark
12 years, 10 months
